aid-prototype

Prototype (validate a direction, throwaway)

/aid-prototype builds a throwaway model now to de-risk a direction, captures the validation signal, presents it, and hands the real build off. It resolves nothing and its output is not production. For a design you intend to keep and build, use /aid-design. Deeper per-slot guidance: .aid/runtime/templates/shortcut-scaffolding/prototype.md.

• Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> BUILD -> VERIFY (light) -> PRESENT [user decides] -> HANDOFF? -> DONE. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

1. Require a direction. Empty argument -> ask one bootstrapping question ("What direction do you want to validate, and what would tell you it works?") and wait.
2. Capture (thin): direction/hypothesis; fidelity (paper | low-fi | runnable spike, default low-fi); the success signal that would validate it; the scope boundary (what it does NOT attempt -- keeps it throwaway).
3. Pick the path: Fast -- a clear direction + success signal -> build now. Guided -- vague ("prototype something for onboarding") -> scope direction / success signal / fidelity first.
4. Classify complexity (model + effort): simple -> aid-architect at sonnet / medium; complex (a runnable spike, a rich flow) -> opus / high.
5. Consult the Work Initiation Gate, then allocate the work folder + STATE. First run the gate (.aid/runtime/templates/work-initiation-gate.md): bash .aid/runtime/scripts/works/enumerate-works.sh (main tree + every git worktree). Empty -> allocate, no prompt. Works exist -> ask new-vs-continuation; on continuation route to the chosen work's resume door and STOP (allocate nothing); on new work: create and enter the worktree per the gate's § 3a step 2 (worktree-lifecycle.sh create <work-id> <name>, STOP on a non-zero exit or empty path, else enter the resolved path), then allocate (pipeline.path: lite, initiator: aid-prototype, lifecycle: Running, active_skill: aid-prototype; phase not driven). For a runnable spike, associate an opt-in git worktree so the throwaway code is isolated.