Agent Skills › growilabs/growi › kiro-spec-status

kiro-spec-status

GitHub

用于展示 Kiro 规范的状态与进度，分析各阶段完成度、识别阻塞点及依赖上下文，生成包含下一步行动和重新验证需求的清晰报告。

.claude/skills/kiro-spec-status/SKILL.md growilabs/growi

触发场景

用户查询特定规范的当前状态或进度需要检查规范文件的完整性或缺失项查看多个规范的列表及其总体状态

安装

npx skills add growilabs/growi --skill kiro-spec-status -g -y

更多选项

非标准路径

npx skills add https://github.com/growilabs/growi/tree/master/.claude/skills/kiro-spec-status -g -y

不安装直接使用

npx skills use growilabs/growi@kiro-spec-status

指定 Agent (Claude Code)

npx skills add growilabs/growi --skill kiro-spec-status -a claude-code -g -y

安装 repo 全部 skill

npx skills add growilabs/growi --all -g -y

预览 repo 内 skill

npx skills add growilabs/growi --list

SKILL.md

Frontmatter

{
    "name": "kiro-spec-status",
    "description": "Show specification status and progress",
    "allowed-tools": "Read, Glob, Grep",
    "argument-hint": "<feature-name>"
}

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.json for metadata and phase status
Read .kiro/specs/$ARGUMENTS/brief.md if 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.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:

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