parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.
82
78%
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/agent-teams/skills/parallel-feature-development/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific niche (multi-agent parallel development coordination), lists concrete actions and strategies, and provides comprehensive trigger guidance with five distinct 'when' scenarios. The description uses proper third-person voice and includes natural keywords that users would employ when needing this capability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: coordinate parallel feature development, file ownership strategies, conflict avoidance rules, integration patterns, decomposing features into work streams, establishing file ownership, designing interface contracts, and deciding between vertical slices vs horizontal layers. | 3 / 3 |
Completeness | Clearly answers both 'what' (coordinate parallel feature development with file ownership, conflict avoidance, integration patterns) and 'when' with an explicit 'Use this skill when...' clause listing five specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'parallel feature development', 'file ownership', 'merge conflicts', 'multi-agent', 'interface contracts', 'vertical slices', 'horizontal layers', 'full-stack feature', 'shared codebase', 'work streams'. These cover a good range of natural language a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche around multi-agent parallel development coordination, file ownership, and merge conflict prevention. The specificity of terms like 'multi-agent implementation', 'file ownership strategies', and 'interface contracts' make it highly unlikely to conflict with general coding or project management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized reference document for parallel development coordination with good structure and clear categorization of strategies. However, it reads more like a knowledge base article than an actionable skill — it lacks concrete sequenced workflows with validation checkpoints, and much of the guidance is strategic rather than executable. The troubleshooting section is a strength, providing specific problem-solution pairs.
Suggestions
Add a concrete step-by-step workflow at the top (e.g., '1. Identify shared files → 2. Assign ownership → 3. Validate no overlaps → 4. Define interface contracts → 5. Create branches → 6. Begin implementation') with explicit validation checkpoints between steps.
Include executable commands for key operations like branch creation, checking for file ownership conflicts (e.g., a script or grep command to verify no file appears in multiple ownership lists), and merge procedures.
Trim explanatory text that Claude already knows (e.g., what MVC is, what merge conflicts are, pros/cons of basic branching strategies) to focus on the novel coordination rules and patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-organized but includes some unnecessary elaboration. Phrases like 'Best for' annotations and the pros/cons lists add moderate value but could be tightened. Some sections (e.g., Branch Management) explain concepts Claude would already understand well. | 2 / 3 |
Actionability | The skill provides concrete examples of file ownership assignments, interface contracts (with executable TypeScript), and branch structures. However, much of the content is strategic guidance rather than executable commands or copy-paste-ready workflows. There are no actual commands for branch creation, merging, or validation steps. | 2 / 3 |
Workflow Clarity | The skill describes strategies and patterns but lacks a clear sequenced workflow for actually performing parallel feature decomposition. There are no explicit validation checkpoints or feedback loops — for instance, no step to verify file ownership assignments don't overlap, or to validate that interface contracts are consistent before implementation begins. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, appropriate use of subsections, and links to related skills at the end. The content stays at an overview/guidance level without becoming monolithic, and references to related skills are one level deep and clearly signaled. | 3 / 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
- wshobson/agents
- Commit
91fe43e
- 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.