Orch Build Mvp
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review and gated feat commits. Use when a design or spec document must become a running MVP through planned vertical slices.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Orch Build Mvp when an AI agent needs a reusable SKILL.md workflow for this job: Orchestrate bootstrapping a working MVP from a design or spec document — ingest the SDD/PRD, plan thin vertical slices, scaffold the first end-to-end slice, then drive a generator-evaluator build loop with review and gated feat commits. Use when a design or spec document must become a running MVP through planned vertical slices.
When not to use it
Skip Orch Build Mvp when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/orch-build-mvp # Save SKILL.md to ~/.claude/skills/orch-build-mvp/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/orch-build-mvp/SKILL.md. For a shared project, commit the folder at .claude/skills/orch-build-mvp/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Orch Build Mvp skill for this task: The user has a design / spec document (SDD, PRD, systemdesign) and wants a. Confirm any required inputs or files before making changes.
What supports this recommendation?
67/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 72/100
- Practical detail
- 62/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# orch-build-mvp
Actor · action · target: **orch · build · mvp**. Thin wrapper over the shared engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
## When to Use
- The user has a **design / spec document** (SDD, PRD, system_design) and wants a working vertical slice bootstrapped from it. - Takes a doc path as its argument, e.g. `civicpulse/docs/SDD-v0.6.md`.
## Operation settings
- **Default size floor:** large — this is the full pipeline including Scaffold. - **Phase mask:** 0 (read the spec) → 1 → 2 (heavy) → 3 (scaffold) → 4 → 5 → 6. - **First move (phase 0 → 2):** read the doc; extract scope, locked decisions, and the feature list; order it into **thin vertical slices** (one end-to-end path first, not all-models-then-all-views). Phase 3 stands up that first slice.
## How It Works
1. Run the `orch-pipeline` engine with the settings above. 2. **Reuse the existing GAN harness** instead of hand-rolling an iterate loop: - Translate the SDD into `gan-harness/spec.md` + `gan-harness/eval-rubric.md` (this stands in for what `gan-planner` would generate — you already have the spec). - Drive the build with `/gan-build "<one-line brief>" --skip-planner` (defaults: `--max-iterations 15`, `--pass-threshold 7.0`, `--eval-mode playwright`; use `--eval-mode code-only` for non-UI slices). - That command runs the `gan-generator` → `gan-evaluator` loop and writes `gan-harness/feedback/feedback-NNN.md` until the score passes or plateaus. 3. Stop at **Gate 1** (slice plan) and **Gate 2** (pre-commit). Commit the scaffold and each slice as separate `feat:` commits. 4. Add `security-reviewer` for any slice touching a security trigger.
## Example
``` orch-build-mvp: civicpulse/docs/SDD-v0.6.md → read SDD → slice list (vertical) → scaffold slice 1 [GATE 1: approve] → /gan-build --skip-planner (generator → evaluator loop) scores vs spec → review → commit feat: [GATE 2: confirm] → next slice ```
Intended uses
- The user has a design / spec document (SDD, PRD, systemdesign) and wants a
- Takes a doc path as its argument, e.g. civicpulse/docs/SDD-v0.6.md.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.