task-orchestration
Documentation-first task execution with quality checks and progress tracking. Use when working with task lists, implementing features, or executing multi-step work to ensure systematic completion with proper documentation review.
71
64%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/product-design/skills/task-orchestration/SKILL.mdQuality
Discovery
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 has good structure with explicit 'Use when' guidance and covers both what and when adequately. However, it lacks concrete specific actions and uses somewhat generic terminology that could cause conflicts with other task-management or development skills. The trigger terms are reasonable but could benefit from more natural user language variations.
Suggestions
Add more specific concrete actions like 'creates task checklists', 'validates against documentation', 'tracks completion status', or 'generates progress reports'
Include additional natural trigger terms users might say: 'todo list', 'checklist', 'step-by-step implementation', 'systematic workflow', 'project tracking'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (task execution, documentation) and some actions (quality checks, progress tracking), but lacks concrete specific actions like 'create task lists', 'update documentation', or 'mark tasks complete'. | 2 / 3 |
Completeness | Clearly answers both what ('Documentation-first task execution with quality checks and progress tracking') and when ('Use when working with task lists, implementing features, or executing multi-step work') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'task lists', 'implementing features', 'multi-step work', but missing common variations users might say like 'todo', 'checklist', 'step-by-step', 'project tasks', or 'workflow'. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'implementing features' and 'multi-step work' are fairly generic and could overlap with coding skills, project management skills, or general workflow skills. 'Documentation-first' provides some distinction but the scope remains broad. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong workflow clarity with explicit validation checkpoints and user confirmation gates, which is appropriate for task orchestration. However, it lacks concrete executable examples (TodoWrite API calls, actual file update commands) and includes some redundancy between sections. The documentation-first principle is well-enforced but the skill could be more actionable with specific code snippets.
Suggestions
Add concrete TodoWrite API examples showing actual function calls (e.g., `TodoWrite({action: 'update', id: '1.1', status: 'completed'})`)
Include a specific example of markdown checkbox update code or command rather than just describing the action
Consider extracting the Quality Assurance Checklist to a separate CHECKLIST.md file and referencing it to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., the checklist format repeats concepts already stated in principles). The communication examples add value but could be slightly tighter. | 2 / 3 |
Actionability | Provides clear protocols and communication templates, but lacks executable code examples. The TodoWrite references are abstract without showing actual API calls or concrete implementation patterns. | 2 / 3 |
Workflow Clarity | Excellent sequential workflow with explicit validation checkpoints (documentation review FIRST, user confirmation required, quality assurance checklist). Clear feedback loops for errors and new task discovery with explicit approval gates. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. For a skill of this complexity (~100 lines), the quality assurance checklist and error handling protocols could be referenced separately to keep the main skill leaner. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.