sprint-workflow

Execute this skill should be used when the user asks about "how sprints work", "sprint phases", "iteration workflow", "convergent development", "sprint lifecycle", "when to use sprints", or wants to understand the sprint execution model and its convergent diffusion approach. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is a lean, actionable, well-sequenced workflow with explicit validation and feedback loops. Its main weakness is progressive disclosure: inline Error Handling and Examples sections duplicate the unreferenced errors.md and examples.md files instead of pointing to them.

Suggestions

Replace the inline "## Error Handling" table with a pointer to references/errors.md (or vice-versa) so the detail lives in one place and the bundle file is actually navigable.

Replace the inline "## Examples" section with a link to references/examples.md, keeping only a single brief example in SKILL.md and delegating the full worked examples to the reference file.

Add the missing reference links to the "## Resources" section so all three bundle files (sprint-phases.md, errors.md, examples.md) are clearly signaled one level deep.

Dimension	Reasoning	Score
Conciseness	The body is lean and concrete with no concept-padding: each phase is one sentence with specific file paths and agent names, and it avoids explaining what a sprint or a library is.	3 / 3
Actionability	It gives concrete commands ("/sprint:new", "/sprint"), specific file paths (".claude/sprint/[N]/specs.md", "api-contract.md"), named agents, and a diagnostic error table, providing actionable rather than vague guidance.	3 / 3
Workflow Clarity	The six phases are clearly numbered and sequenced with explicit validation (Phase 3 testing, Phase 4 conformity review), a feedback loop (re-address only failures), and an explicit 5-iteration safety checkpoint.	3 / 3
Progressive Disclosure	Only sprint-phases.md is referenced from the body, while errors.md and examples.md exist as bundle files but are not linked; instead their content is duplicated inline in the Error Handling and Examples sections, so content that should be separate is inline and two references are orphaned.	2 / 3
	Total	11 / 12 Passed

Description

72%

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 strong, specific trigger terms and a clear niche, but it frames the skill's purpose through the user's intent rather than concrete skill actions, leaving the "what does this do" only implicit. Tightening the opening into a third-person capability statement would lift completeness and specificity.

Suggestions

Lead with a concrete third-person action statement of what the skill does (e.g., "Explains the Sprint plugin's convergent diffusion execution model and its six phases") before the trigger clauses, so the "what" is explicit.

Replace the generic filler "Use when appropriate context detected. Trigger with relevant phrases based on skill purpose." with the specific trigger phrases already listed, removing vague padding.

Drop the awkward leading words "Execute this skill should be used" in favor of a direct capability verb to improve both specificity and voice clarity.

Dimension	Reasoning	Score
Specificity	It names a clear domain ("sprint execution model", "convergent diffusion approach") but states the user's intent rather than listing concrete skill actions, so it names the domain without being comprehensive on capabilities.	2 / 3
Completeness	The "when" is explicit ("should be used when the user asks about...", "Use when appropriate context detected"), but the "what" is only implied through the user's desire to understand the model rather than a clear statement of the skill's own actions.	2 / 3
Trigger Term Quality	It lists several natural phrases a user would say ("how sprints work", "sprint phases", "iteration workflow", "when to use sprints") giving good coverage, despite some jargon like "convergent diffusion".	3 / 3
Distinctiveness Conflict Risk	Triggers are tightly scoped to the Sprint plugin niche ("sprint lifecycle", "sprint phases", "convergent diffusion"), making it clearly distinguishable and unlikely to fire for unrelated skills.	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: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: 2 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.