You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: add brownfield workflow page rendering and SPA routing
- Add brownfield-workflow.adoc to render-docs.js prebuild step
- Register /brownfield route in main.js and router.js
- Fix AsciiDoc cross-links to use SPA hash routes (#/brownfield,
#/workflow) instead of .adoc file references
Without this, the brownfield page returns 404 on the deployed site.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|Follow link:spec-driven-workflow.adoc[the standard workflow] from Step 3 (PRD) or Step 8 (Implementation), depending on whether you are adding new features or fixing bugs.
155
+
|Follow link:#/workflow[the standard workflow] from Step 3 (PRD) or Step 8 (Implementation), depending on whether you are adding new features or fixing bugs.
Copy file name to clipboardExpand all lines: docs/spec-driven-workflow.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Click on any anchor to see its full definition on the Semantic Anchors website.
31
31
[IMPORTANT]
32
32
====
33
33
This workflow is designed for greenfield projects built from scratch with AI assistance.
34
-
For existing codebases, see link:brownfield-workflow.adoc[Adapting the Workflow to Brownfield Projects].
34
+
For existing codebases, see link:#/brownfield[Adapting the Workflow to Brownfield Projects].
35
35
====
36
36
37
37
== The Key Principle: Small Steps, High Autonomy
@@ -434,7 +434,7 @@ Consider assigning different AI models to different review roles.
434
434
Run ATAM reviews after each major architectural change, not just once.
435
435
Groom the backlog more frequently as the project grows.
436
436
*Legacy codebases*:: This workflow assumes you start from scratch.
437
-
See link:brownfield-workflow.adoc[Adapting the Workflow to Brownfield Projects] for a dedicated guide covering reverse engineering, baseline test coverage, and incremental migration using bounded contexts.
437
+
See link:#/brownfield[Adapting the Workflow to Brownfield Projects] for a dedicated guide covering reverse engineering, baseline test coverage, and incremental migration using bounded contexts.
438
438
*Frontend / HTML applications*:: This workflow works well for backend code, CLIs, and libraries where the compiler and TDD provide strong error correction.
439
439
Frontend applications can be built with the same approach, but consistent UI is harder to verify automatically.
440
440
The error correction layers that make backend development reliable (compiler errors, test failures) have no direct equivalent for visual consistency.
@@ -532,7 +532,7 @@ Start with the Socratic Method for requirements and see where it leads.
532
532
If you discover anchors that work well in your workflow, https://github.com/LLM-Coding/Semantic-Anchors/blob/main/CONTRIBUTING.md[contribute them to the collection].
533
533
534
534
Once you are comfortable with this greenfield workflow, you can adapt it to existing codebases.
535
-
See link:brownfield-workflow.adoc[Adapting the Workflow to Brownfield Projects] for a step-by-step guide.
535
+
See link:#/brownfield[Adapting the Workflow to Brownfield Projects] for a step-by-step guide.
0 commit comments