CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-orchestrate

Turns the current session into the operator's SDLC proxy for parallel PRP workstreams in isolated worktrees. It owns the combined outcome, steers autonomous deliveries, holds human and merge gates, verifies proof, and sequences merges. Use when the user wants to "spawn N agents in separate worktrees", "run prp-issue on these issues in parallel", "orchestrate these features", "act as my orchestrator", "coordinate agents through the PRP pipeline", "ship these issues in parallel", or invokes $prp-orchestrate.

78

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

The content is a lean, highly actionable orchestration runbook with a clear sequenced workflow and strong validation gates. Its only real gap is a referenced template file that is not present in the bundle.

Suggestions

Ship templates/orchestration-run.md alongside the skill — the body marks it as the required durable run format and instructs reading it before creating or closing a run, so its absence is a broken reference.

Confirm the $prp-worktree create/remove commands in references/launching.md resolve to a real skill or helper available to the orchestrator, since the cleanup and checkout steps depend on them.

DimensionReasoningScore

Conciseness

Dense imperative prose with no padding and no explanation of concepts Claude already knows; every section, including the 7-question design gate, earns its tokens.

5 / 5

Actionability

Provides concrete executable commands (the store-resolver bash block, 'gh pr diff <n> --name-only', 'git worktree list'), exact per-step owner contracts, and a referenced file with copy-paste verification commands.

5 / 5

Workflow Clarity

Sections 1–7 form a clear sequence with explicit validation checkpoints (first-gate approval, current-head re-review and CI recheck before each merge) and feedback loops (rebase → resolve conflicts → validate → push) for the batch/destructive merge operations.

5 / 5

Progressive Disclosure

The body is a well-signaled overview pointing one level deep to references/launching.md and templates/orchestration-run.md, but templates/orchestration-run.md is referenced and treated as required yet is absent from the bundle, leaving a broken navigation target.

4 / 5

Total

19

/

20

Passed

Description

100%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.

The description is lean, specific, and answers both what and when with a rich set of natural trigger phrases and the skill's invocation name. It is highly distinctive within the PRP skill family.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'owns the combined outcome', 'steers autonomous deliveries', 'holds human and merge gates', 'verifies proof', 'sequences merges' — giving comprehensive coverage of the orchestrator's responsibilities.

5 / 5

Completeness

Explicitly answers both what (SDLC proxy for parallel PRP workstreams) and when ('Use when the user wants to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quoted natural phrases a user would actually say ('spawn N agents in separate worktrees', 'orchestrate these features', 'act as my orchestrator', 'ship these issues in parallel') plus the explicit $prp-orchestrate invocation, covering synonyms and the skill name.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — parallel PRP orchestration in isolated worktrees — with distinctive triggers unlikely to fire for sibling single-workstream PRP skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Wirasm/prp
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.