fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: strip residual Phase/Plan refs from guides

Browse Source 
Five spots across three guides referenced the original implementation
phasing (Plan-N / Phase-N nomenclature) from the template's setup era.
Now that the template-reset epic completed and the setup history was
archived, these refs are dead vocabulary for fresh consumers.

guides/scaffolding-a-feature.md:
  - "real repo body is a Phase-1 stub" -> "real repo body is a stub"
  - "## Phase-1 scope (intentionally limited)" -> "## Scope (intentionally limited)"
  - "manually authored as part of Phase-2 wiring" -> "manually authored
    as part of the post-scaffold wiring"

guides/adding-a-feature.md:
  - "the generator's Phase-1 scope doesn't fit" -> "the generator's
    default scope doesn't fit"

guides/tdd-workflow.md:
  - "**File naming convention (post-Plan-8):**" -> "**File naming
    convention:**"

The Plan-9 refs in docs/architecture/data-flow-explainer.html will be
handled separately along with that file's other staleness in the
next commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Danijel Martinek
2026-05-13 17:01:17 +02:00
parent 89d47cce5c
commit 03d4e0cbc8
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guides/adding-a-feature.md
View File

@@ -9,7 +9,7 @@ by one package under `packages/<feature>/`.
> `navigation` reference shape (DI, tRPC router with tests, span + capture
> sandwich, dev seed, contract suite). See
> [Scaffolding a Feature](./scaffolding-a-feature.md). Use this guide when
> the generator's Phase-1 scope doesn't fit — multi-entity layouts, custom
> the generator's default scope doesn't fit — multi-entity layouts, custom
> shapes, or extending an existing feature — or when you need to understand
> what the generator emits and why.