CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, well-structured thin-wrapper skill: lean body, explicit gates and feedback loop, concrete command with defaults, and clean delegation to the engine skill. The only minor gap is that the primary executable step relies on the external orch-pipeline skill and a placeholder brief.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes competence: every line carries operational data (phase mask, default flags, gates, file paths) with zero padding or explanation of known concepts.

5 / 5

Actionability

Provides a concrete copy-paste-ready command ('/gan-build "<one-line brief>" --skip-planner' with --max-iterations, --pass-threshold, --eval-mode defaults) and real file paths, but the core step delegates to the external orch-pipeline engine and the brief remains a placeholder.

4 / 5

Workflow Clarity

The sequence is explicit with named validation gates ('Stop at Gate 1 (slice plan) and Gate 2 (pre-commit)') and a built-in feedback loop ('writes feedback-NNN.md until the score passes or plateaus'), plus a worked example tracing the full flow.

5 / 5

Progressive Disclosure

Under 50 lines with no need for bundle files (none exist), well-organized sections, and a single clearly-signaled one-level-deep reference to ../orch-pipeline/SKILL.md.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that states concrete pipeline actions, an explicit 'Use when' trigger clause, and a well-differentiated niche. Only minor synonym coverage is missing in the trigger terms.

DimensionReasoningScore

Specificity

The description enumerates the full pipeline concretely — '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' — covering every phase with no gaps.

5 / 5

Completeness

Both what ('orchestrate bootstrapping a working MVP... generator-evaluator build loop with review and gated feat commits') and when ('Use when a design or spec document must become a running MVP') are explicitly and concretely stated.

5 / 5

Trigger Term Quality

Natural terms like 'MVP', 'spec document', 'SDD/PRD', and 'design' are present, but common synonyms such as 'requirements document', 'prototype', or 'build an app' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — turning a spec document into a running MVP via planned vertical slices — anchored by distinctive artifacts (SDD/PRD, vertical slices), minimizing overlap with generic build or review skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

skills/orch-build-mvp/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.