Prompt file imported from cruujon/SubsidyPayment (.windsurf/workflows/kiro-spec-status.md). Fill in {{arg1}} before use. Copyright stays with the author.

Specification Status

Name: kiro-spec-status
Author: cruujon

<background_information>

Mission: Display comprehensive status and progress for a specification
Success Criteria:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress </background_information>

Execution Steps

Step 1: Load Spec Context

Read .kiro/specs/{{arg1}}/spec.json for metadata and phase status
Read existing files: requirements.md, design.md, tasks.md (if they exist)
Check .kiro/specs/{{arg1}}/ directory for available files

Step 2: Analyze Status

Parse each phase:

Requirements: Count requirements and acceptance criteria
Design: Check for architecture, components, diagrams
Tasks: Count completed vs total tasks (parse - [x] vs - [ ])
Approvals: Check approval status in spec.json

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
Next Actions: What needs to be done next
Blockers: Any issues preventing progress

Critical Constraints

Use language from spec.json
Calculate accurate completion percentages
Identify specific next action commands

Tool Guidance

Read: Load spec.json first, then other spec files as needed
Parse carefully: Extract completion data from tasks.md checkboxes
Use Glob to check which spec files exist

Output Description

Provide status report in the language specified in spec.json:

Report Structure:

Feature Overview: Name, phase, last updated
Phase Status: Requirements, Design, Tasks with completion %
Task Progress: If tasks exist, show X/Y completed
Next Action: Specific command to run next
Issues: Any blockers or missing elements

Format: Clear, scannable format with emojis (✅/⏳/❌) for status

Safety & Fallback

Error Scenarios

Spec Not Found:

Message: "No spec found for {{arg1}}. 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

{ "prompt": "<meta>\ndescription: Show specification status and progress\nargument-hint: <feature-name:{{arg1}}>\n</meta>\n\n# Specification Status\n\n<background_information>\n- **Mission**: Display comprehensive status and progress for a specification\n- **Success Criteria**:\n - Show current phase and completion status\n - Identify next actions and blockers\n - Provide clear visibility into progress\n</background_information>\n\n<instructions>\n## Core Task\nGenerate status report for feature **{{arg1}}** showing progress across all phases.\n\n## Execution Steps\n\n### Step 1: Load Spec Context\n- Read `.kiro/specs/{{arg1}}/spec.json` for metadata and phase status\n- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)\n- Check `.kiro/specs/{{arg1}}/` directory for available files\n\n### Step 2: Analyze Status\n\n**Parse each phase**:\n- **Requirements**: Count requirements and acceptance criteria\n- **Design**: Check for architecture, components, diagrams\n- **Tasks**: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)\n- **Approvals**: Check approval status in spec.json\n\n### Step 3: Generate Report\n\nCreate report in the language specified in spec.json covering:\n1. **Current Phase & Progress**: Where the spec is in the workflow\n2. **Completion Status**: Percentage complete for each phase\n3. **Task Breakdown**: If tasks exist, show completed/remaining counts\n4. **Next Actions**: What needs to be done next\n5. **Blockers**: Any issues preventing progress\n\n## Critical Constraints\n- Use language from spec.json\n- Calculate accurate completion percentages\n- Identify specific next action commands\n</instructions>\n\n## Tool Guidance\n- **Read**: Load spec.json first, then other spec files as needed\n- **Parse carefully**: Extract completion data from tasks.md checkboxes\n- Use **Glob** to check which spec files exist\n\n## Output Description\n\nProvide status report in the language specified in spec.json:\n\n**Report Structure**:\n1. **Feature Overview**: Name, phase, last updated\n2. **Phase Status**: Requirements, Design, Tasks with completion %\n3. **Task Progress**: If tasks exist, show X/Y completed\n4. **Next Action**: Specific command to run next\n5. **Issues**: Any blockers or missing elements\n\n**Format**: Clear, scannable format with emojis (✅/⏳/❌) for status\n\n## Safety & Fallback\n\n### Error Scenarios\n\n**Spec Not Found**:\n- **Message**: \"No spec found for `{{arg1}}`. Check available specs in `.kiro/specs/`\"\n- **Action**: List available spec directories\n\n**Incomplete Spec**:\n- **Warning**: Identify which files are missing\n- **Suggested Action**: Point to next phase command\n\n### List All Specs\n\nTo see all available specs:\n- Run with no argument or use wildcard\n- Shows all specs in `.kiro/specs/` with their status", "variables": [ "arg1" ], "notes": "Show specification status and progress", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/cruujon/SubsidyPayment", "path": ".windsurf/workflows/kiro-spec-status.md", "ref": "bf7dfcd4b25381984887e20fd38da36d9d641e98", "url": "https://github.com/cruujon/SubsidyPayment/blob/bf7dfcd4b25381984887e20fd38da36d9d641e98/.windsurf/workflows/kiro-spec-status.md", "key": "cruujon/SubsidyPayment/.windsurf/workflows/kiro-spec-status.md" } } }

kiro-spec-status

About