From dominion-flow
Starts new milestone cycle for existing projects via questioning, research, requirements, and roadmap. Updates .planning/PROJECT.md goals, creates REQUIREMENTS.md, VISION.md, CONSCIENCE.md, optional research folder.
How this command is triggered — by the user, by Claude, or both
Slash command
/dominion-flow:fire-new-milestoneFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /fire-new-milestone > Start a new milestone through unified flow: questioning -> research -> requirements -> roadmap --- ## Purpose Start a new milestone for an existing project. This is the brownfield equivalent of `/fire-1a-new`. The project exists, PROJECT.md has history. This command gathers "what's next" and takes you through the full cycle. **Creates/Updates:** - `.planning/PROJECT.md` - Updated with new milestone goals - `.planning/research/` - Domain research (optional) - `.planning/REQUIREMENTS.md` - Scoped requirements - `.planning/VISION.md` - Phase structure - `.planning/...
Start a new milestone through unified flow: questioning -> research -> requirements -> roadmap
Start a new milestone for an existing project. This is the brownfield equivalent of /fire-1a-new. The project exists, PROJECT.md has history. This command gathers "what's next" and takes you through the full cycle.
Creates/Updates:
.planning/PROJECT.md - Updated with new milestone goals.planning/research/ - Domain research (optional).planning/REQUIREMENTS.md - Scoped requirements.planning/VISION.md - Phase structure.planning/CONSCIENCE.md - Updated project memoryAfter this command: Run /fire-2-plan [N] to start execution.
arguments:
milestone_name:
required: false
type: string
description: "Optional milestone name (e.g., 'v1.1 Notifications')"
example: "/fire-new-milestone v1.1 Notifications"
MANDATORY FGTAT STEP - Execute these checks before ANY user interaction:
[ -f .planning/PROJECT.md ] || { echo "ERROR: No PROJECT.md. Run /fire-1a-new first."; exit 1; }
Check for active milestone (VISION.md exists):
[ -f .planning/VISION.md ] && echo "ACTIVE_MILESTONE" || echo "READY_FOR_NEW"
If ACTIVE_MILESTONE:
Use AskUserQuestion:
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > NEW MILESTONE |
+------------------------------------------------------------------------------+
Present what shipped:
Last milestone: v[X.Y] [Name] (shipped [DATE])
Key accomplishments:
- [From MILESTONES.md]
- [From MILESTONES.md]
Validated requirements:
- [From PROJECT.md Validated section]
Pending todos:
- [From CONSCIENCE.md if any]
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > QUESTIONING |
+------------------------------------------------------------------------------+
Open the conversation:
Ask inline (freeform, NOT AskUserQuestion):
"What do you want to build next?"
Wait for response. This gives context for intelligent follow-up questions.
Follow the thread:
Based on their response, ask follow-up questions that dig deeper. Use AskUserQuestion with options that probe what they mentioned.
Keep following threads. Each answer opens new threads to explore:
WARRIOR Enhancement - Honesty Protocol:
Before finalizing understanding, acknowledge:
Decision gate:
When ready, use AskUserQuestion:
Parse last version from MILESTONES.md and suggest next:
Use AskUserQuestion:
Update .planning/PROJECT.md with new milestone section:
## Current Milestone: v[X.Y] [Name]
**Goal:** [One sentence describing milestone focus]
**Target features:**
- [Feature 1]
- [Feature 2]
- [Feature 3]
Commit:
git add .planning/PROJECT.md
git commit -m "$(cat <<'EOF'
docs: start milestone v[X.Y] [Name]
[One-liner describing milestone focus]
EOF
)"
Use AskUserQuestion:
If "Research first":
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > RESEARCHING |
+------------------------------------------------------------------------------+
Researching [domain] ecosystem...
Spawn 4 parallel fire-project-researcher agents:
After completion, spawn synthesizer to create RECORD.md.
Adversarial Fact-Check (v11.0):
After the synthesizer writes SYNTHESIS.md, spawn fire-fact-checker:
.planning/research/CONTESTED-CLAIMS.mdSpawning fire-fact-checker for adversarial verification...
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > DEFINING REQUIREMENTS |
+------------------------------------------------------------------------------+
If research exists: Read FEATURES.md and present by category.
If no research: Gather requirements through conversation.
Scope each category:
For each category, use AskUserQuestion with multiSelect:
Generate REQUIREMENTS.md:
Create .planning/REQUIREMENTS.md with:
Commit:
git add .planning/REQUIREMENTS.md
git commit -m "$(cat <<'EOF'
docs: define v[X.Y] requirements
[X] requirements across [N] categories
[Y] requirements deferred to v2
EOF
)"
Display banner:
+------------------------------------------------------------------------------+
| DOMINION FLOW > CREATING ROADMAP |
+------------------------------------------------------------------------------+
Spawning roadmapper...
Spawn fire-roadmapper agent with context:
Handle roadmapper return:
If ## ROADMAP CREATED:
If approved: Commit roadmap.
Update persistent state:
## .claude/dominion-flow.local.md
### Current Milestone
- Version: v[X.Y]
- Name: [Name]
- Phases: [count]
- Requirements: [count]
- Started: {timestamp}
- Status: Ready to plan
- Next: /fire-2-plan [first_phase]
+------------------------------------------------------------------------------+
| DOMINION FLOW > MILESTONE INITIALIZED |
+------------------------------------------------------------------------------+
| |
| v[X.Y] [Name] |
| |
| | Artifact | Location | |
| |----------------|----------------------------- |
| | Project | .planning/PROJECT.md | |
| | Research | .planning/research/ | |
| | Requirements | .planning/REQUIREMENTS.md | |
| | Roadmap | .planning/VISION.md | |
| |
| [N] phases | [X] requirements | Ready to build |
| |
+------------------------------------------------------------------------------+
| NEXT UP |
+------------------------------------------------------------------------------+
| |
| Phase [N]: [Phase Name] - [Goal] |
| |
| -> Run `/fire-1a-discuss [N]` to gather context and clarify approach |
| -> Or run `/fire-2-plan [N]` to plan directly |
| |
| Tip: Run `/clear` first for fresh context window |
| |
+------------------------------------------------------------------------------+
/fire-2-plan [N]/fire-1a-new - Initialize new project (greenfield)/fire-complete-milestone - Archive completed milestone/fire-1a-discuss - Discuss phase before planningfire-roadmapper for roadmap creationfire-project-researcher for domain research@references/ui-brand.mdnpx claudepluginhub thierryn/fire-flow/new-milestoneStarts a new milestone cycle: prompts for milestone name, runs questioning and optional research, then generates scoped requirements and a phased roadmap. Updates PROJECT.md and resets STATE.md.
/new-milestoneStarts a new milestone cycle [name] on an existing project after prior milestone completion. Executes learnship workflow end-to-end with gates, validations, checkpoints, and routing.
/milestone-planCreates or revises a milestone plan with goals, dependencies, risks, and exit criteria.
/planPlans a phase of work in Shipyard project (creates roadmap if needed). Accepts phase-number, --skip-research, --no-discuss flags.