Use ShardStitch with Kiro.
This Kiro profile uses a steering document for project pickup and a separate MCP settings file. It is most useful when the next Kiro workspace can reopen the same project.
Integration paths.
.kiro/steering/handover.md.
Auto-configured at ~/.kiro/settings/mcp.json.
Project steering seeds the next run; verify prior execution output independently.
Setup path.
Write .kiro/steering/handover.md in the repository and open the exact workspace. If using MCP, inspect ~/.kiro/settings/mcp.json and confirm the server is available to this Kiro profile.
Generate the steering handover and install MCP automatically.
Ask Kiro to identify the steering document, current branch, and the next verification step before it changes code.
Limits to know.
Steering context is not the same as a restored Kiro session. User-level MCP settings may differ between machines, and neither path verifies that remote task state matches the local checkout.
Best use case.
Starting Kiro with verified project state and a next action.
FAQ.
Does Kiro steering restore the last agent execution?
No. The handover file guides a new workspace; it does not prove the prior execution completed or restore its remote run state. Check local files and output.
Resume this workflow.
For a code-execution task that was interrupted, record the last command and whether its output completed. Reopen Kiro in the same project, compare the diff, and rerun only the missing safe check.
Confirm Kiro steering includes the checkpoint for this workspace, preserving existing requirements and acceptance criteria.
Primary source and delivery boundary.
Kiro documentation (checked September 27, 2026). Kiro documents its development workflow and configuration. Verify the workspace and steering applied to your current client rather than treating a saved file as proof that a session consumed it.
Tool-specific troubleshooting
For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Kiro.