CtrlK
BlogDocsLog inGet started
Tessl Logo

pm-spec-writing

Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A highly actionable, well-sequenced instruction skill with concrete templates, validation checkpoints, and properly signaled one-level references. Its only weakness is length — the inline templates duplicate material also held in the reference files.

Suggestions

Condense the inline Format A/B/C templates to field lists and let references/ hold the full templates, reducing overlap between the body and the reference files.

Trim framing aphorisms (e.g., 'Specs without sequencing become dust on a shelf.') to recover tokens without losing instructional value.

DimensionReasoningScore

Conciseness

The body is free of basic-concept bloat and is well organized, but at ~150 lines it renders three full inline template formats (A/B/C) that overlap with the reference template files, and includes framing aphorisms that could be tightened — matching 'mostly efficient but could be tightened'.

2 / 3

Actionability

Provides concrete, copy-paste-ready templates with exact field structures (TITLE/PROBLEM/USERS/ACCEPTANCE CRITERIA/...), a filled impact-effort grid with examples, and specific priority labels (P0–P3) and output filenames — fully executable guidance.

3 / 3

Workflow Clarity

A clearly sequenced 4-phase framework (Clarify → Scope → Write → Sequence) plus a 7-step workflow with explicit checkpoints ('If any answer is "I don't know," go back to the user', 'Empty sections are flags', 'Define done') and error-recovery loops.

3 / 3

Progressive Disclosure

SKILL.md is an overview that signals three one-level-deep references via markdown links (feature-spec-template.md, dev-brief-template.md, prioritization-frameworks.md), all of which exist on disk; content is appropriately split with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

92%

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, third-person description that explicitly covers what, when, and a rich set of natural trigger phrases. Its only weakness is that several broad triggers overlap with adjacent planning skills.

Suggestions

Qualify or narrow the broader triggers ('prioritize', 'scope this', 'what is the plan for') so they don't fire for roadmap-planning; mirror the body's 'When NOT to use' disambiguation in the description itself.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across work types — 'Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs', 'a feature to spec out, a bug to file, a project to scope' — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what ('Translate ideas ... into specific, actionable dev briefs') and when ('Use this skill whenever the user has an idea they want to build ...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The explicit 'Triggers on I want to add, we should build, can we make, ... PRD, user story, acceptance criteria, scope this, prioritize' gives broad coverage of natural phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Core triggers (PRD, user story, acceptance criteria, dev brief, feature spec) carve a clear spec-writing niche, but broader phrases like 'prioritize', 'scope this', and 'what is the plan for' overlap with roadmap-planning, so conflict risk remains — matching the 'somewhat specific but could overlap' anchor rather than 'unlikely to conflict'.

2 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.