kiro-spec-status

Name: kiro-spec-status
Author: gotalab

3.6kstars271forks

How to install kiro-spec-status?

gotalab/cc-sdd/kiro-spec-status

$npx -y skills add gotalab/cc-sdd --skill kiro-spec-status

Installs into the current project.

Summary

Show specification status and progress

Files · 1

View on GitHub

SKILL.md

1	# Specification Status
2
3	<background_information>
4	- Success Criteria:
5	- Show current phase and completion status
6	- Identify next actions and blockers
7	- Provide clear visibility into progress
8	- Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available
9	</background_information>
10
11	<instructions>
12	## Execution Steps
13
14	### Step 1: Load Spec Context
15	- Read `{{KIRO_DIR}}/specs/$1/spec.json` for metadata and phase status
16	- Read `{{KIRO_DIR}}/specs/$1/brief.md` if it exists
17	- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)
18	- Check `{{KIRO_DIR}}/specs/$1/` directory for available files
19	- Read `{{KIRO_DIR}}/steering/roadmap.md` if it exists and this spec appears in it
20
21	### Step 2: Analyze Status
22
23	Parse each phase:
24	- Requirements: Count requirements and acceptance criteria
25	- Design: Check for architecture, components, diagrams, and whether boundary sections are present
26	- Tasks: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)
27	- Approvals: Check approval status in spec.json
28	- Boundary context:
29	- From brief.md: note `Boundary Candidates`, `Upstream / Downstream`, and `Existing Spec Touchpoints` if present
30	- From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present
31	- From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`
32	- Revalidation watchlist:
33	- Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
34	- Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair
35
36	### Step 3: Generate Report
37
38	Create report in the language specified in spec.json covering:
39	1. Current Phase & Progress: Where the spec is in the workflow
40	2. Completion Status: Percentage complete for each phase
41	3. Task Breakdown: If tasks exist, show completed/remaining counts
42	4. Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
43	5. Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
44	6. Next Actions: What needs to be done next
45	7. Blockers: Any issues preventing progress
46
47	</instructions>
48
49	## Safety & Fallback
50
51	### Error Scenarios
52
53	Spec Not Found:
54	- Message: "No spec found for `$1`. Check available specs in `{{KIRO_DIR}}/specs/`"
55	- Action: List available spec directories
56
57	Incomplete Spec:
58	- Warning: Identify which files are missing
59	- Suggested Action: Point to next phase command
60
61	### List All Specs
62
63	To see all available specs:
64	- Run with no argument or use wildcard
65	- Shows all specs in `{{KIRO_DIR}}/specs/` with their status

People who liked this also viewed

6 picks

Type

kiro-spec-status

3.6kstars271forks

View on GitHub

How to install kiro-spec-status?

gotalab/cc-sdd/kiro-spec-status

$npx -y skills add gotalab/cc-sdd --skill kiro-spec-status

Installs into the current project.

Summary

Show specification status and progress

Files · 1

View on GitHub

SKILL.md

1	# Specification Status
2
3	<background_information>
4	- Success Criteria:
5	- Show current phase and completion status
6	- Identify next actions and blockers
7	- Provide clear visibility into progress
8	- Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available
9	</background_information>
10
11	<instructions>
12	## Execution Steps
13
14	### Step 1: Load Spec Context
15	- Read `{{KIRO_DIR}}/specs/$1/spec.json` for metadata and phase status
16	- Read `{{KIRO_DIR}}/specs/$1/brief.md` if it exists
17	- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)
18	- Check `{{KIRO_DIR}}/specs/$1/` directory for available files
19	- Read `{{KIRO_DIR}}/steering/roadmap.md` if it exists and this spec appears in it
20
21	### Step 2: Analyze Status
22
23	Parse each phase:
24	- Requirements: Count requirements and acceptance criteria
25	- Design: Check for architecture, components, diagrams, and whether boundary sections are present
26	- Tasks: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)
27	- Approvals: Check approval status in spec.json
28	- Boundary context:
29	- From brief.md: note `Boundary Candidates`, `Upstream / Downstream`, and `Existing Spec Touchpoints` if present
30	- From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present
31	- From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`
32	- Revalidation watchlist:
33	- Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
34	- Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair
35
36	### Step 3: Generate Report
37
38	Create report in the language specified in spec.json covering:
39	1. Current Phase & Progress: Where the spec is in the workflow
40	2. Completion Status: Percentage complete for each phase
41	3. Task Breakdown: If tasks exist, show completed/remaining counts
42	4. Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
43	5. Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
44	6. Next Actions: What needs to be done next
45	7. Blockers: Any issues preventing progress
46
47	</instructions>
48
49	## Safety & Fallback
50
51	### Error Scenarios
52
53	Spec Not Found:
54	- Message: "No spec found for `$1`. Check available specs in `{{KIRO_DIR}}/specs/`"
55	- Action: List available spec directories
56
57	Incomplete Spec:
58	- Warning: Identify which files are missing
59	- Suggested Action: Point to next phase command
60
61	### List All Specs
62
63	To see all available specs:
64	- Run with no argument or use wildcard
65	- Shows all specs in `{{KIRO_DIR}}/specs/` with their status

People who liked this also viewed

6 picks

Type