CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured instructional skill with concrete examples, a numbered procedure for the trickiest case (shared files), and a strong troubleshooting section covering failure modes and recovery. The main gaps are missing explicit validation checkpoints in the workflow, and a progressive-disclosure failure: the two bundled reference files are orphaned — never referenced from SKILL.md — while overlapping content is inlined instead of delegated.

Suggestions

Link the existing bundle files from the relevant sections (e.g., 'For a step-by-step ownership assignment process, see [file-ownership.md](references/file-ownership.md)' under File Ownership Strategies, and 'For merge ordering and integration patterns, see [merge-strategies.md](references/merge-strategies.md)' under Branch Management), and trim the duplicated inline content to keep SKILL.md an overview.

Add an explicit validation checkpoint to the main workflow, e.g., before implementation starts: 'Verify the assignment is complete: every file in the change set maps to exactly one owner, and every cross-boundary dependency has a contract file.'

Remove or shrink the 'When to Use This Skill' section, which restates the frontmatter description and adds no new information to the body.

DimensionReasoningScore

Conciseness

The body is efficient: terse sections, illustrative ownership/branch examples, and a complete TypeScript contract, with no padding explaining concepts Claude already knows (it never explains what a merge conflict is). Falls short of level 5 because the 'When to Use This Skill' section restates the frontmatter description and the Single/Multi-Branch bullets partly restate the Integration Patterns section. Clearly above level 3, which expects noticeably unnecessary explanation.

4 / 5

Actionability

Mostly executable guidance: concrete ownership assignment blocks, a numbered four-step procedure for shared files, a copy-paste-ready TypeScript interface contract, and per-symptom troubleshooting fixes. Falls short of level 5 because some guidance stays high-level (e.g., 'Message the owner with specific change requests' gives no message format or protocol, and 'have the lead merge them at the end' gives no merge order). Well above level 3, which expects pseudocode or missing key details.

4 / 5

Workflow Clarity

Sequences are clear where given (the shared-file procedure, the hybrid decomposition examples) and the Troubleshooting section provides explicit error-recovery loops ('merge conflicts appear even with clear ownership rules' → diagnose the double-assigned barrel file → 'designate one owner... or have the lead merge'). Falls short of level 5 because there is no end-to-end workflow with explicit validation checkpoints (e.g., a 'verify every file has exactly one owner before starting' gate) and the overall decompose → assign → implement → integrate sequence is implicit across sections. Above level 3, which expects missing/implicit checkpoints with no recovery guidance.

4 / 5

Progressive Disclosure

The body itself is well organized with clear section headers and a 'Related Skills' section, but the bundle's two reference files (references/file-ownership.md and references/merge-strategies.md) are never linked or signaled from SKILL.md, and their subject matter (file ownership decision process, integration/merge strategies) partially duplicates the inlined File Ownership Strategies and Branch Management sections. This matches level 3 ('references present but not clearly signaled; content that should be separate is inline') rather than level 4, which requires references to be mostly clearly signaled.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description: concrete, third-person capability statement paired with an explicit multi-condition 'Use when' trigger clause. It clearly communicates both what the skill does and when to reach for it. The only weaknesses are a handful of missing natural synonyms and slight breadth in the opening clause that could overlap with general orchestration skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with comprehensive coverage: 'Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns', plus 'decomposing a large feature into independent work streams', 'establishing file ownership to prevent merge conflicts', 'designing interface contracts', and 'vertical slices versus horizontal layers'. No vague filler; every clause names a concrete capability, matching the level-5 anchor rather than level 4 (which expects minor coverage gaps).

5 / 5

Completeness

Both questions are explicitly answered: the 'what' is 'Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation', and the 'when' is an explicit 'Use this skill when...' clause with five concrete trigger conditions. This matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say: 'parallel feature development', 'file ownership', 'merge conflicts', 'interface contracts', 'work streams', 'vertical slices', 'horizontal layers'. Falls short of level 5 because a few natural synonyms and phrasings are missing (e.g., 'parallelize work', 'split a feature across agents', 'assign files to agents'), while clearly exceeding level 3 (which expects missing common variations).

4 / 5

Distinctiveness Conflict Risk

Distinctive triggers like 'establishing file ownership to prevent merge conflicts', 'designing interface contracts', and 'deciding whether to use vertical slices versus horizontal layers' carve out a clear niche, but the broad opening clause 'Coordinate parallel feature development... for multi-agent implementation' has minor overlap risk with general multi-agent orchestration/team-formation skills. Fits level 4 (mostly distinct, minor overlap with closely related skills) better than level 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

wshobson/agents

Path

plugins/agent-teams/skills/parallel-feature-development/SKILL.md

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.