Project Build From Scratch - Greenfield Design, Scaffold, Build

Use this skill to build a new application or a major new module from scratch, before code exists. The design happens here, in-session - there is no dispatched greenfield seat: with no code to read, a design pass reasons from the spec that is already in this conversation, and its options come back to the user anyway. The frontmatter pins the invoking turn to opus/xhigh, so DESIGN runs on the architect's budget regardless of the session model (the pin lasts the turn - after the user's pick, orchestration resumes on the session model, which is fine: scaffold and build are dispatch mechanics).

Steps

1. DESIGN - in-session, on the pinned turn

Turn the spec into 2-3 reasoned architecture options - stack, architecture style, folder/module shape, state and persistence approach - each with its tradeoffs, using the brainstorming discipline plus the stack's architecture skills (the per-stack table below names them). Ground every option in the house skills, not recall. A spec gap that blocks the design is a question to the user (the superpowers brainstorming + AskUserQuestion path), never a guess. Multi-stack designs name the seam and its producer/consumer direction up front - the build step will run it producer-first per project-task-flow.

2. THE PICK - hard gate

Present the options; the user chooses the architecture and the stack. Greenfield tech choices are the user's, never silently picked - nothing is scaffolded before this gate.

3. SCAFFOLD

Run the named new-project command (dotnet new <template>; ng new; ionic start for Ionic), establish the structure from the chosen architecture skill, and wire the baseline - DI, config, a test project, formatter/analyzer config - via the stack's setup skills (dotnet-project-setup + dotnet-code-quality on .NET).

4. BUILD - slice by slice

For each vertical slice, dispatch that slice's stack seats directly from the main session - its designer, then implementer(s), then verifier (the domain-trio vertical - project-task-flow's references/domain-trio-protocol.md); reds route to the matching resolver. A multi-stack slice runs producer-first with the recorded interface, per project-task-flow. Loop until the spec's first milestone is met. (INLINE fallback - Cursor, or a scaffold too small to fan out: do the slices in-session with writing-plans + the architecture skills instead of dispatching.)