kiro-discovery

1# Discovery
2 
3<background_information>
4- **Success Criteria**:
5  - Correct action path or work decomposition identified based on existing project state
6  - User's intent clarified through questions, not assumptions
7  - Output is an actionable next step (not just a description)
8</background_information>
9 
10<instructions>
11 
12## Step 1: Lightweight Scan
13 
14Gather **only metadata** to determine the action path. Do NOT read full file contents yet.
15 
16- **Specs inventory**: Scan `{{KIRO_DIR}}/specs/*/spec.json` for `name`, `phase` fields and `approvals` status. Note feature names and their current status.
17- **Steering existence**: Check which files exist in `{{KIRO_DIR}}/steering/` (product.md, tech.md, structure.md, roadmap.md). Do NOT read their contents yet.
18- **Roadmap check**: If `{{KIRO_DIR}}/steering/roadmap.md` exists, read it. This contains project-level context (approach, scope, constraints, spec list) from a previous discovery session. Use it to restore project context.
19- **Top-level structure**: List the project root directory to note key directories and files. Do NOT recurse into subdirectories.
20 
21This step should consume minimal context. If `specs/` is empty and no steering exists, note "greenfield project" and move to Step 2.
22 
23## Step 2: Determine Action Path
24 
25Based on the user's request and the metadata from Step 1, determine which path applies:
26 
27**Path A: Existing spec covers this**
28- The request is an extension, enhancement, or fix within an existing spec's domain
29…