* fix(#1205): roadmapper applies phase_id_convention to generated phase IDs - Add Phase ID Convention section to <phase_identification> block: documents sequential (default) vs milestone-prefixed forms, and instructs the agent to read phase_id_convention from config.json - Update <output_formats> to show both header and checklist forms for sequential and milestone-prefixed conventions with examples (e.g. ### Phase 1-01: Name, - [ ] **Phase 1-01: Name**) - Add TDD regression test tests/bug-1205-roadmapper-convention.test.cjs (5 assertions, confirmed fail-first then pass after fix) - Update tests/agent-size-baseline.json to reflect legitimate growth - Add .changeset/brave-otters-leap.md (Fixed, pr:0 placeholder) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: backfill changeset pr: 1215 for fix/1205 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(#1205): move phase_id_convention regression into roadmapper-granularity.test.cjs lint-regression-test-names rejects new standalone bug-NNNN-*.test.cjs files; regression cases must live in the owning module's test file. Move the 5 phase_id_convention assertions (#1205 regression) from the removed tests/bug-1205-roadmapper-convention.test.cjs into tests/roadmapper-granularity.test.cjs as a new describe block, alongside the existing granularity calibration tests. Also update the allow-test-rule comment to cover both #163 and #1205 surface contracts. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(#1205): fix lint-allow-test-rule-refs for roadmapper-granularity - Add issue ref (see #1205) to allow-test-rule comment in tests/roadmapper-granularity.test.cjs so lint-allow-test-rule-refs passes (new exemptions require #NNN per ADR-456) - Prune stale 'source-text-is-the-product' entry from scripts/lint-allow-test-rule-refs.allowlist.json (ratchet-down; comment now compliant and no longer needs grandfathering) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -209,6 +209,23 @@ Track coverage as you go.
|
||||
- New milestone: Start at 1
|
||||
- Continuing milestone: Check existing phases, start at last + 1
|
||||
|
||||
## Phase ID Convention
|
||||
|
||||
Read `phase_id_convention` from config.json. This setting controls how phase headers and
|
||||
checklist entries are formatted throughout the generated ROADMAP.md.
|
||||
|
||||
| Convention | Summary checklist form | Detail header form |
|
||||
|---|---|---|
|
||||
| `sequential` (default) | `- [ ] **Phase 1: Name**` | `### Phase 1: Name` |
|
||||
| `milestone-prefixed` | `- [ ] **Phase 1-01: Name**` | `### Phase 1-01: Name` |
|
||||
|
||||
When `phase_id_convention` is absent or set to `"sequential"`, use plain sequential phase IDs
|
||||
(e.g. `Phase 1`, `Phase 2`). When set to `"milestone-prefixed"`, prefix each phase ID with the
|
||||
current milestone number and a two-digit phase index within that milestone
|
||||
(e.g. `Phase 1-01`, `Phase 1-02`, `Phase 2-01`). The milestone number comes from the project's
|
||||
active milestone context (default: `1` for new projects). This ensures downstream tools that
|
||||
parse `### Phase N-NN:` headers for milestone-scoped workflows receive correctly prefixed IDs.
|
||||
|
||||
## Granularity Calibration
|
||||
|
||||
Read granularity from config.json. Granularity controls compression tolerance.
|
||||
@@ -310,14 +327,30 @@ After roadmap creation, REQUIREMENTS.md gets updated with phase mappings:
|
||||
|
||||
### 1. Summary Checklist (under `## Phases`)
|
||||
|
||||
Use the form matching `phase_id_convention` from config.
|
||||
|
||||
**Sequential (default — when absent or `"sequential"`):**
|
||||
|
||||
```markdown
|
||||
- [ ] **Phase 1: Name** - One-line description
|
||||
- [ ] **Phase 2: Name** - One-line description
|
||||
- [ ] **Phase 3: Name** - One-line description
|
||||
```
|
||||
|
||||
**Milestone-prefixed (when `phase_id_convention: "milestone-prefixed"`):**
|
||||
|
||||
```markdown
|
||||
- [ ] **Phase 1-01: Name** - One-line description
|
||||
- [ ] **Phase 1-02: Name** - One-line description
|
||||
- [ ] **Phase 1-03: Name** - One-line description
|
||||
```
|
||||
|
||||
### 2. Detail Sections (under `## Phase Details`)
|
||||
|
||||
Use the header form matching `phase_id_convention` from config.
|
||||
|
||||
**Sequential (default):**
|
||||
|
||||
```markdown
|
||||
### Phase 1: Name
|
||||
**Goal**: What this phase delivers
|
||||
@@ -334,7 +367,25 @@ After roadmap creation, REQUIREMENTS.md gets updated with phase mappings:
|
||||
...
|
||||
```
|
||||
|
||||
**The `### Phase X:` headers are parsed by downstream tools.** If you only write the summary checklist, phase lookups will fail.
|
||||
**Milestone-prefixed (when `phase_id_convention: "milestone-prefixed"`):**
|
||||
|
||||
```markdown
|
||||
### Phase 1-01: Name
|
||||
**Goal**: What this phase delivers
|
||||
**Depends on**: Nothing (first phase)
|
||||
**Requirements**: REQ-01, REQ-02
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. Observable behavior from user perspective
|
||||
2. Observable behavior from user perspective
|
||||
**Plans**: TBD
|
||||
|
||||
### Phase 1-02: Name
|
||||
**Goal**: What this phase delivers
|
||||
**Depends on**: Phase 1-01
|
||||
...
|
||||
```
|
||||
|
||||
**The `### Phase X:` headers are parsed by downstream tools.** If you only write the summary checklist, phase lookups will fail. Use the correct form for the configured convention so downstream parsing succeeds.
|
||||
|
||||
### UI Phase Detection
|
||||
|
||||
@@ -476,6 +527,8 @@ Apply phase identification methodology:
|
||||
2. Identify dependencies between groups
|
||||
3. Create phases that complete coherent capabilities
|
||||
4. Check granularity setting for compression guidance
|
||||
5. Read `phase_id_convention` from config (`sequential` or `milestone-prefixed`); apply the
|
||||
matching header and checklist form throughout all output sections
|
||||
|
||||
## Step 5: Derive Success Criteria
|
||||
|
||||
|
||||
Reference in New Issue
Block a user