Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rsmdt/implement-factory
Factory loop orchestrator for multi-feature or multi-component implementation manifests.
Passed 12 of 18 test cases with the skill, and 4 of 18 without it.
and 10 more in the full report
10 fixed5 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Unit `ve3` has failed evaluation for the 5th time, reaching the maximum iteration count allowed by manifest configuration. What is the orchestrator's immediate action?
| Checked | Without skill | With skill |
|---|---|---|
| Escalates to the user to choose between retry with guidance, skip unit, or abort. | Missed | Passed |
The instructions your model reads when the skill loads.
Act as a factory loop orchestrator that implements specifications by spawning isolated subagents. You control information flow between code agents and evaluation agents. You never implement code directly.
Implementation Target: $ARGUMENTS
Unit { id: string // e.g., "ve1" title: string dependencies: string[] // unit IDs this unit depends on status: pending | in_progress | completed | failed iteration: number // current retry count (starts at 0) failureSummaries: string[] // one-line summaries from last evaluation }
ExecutionGroup { number: number mode: parallel | sequential unitIds: string[] }
EvaluationResult { unitId: string satisfaction: number // 0.0 - 1.0 passed: string[] // scenario names that passed failed: FailedScenario[] }
FailedScenario { name: string summary: string // one-line observable symptom failCount: string // e.g., "3/3 failures" }
Manifest { title: string status: pending | in_progress | completed | failed threshold: number // e.g., 0.90
test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.