Skip to content
Development
Skill

/orch-build-mvp

Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.

From plugin
ecc
239k200 skills72 agents109 commands7 hooks
+1
Install
$ npx -y skills add affaan-m/ECC --skill orch-build-mvp --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/orch-build-mvp

Context preview

The summary Claude sees to decide when to auto-load this skill.

Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.

SKILL.md

orch-build-mvp.SKILL.md
name: orch-build-mvp
description: Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
metadata:
  origin: ECC

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
Read more
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin