Skip to content
cccskills
FreePublished on GitHub

kiro-spec-status

Review specification files to see the current phase, completion levels, and remaining tasks. Get a progress report that identifies next steps, blockers, dependencies, and related specifications that may need checking after changes.

OriginalShow the original description

Show specification status and progress

gotalab/cc-sdd
See how to install

Good for

  • Check a specification’s progress and remaining tasks
  • Identify next steps and blockers
  • Review related work that may need checking after changes
  • View the status of all specifications

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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>
<instructions> ## Execution Steps

Step 1: Load Spec Context

  • Read {{KIRO_DIR}}/specs/$1/spec.json for metadata and phase status
  • Read {{KIRO_DIR}}/specs/$1/brief.md if 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.md if 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, and Existing Spec Touchpoints if present
    • From design.md: note Boundary Commitments, Out of Boundary, Allowed Dependencies, and Revalidation Triggers if present
    • From roadmap.md: note upstream dependencies and whether this spec is adjacent to Existing Spec Updates
  • 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:

  1. Current Phase & Progress: Where the spec is in the workflow
  2. Completion Status: Percentage complete for each phase
  3. Task Breakdown: If tasks exist, show completed/remaining counts
  4. Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
  5. Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
  6. Next Actions: What needs to be done next
  7. Blockers: Any issues preventing progress
</instructions>

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

cc-sdd-new-agent

FreeSummary

Add coding-agent support to cc-sdd through a documented workflow. Research the agent’s official formats, prepare an integration plan, implement registry entries and templates, and verify generated files, including Japanese and English output.

  • Adding support for a new coding agent
  • Adding an agent variant with subagent support
  • Planning migration to SKILL.md-based templates
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

kiro-debug

FreeSummary

Investigate blocked implementation work and recurring failures using error output, code changes, configuration, and dependency evidence. Get a root cause report with a focused repair plan, verification steps, and a recommendation to retry, block, or seek human input.

  • Investigating an implementation blocker
  • Finding why repeated fixes keep failing
  • Checking runtime and dependency conflicts
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

kiro-discovery

FreeSummary

Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.

  • Clarify a development idea before defining requirements
  • Choose between updating a specification and implementing directly
  • Split a large request into features with explicit dependencies
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

kiro-impl

FreeSummary

Implement approved development tasks one at a time using test-driven development, which starts with a failing test. Process all pending tasks or selected ones, check changes against requirements and design, and update progress after review and completion verification.

  • Working through all approved pending tasks
  • Implementing selected task numbers
  • Developing features with tests written first
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

kiro-impl

FreeSummary

Implement approved tasks through test-driven development, writing tests before code. Run all pending tasks sequentially with subagents or select tasks for direct execution, then track completion using reviews and verification evidence.

  • Running all pending approved implementation tasks
  • Implementing selected tasks by number
  • Developing features with tests written first
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

kiro-impl

FreeSummary

Implement approved tasks using test-driven development, writing tests before code. Run all pending tasks one at a time or select specific tasks, with configurable review and verification before updating completion status.

  • Implement all pending tasks from an approved plan
  • Work on selected task numbers
  • Develop features by writing tests before code
gotalab/cc-sdd3.7KUpdated Oct 22, 2026

See all skills by gotalab

Report a problem with this skill