kiro-spec-status
Show specification status and progress
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- kiro-spec-status
- description
- Show specification status and progress
- allowed-tools
- Read, Glob, Grep
- argument-hint
- <feature-name>
03 SKILL.md 正文
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_DIR}}/specs/$ARGUMENTS/spec.jsonfor metadata and phase status - Read
{{KIRO_DIR}}/specs/$ARGUMENTS/brief.mdif it exists - Read existing files:
requirements.md,design.md,tasks.md(if they exist) - Check
{{KIRO_DIR}}/specs/$ARGUMENTS/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
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_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
04 同仓库更多 Skills
kiro-spec-init
暂无简介
kiro-spec-init
暂无简介
sb-verify-completion
Consequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
sb-validate-implementation
Validate completed Tasks against active Requirement IDs and record completion on GO under an explicit lifecycle-validation request or ordinary Drive authority. Also owns completion withdrawal under an evidenced Drive replan recovery handoff. For a consequence-free claim check, use sb-verify-completion.
sb-validate-design
Independently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
sb-steering
Maintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.