orch-build-mvp

Name: orch-build-mvp
Rating: 0
Author: Affaan Mustafa

by Affaan Mustafa·8d ago

Orchestrate turning a design document into a working MVP through thin vertical slices, scaffolding, and gated commits.

Automated screen · 自动筛查open source · 开源

Before you install安装前须知

✓No special access needs declared未声明特殊权限需求

Editor's verdict· 编辑结论

Position as a specialized entry point over the more general orch-pipeline skill, so docs can explain it as a preset rather than a standalone system.
— Editorial team · 编辑团队

Install via Skills CLI

Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.

Codex

npx skills add https://github.com/affaan-m/ECC -g -a codex -y

Drop `-g` to install project-locally

✓

Best for适合什么场景

Teams that already have a written design document and want a structured path to a first running slice.
Projects where the value comes from shipping a thin end-to-end path quickly rather than complete layers.
Engineers using a GAN-style generator and evaluator loop and wanting the planner step skipped because the spec already exists.

✗

Not for不适合什么场景

Greenfield work without any spec, design doc, or PRD to drive the slicing from.
Tasks that need a full horizontal layer first, such as building the entire data model before any UI.
Users who want to manually iterate slice by slice without an automated build and evaluator loop.

vs alternativesvs 其他选择

Full compare table完整对比表 →

#1GStack Review

Find the risky changes before the branch lands.

★ 4.9·110k stars

diff · 差异Best first pick for high-signal PR review. It reads the actual diff instead of re-summarizing the whole repo, so the review stays grounded in code that changed. Strongest on trust-boundary cases — SQL injection, auth checks, conditional side-effects — where surface reviewers usually miss the failure mode. Skip it for pure style nits; bring in a linter instead. Try it on a feature branch before relying on it for hot-fix gating.

#2Git Shiproom

Pre-flight every branch before you ask for review.

★ 4.9·13k stars

diff · 差异Best for the narrow gap between "my branch is ready" and "a reviewer can pick it up cold." Runs a pre-flight: dependency drift, missing tests for the changed files, commits that don't match the PR title, and writes a handoff note your reviewer can read in 60 seconds. It is not a code reviewer — it does not audit logic. Use it as the last thing before requesting review, not as a replacement for review itself.

#3Review Radar

Find the bugs, regressions, and missing tests first.

★ 4.8·11k stars

diff · 差异Best when you want PR review insights without committing to a full review workflow. Surfaces the same regression-and-missing-tests signal as gstack-review, but in a quieter, suggestion-only mode — no fix application, no diff edits, no comment threads. Strongest for senior engineers who want a second opinion before they merge their own PR. Weakest when the goal is gating others' code; for that, gstack-review's heavier loop pays off.

Side-by-side compare维度对比

Key differences with same-lane alternatives

	this skill · 当前orch-build-mvp	GStack Review	Git Shiproom	Review Radar
Rating · 评分	0.0	4.9	4.9	4.8
Stars · 星标	215k	110k	13k	11k
Risk · 风险	Automated screen · 自动筛查	Low risk · 低风险	Low risk · 低风险	Low risk · 低风险
Best for · 最适合	Teams that already have a written design document and want a structured path to a first running slice.	Pre-merge PR review	Pre-flight every branch before you ask for review.	Find the bugs, regressions, and missing tests first.
Not for · 不适合	Greenfield work without any spec, design doc, or PRD to drive the slicing from.	Pure style review	Workflows that require stronger human review than this catalog entry documents.	Workflows that require stronger human review than this catalog entry documents.

Audit notes审计备注

last reviewed 2026-06-10 · 复查

Source源码open on GitHub · 公开✓

Author作者community · 社区!

Network网络访问read-only · 只读✓

Filesystem文件写入sandboxed · 沙箱✓

Dependencies依赖audited · 已审计✓

Telemetry遥测none · 无✓