52 lines
2.7 KiB
Markdown
52 lines
2.7 KiB
Markdown
---
|
|
name: create-roadmap
|
|
description: Create a minimal roadmap scaffold with goals, Phases, Milestones, Tasks, active candidates, and explicit user-stated dependencies.
|
|
---
|
|
|
|
# Create Roadmap
|
|
|
|
## Purpose
|
|
|
|
Create `agent-roadmap/` as a lightweight long-term map. The primary direction is **verification gate minimization**: roadmap creation must not introduce implementation locks, approval chains, mandatory SDDs, consistency preflights, or evidence-format gates.
|
|
|
|
## Structure
|
|
|
|
- `ROADMAP.md`: overall goal and Phase links.
|
|
- `priority-queue.md`: lane order and only explicit user-stated blockers.
|
|
- `current.md`: local active Phase and Milestone candidates.
|
|
- `phase/<phase>/PHASE.md`: one Phase goal and Milestone links.
|
|
- `phase/<phase>/milestones/<milestone>.md`: goal, state, optional promotion notes, decisions, optional design references, scope, functional Tasks, exclusions, and context.
|
|
- `sdd/.../SDD.md`: optional design reference only when requested or materially useful.
|
|
- `archive/...`: completed or discarded snapshots.
|
|
|
|
## Rules
|
|
|
|
- Use the smallest number of Phases and Milestones that explains the actual work.
|
|
- Prefer existing project terminology.
|
|
- Use `[스케치]`, `[계획]`, `[진행중]`, `[검토중]`, `[완료]`, `[보류]`, or `[폐기]`.
|
|
- A sketch records unclear scope; it is not an approval gate.
|
|
- Record only directly required user-owned product decisions under `결정 사항`.
|
|
- Create an SDD only when the user asks or a large contract/lifecycle change benefits materially from one. SDD status never blocks implementation.
|
|
- Create a queue blocker or workspace lock only for a dependency explicitly stated by the user.
|
|
- Functional verification belongs on the relevant Task only when actually needed.
|
|
- `[검토중]` is optional; a completed Milestone may move directly to `[완료]`.
|
|
|
|
## Procedure
|
|
|
|
1. Confirm that an existing roadmap will not be overwritten.
|
|
2. Read the project overview and inspect only the top-level structure needed to identify domains.
|
|
3. Create the smallest Phase → Milestone → Epic → Task hierarchy.
|
|
4. Create active current links and a minimal queue.
|
|
5. Add optional design references and explicit dependencies only when justified above.
|
|
6. Validate links, ids, status values, and `git diff --check`.
|
|
|
|
## Prohibited
|
|
|
|
- Do not create `구현 잠금`, SDD lock, approval checklist, USER_REVIEW gate, mandatory preflight, Evidence Map requirement, or spec-sync gate.
|
|
- Do not create documents or empty sections solely to satisfy a template.
|
|
- Do not infer dependencies or execution blockers.
|
|
- Do not overwrite an existing roadmap; use `update-roadmap` instead.
|
|
|
|
## Output
|
|
|
|
Report created files, active candidates, explicit dependencies, optional design references, and unresolved product decisions. Do not report lock or gate counts.
|