Kiro Spec Status
Productivitykiro-spec-statusKiro Spec Status is an Agent Skill for productivity published in the cm45t3r/candlestick repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Show specification status and progress
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/cm45t3r/candlestick/blob/HEAD/.claude/skills/kiro-spec-status/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/kiro-spec-status, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
kiro-spec-status Skill
Core Mission
- Success Criteria:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress
- Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available
Execution Steps
Step 1: Load Spec Context
- Read
.kiro/specs/$ARGUMENTS/spec.jsonfor metadata and phase status - Read
.kiro/specs/$ARGUMENTS/brief.mdif it exists - Read existing files:
requirements.md,design.md,tasks.md(if they exist) - Check
.kiro/specs/$ARGUMENTS/directory for available files - Read
.kiro/steering/roadmap.mdif it exists and this spec appears in it
Step 2: Analyze Status
Parse each phase:
- Requirements: Count requirements and acceptance criteria
- Design: Check for architecture, components, diagrams, and whether boundary sections are present
- Tasks: Count completed vs total tasks (parse
- [x]vs- [ ]) - Approvals: Check approval status in spec.json
- Boundary context:
- From brief.md: note
Boundary Candidates,Upstream / Downstream, andExisting Spec Touchpointsif present - From design.md: note
Boundary Commitments,Out of Boundary,Allowed Dependencies, andRevalidation Triggersif present - From roadmap.md: note upstream dependencies and whether this spec is adjacent to
Existing Spec Updates
- From brief.md: note
- Revalidation watchlist:
- Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
- Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair
Step 3: Generate Report
Create report in the language specified in spec.json covering:
- Current Phase & Progress: Where the spec is in the workflow
- Completion Status: Percentage complete for each phase
- Task Breakdown: If tasks exist, show completed/remaining counts
- Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
- Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
- Next Actions: What needs to be done next
- Blockers: Any issues preventing progress
Format: Clear, scannable format with emojis for status
Safety & Fallback
Error Scenarios
Spec Not Found:
- Message: "No spec found for
$ARGUMENTS. Check available specs in.kiro/specs/" - Action: List available spec directories
Incomplete Spec:
- Warning: Identify which files are missing
- Suggested Action: Point to next phase command
List All Specs
To see all available specs:
- Run with no argument or use wildcard
- Shows all specs in
.kiro/specs/with their status