mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-07 05:56:41 +02:00
Garry Tan
db18f0f16c
New gstack-plan template chains /office-hours → /autoplan (CEO + eng + design + DX + codex adversarial), saves the reviewed plan, and reports back to the orchestrator. The orchestrator persists the plan link to its own memory store. 5 tiers now: Simple, Medium, Heavy, Full, Plan. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.0 KiB
1.0 KiB
gstack-plan: Full Review Gauntlet
Injected by the orchestrator when the user wants to plan a Claude Code project. Append to existing CLAUDE.md.
Planning Pipeline
- Read CLAUDE.md and understand the project context.
- Run /office-hours to produce a design doc (problem statement, premises, alternatives).
- Run /autoplan to review the design (CEO + eng + design + DX reviews + codex adversarial).
- Save the final reviewed plan to a file the orchestrator can reference later. Write it to: plans/-plan-.md in the current repo. Include the design doc, all review decisions, and the implementation sequence.
- Report back to the orchestrator:
- Plan file path
- One-paragraph summary of what was designed and the key decisions
- List of accepted scope expansions (if any)
- Recommended next step (usually: spawn a new session with gstack-full to implement)
Do not implement anything. This is planning only. The orchestrator will persist the plan link to its own memory/knowledge store.