feat: add project-level scope assessment to brainstorming pipeline

Brainstorming now assesses whether a project is too large for a single
spec and helps decompose into sub-projects. Spec reviewer checks scope.
Writing-plans has a backstop if brainstorming missed it.
This commit is contained in:
Jesse Vincent
2026-02-08 13:02:17 -08:00
parent b0519329df
commit eac29a909f
3 changed files with 12 additions and 0 deletions

View File

@@ -18,6 +18,10 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
- (User preferences for plan location override this default)
## Scope Check
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
## File Structure
Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.