project-orchestration

Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skill/project-orchestration/SKILL.md

Quality

Content

77%

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

The body is highly actionable with executable commands and code, and the 8-stage workflow is clearly sequenced with validation and rollback. Its main weaknesses are repetition (stage commands and file paths listed multiple times) and inline detail that belongs in the referenced workflow files, several of which are not present in the bundle.

Suggestions

Eliminate the triplicated stage-command listings: keep them in the Command Reference table and link from Quick Start and the 8-Stage section instead of repeating them.

Move the Context Handoff Pattern examples, comparison table, and Planning Agents Integration into the referenced workflow files, keeping SKILL.md a lean overview.

Verify the referenced workflows/context-handoff.md, workflows/8-stage-delivery.md, and workflows/planning-agents.md actually exist in the bundle, or remove the dangling references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of beginner-concept padding, but it repeats the stage commands three times (Quick Start, Command Reference, and the 8-Stage section) and the File Locations section duplicates the Architecture tree, so it could be tightened considerably.	2 / 3
Actionability	It provides copy-paste-ready bash commands, full TypeScript import/usage examples, and complete command-reference tables with argument signatures, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The 8-stage workflow is explicitly numbered 1-8 and pairs execution with validation (stage-validate), completion, and rollback/abort feedback loops, satisfying the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	References to workflow guides are clearly signaled one level deep and the scripts/ bundle files exist, but the referenced workflows/*.md files are absent from the bundle and substantial inline detail (Context Handoff Pattern, comparison table, Planning Agents Integration) should live in those separate files.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinct, clearly stating what the skill orchestrates, but it omits explicit 'when to use' trigger guidance and relies on somewhat technical keywords rather than natural user phrasing. Adding a Use-when clause and more colloquial trigger terms would raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when coordinating multiple agents to deliver a feature, managing planning handoffs, or running a staged delivery workflow.'

Soften technical jargon with natural phrasings users would say ('planning handoffs', 'agent pipeline', 'feature delivery stages').

Lead with the highest-value trigger ('multi-agent feature delivery') so the most common user request maps clearly to this skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('multi-agent workflows for feature development') and lists multiple concrete mechanisms ('planning agents, context handoff, and stage management'), matching the anchor for several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant domain terms are present ('multi-agent workflows', 'planning agents', 'feature development') but they lean technical; common natural variations a user would actually say are missing, so it sits at 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	'Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management' carves a clear niche unlikely to trigger for unrelated skills, matching the distinct-trigger anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: darrenhinde/OpenAgentsControl
Path: .opencode/skill/project-orchestration/SKILL.md
Commit: 37ca233

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.