governance: add planning/architecture rule (plan ahead, module map, avoid refactors); propagate to system prompts, AGENTS templates, proposal, and plan

This commit is contained in:
2025-09-17 10:33:57 -05:00
parent fae0f5b413
commit c655476699
10 changed files with 47 additions and 3 deletions

View File

@@ -41,3 +41,8 @@ This file is copied by scaffolding into new projects. Edit to suit the project w
- Safety first; speed second. No technical debt, ever.
- Do not defer tests, docs, or clarity/maintainability refactors.
- Practice TDD (tests first) and keep docs up to date with changes.
## Planning and Architecture
- Plan ahead via Questions → Proposal → Plan to align before coding.
- Maintain an architecture/module map and clear module boundaries.
- Implement module-by-module; refactor only when new information requires plan/doc updates.