Project Scaffold - Greenfield Build Orchestration

Use this skill to build a new application or a major new module from scratch, before code exists. It routes the work to the right architecture skill and scaffolding command, then - in a stack-installed Claude Code project - drives the build itself, slice by slice, from the main session.

Execution modes

DELEGATED vs INLINE - and why detection keys on dispatch capability, not file presence - is the shared policy cross-stack-agents-flow owns. Pick the mode once, before DESIGN, hold it for the run, and apply it to the scaffold:

• DELEGATED (dispatch available) - the main session dispatches greenfield-solution-designer, then runs each slice's main-stack-agents-flow vertical by dispatching that stack's seats directly, never doing their work itself. (This skill and main-stack-agents-flow are manual /-only skills (disable-model-invocation), so a slice runs its vertical by dispatching the seats, not by model-invoking the main-stack-agents-flow skill.)
• INLINE (no dispatch: Cursor, a non-stack project, or a scaffold too small to fan out) - do it all in-session, using brainstorming and writing-plans plus the architecture skills directly, instead of dispatching a designer.

Steps

1. DESIGN - DELEGATED: dispatch greenfield-solution-designer to turn the spec into architecture options. INLINE: brainstorming and writing-plans in-session, to the same end. Either way, get the user's approval on the architecture and the stack before scaffolding anything - greenfield tech choices are the user's, never silently picked.
2. SCAFFOLD - once approved, run the named new-project command (dotnet new ; 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).
3. 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 main-stack-agents-flow vertical). Loop until the spec's first milestone is met.

Per-stack scaffolding