scope

Run /scope with a short description of your product. It asks batched decision panel questions about business goals and capabilities, recommends a build approach and workflow tier, then writes an ordered feature scope to docs/scope/scope.md.

Plan creates a new scope from a product sized idea, replan runs with no argument on an existing scope to reconcile shipped work and queue the next slice, and add enrolls one named feature as a single coarse row without replanning.

Yes. Brownfield mode enrolls already built features as existing or in-progress from MEMORY.md and a code scan, while monorepo mode plans per workspace under docs/scope/<workspace>/ with a top level index mapping rollups.

Tracer Bullet proves the whole stack connects with one thin real end to end slice, suiting production builds. Skateboard ships the smallest genuinely usable product first, cutting structure like teams or roles, suiting fast validation of one core loop.

It never picks tools, providers, or libraries; those decisions belong to the /architect skill per feature. It also writes only scope files, never specs, code, or MEMORY.md, and keeps atomic build tasks inside specs rather than the scope.