gotalab/cc-sdd / tools/cc-sdd/templates/agents/codex-skills/skills/kiro-spec-status
kiro-spec-status
VerifiedShow specification status and progress
Specification Status
<background_information>
- 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 </background_information>
Step 1: Load Spec Context
- Read
{{KIRO_DIR}}/specs/$1/spec.jsonfor metadata and phase status - Read
{{KIRO_DIR}}/specs/$1/brief.mdif it exists - Read existing files:
requirements.md,design.md,tasks.md(if they exist) - Check
{{KIRO_DIR}}/specs/$1/directory for available files - Read
{{KIRO_DIR}}/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
Safety & Fallback
Error Scenarios
Spec Not Found:
- Message: "No spec found for
$1. Check available specs in{{KIRO_DIR}}/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_DIR}}/specs/with their status
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |