Loading...
Loading...
Found 7 Skills
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Sync spec files with code changes. Triggers when modifying code that affects .kiro/specs/*/requirements.md or .kiro/specs/*/design.md. Use after implementing features, fixing bugs, or refactoring that changes behavior documented in specs.
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Create PRDs through the gather-criticize loop, sync existing PRDs, push amendments, and check PRD status.
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .claude/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Scan code and specs for drift, directly synchronize spec files, and report the gaps in chat.