feature-planning-artifacts

Use when creating or iterating staged planning artifacts for a complex feature: design discussion, structure outline, final executor plan, or supporting research/research questions. Also use when designing before coding, breaking work into vertical slices, or deepening a high-value roadmap item, NNN improve plan, architecture candidate, or HumanLayer-style task.

Quality

82%

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

Quality

Content

81%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 detailed, well-structured instruction skill with explicit staged workflows, validation checkpoints, and a single well-signaled reference file. Its main weakness is mild redundancy between the Stage Contract table and the Workflow section.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and assumes Claude's competence without explaining basic concepts, but the Stage Contract table and the Workflow section restate the same stages, introducing some redundancy that could be trimmed.	4 / 5
Actionability	Concrete, specific guidance throughout — file paths (`.agents/plans/features/<feature-slug>/`), status markers (`status: in-review`), numbered stages, and exact review-gate phrases; minor gaps keep it just below fully copy-paste-ready 5.	4 / 5
Workflow Clarity	A clearly sequenced multi-stage workflow with explicit stop gates, review gates, status transitions, and validation checkpoints ('Verify load-bearing claims before they enter the design discussion', 'Verify factual corrections', drift checks), matching the 5 anchor.	5 / 5
Progressive Disclosure	Good structure with a single clearly-signaled, one-level-deep reference to [references/artifact-templates.md](references/artifact-templates.md) (a real file); the body is somewhat long, which is appropriate for the content but keeps it just below the lean 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

83%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 that clearly states both capability and trigger conditions with concrete, natural language. It is dense with artifact names and would benefit only from minor tightening and a few extra synonyms.

Dimension	Reasoning	Score
Specificity	Names a long list of concrete artifact types ('design discussion, structure outline, final executor plan, or supporting research/research questions', 'vertical slices', 'NNN improve plan', 'architecture candidate'), giving several specific outputs; slightly dense rather than cleanly comprehensive, so below 5.	4 / 5
Completeness	Explicitly answers both what ('creating or iterating staged planning artifacts') and when (two clear 'Use when' / 'Also use when' clauses with concrete trigger phrases), matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('designing before coding', 'breaking work into vertical slices', 'deepening a high-value roadmap item'); good coverage but a few common phrasings/synonyms are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The 'HumanLayer-style', 'vertical slices', and 'executor plan' framing carves a distinct niche with minimal conflict; 'designing before coding' is somewhat broad, leaving minor overlap risk with general design skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: joshuadavidthomas/agent-skills
Path: feature-planning-artifacts/SKILL.md
Commit: 516dee7

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