Agents & OrchestrationSûr100100/100
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.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ npx arboris-cli@latest install orch-build-mvpaffaan-m
affaan-m/ECC
Contenu à copier
---
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
```Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Orch Build Mvp
The user has a **design / spec document** (SDD, PRD, system_design) and wants a
Takes a doc path as its argument, e.g. `civicpulse/docs/SDD-v0.6.md`.
**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.
Comment utiliser Orch Build Mvp
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Orch Build Mvp
Dis simplement à ton agent quelque chose comme :
Applique le skill orch-build-mvp à cette tâche
Utilise orch-build-mvp pour améliorer cette implémentation
Passe en revue ce sujet avec orch-build-mvp
Skills liés à Orch Build Mvp
Acceleration (Microsoft)
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.Account Overview (Microsoft)
Create a synthetic Acme account overview and identify evidence that merits seller attention.Acroform Writer (Microsoft)
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.