rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-04-26 03:29:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add project-level scope assessment to brainstorming pipeline

Browse Source 
Brainstorming now assesses whether a project is too large for a single
spec and helps decompose into sub-projects. Scope check is inline in
the understanding phase (testing showed it was skipped as a separate step).
Spec reviewer also checks scope. Writing-plans has a backstop.
This commit is contained in:
Jesse Vincent
2026-03-06 12:38:04 -08:00
parent daa3fb2322
commit d48b14e5ac
3 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
skills/writing-plans/SKILL.md
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.