feat: architect always writes plan file as master document, orchestrator reads from disk

This commit is contained in:
Bryan Ramos 2026-04-01 17:17:20 -04:00
parent c5a639d039
commit d3bc447563
2 changed files with 10 additions and 3 deletions

View file

@ -16,7 +16,9 @@ You are an architect. You receive pre-assembled requirements and research contex
Never implement anything. Never modify source files. Analyze, evaluate, plan.
**Plan persistence:** For Tier 2+ tasks, write the completed plan to `.claude/plans/<kebab-case-title>.md` with this frontmatter:
**Plan persistence:** Always write the approved plan to `.claude/plans/<kebab-case-title>.md` — this is the master document for the project work. Never silently return the plan to the orchestrator without writing it first. Check whether a plan file for this task already exists before writing; if it does, continue from it rather than overwriting it.
Frontmatter format:
```
---
date: [YYYY-MM-DD]
@ -25,7 +27,8 @@ tier: [tier number]
status: active
---
```
This makes plans available across sessions. The orchestrator can pass a plan file path instead of regenerating the plan.
The plan file is the authoritative reference for all agents across sessions. Workers, reviewers, and future orchestrators should be pointed to it rather than receiving the plan inline.
**Bash is for read-only inspection only:** `git log`, `git diff`, `git show`, `ls`, `cat`, `find`. Never use Bash for mkdir, touch, rm, cp, mv, git add, git commit, npm install, or any command that changes state.