CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan-product

Use this skill when the user asks to "plan this product", "define the product", "define product docs", "seed Ubiquitous Language glossary and feature inventory", "define a domain concept", "capture a macro-flow", "plan a feature", "create feature guide", "document a use case", "document the use case", "map actor workflows and alternate flows", "sequence development plan", "dependency-ordered development plan", "order delivery steps", "upgrade planning docs", "migrate model v1 to v2", or run any plan-product workflow. Do NOT use this skill for implementing source code, editing repository files directly, technical slice planning / code review / debugging (route to dev-delivery), repo standards conformance (route to dev-standards), post-implementation learnings (route to dev-learnings), PR/release shipping (route to dev-ship), or plugin/skill authoring (route to plugin-builder).

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/plan-product/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured as a facade skill: a clear triage matrix, explicit invariants, and a closing verification checklist. Its weaknesses are an overloaded path-resolution/telemetry invariant that should be extracted to a reference file, and referenced workflow/src files that are absent from the bundle, leaving the progressive-disclosure chain broken.

Suggestions

Extract the runtime-root 4-step precedence contract and telemetry policy from Invariant 1 into a reference file (e.g. references/path-resolution.md), keeping only the repository-path authority rule inline.

Ensure the referenced `workflows/*.md` runbooks and `src/init/init.mjs`, `src/migration/migrate.mjs`, `src/validation/validate.mjs` actually ship in the skill bundle so the dispatch table's links resolve.

Move the per-segment definitions of the canonical numbering table into a reference document, keeping the ID pattern, canonical name, and path columns inline for quick triage.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts, but Invariant 1 packs path precedence, a 4-step runtime-root resolution contract, and telemetry policy into one ~200-word paragraph, and the numbering table inlines dense segment definitions — material that could be tightened or moved to a reference file. This is 'mostly efficient but could be tightened' rather than clearly verbose.

3 / 5

Actionability

Concrete executable commands are present (`node "${PLUGIN_ROOT}/src/init/init.mjs"`, `src/migration/migrate.mjs`), with exact paths, env-var precedence, and an intent-to-runbook dispatch table. It stops short of 5 because the detailed per-workflow procedures live in external workflow files rather than being demonstrated inline.

4 / 5

Workflow Clarity

Dispatch sequencing is clear (triage matrix, bootstrap-before-interview ordering, explicit stop-and-migrate condition on legacy detection) and a Verification checklist closes every workflow. Not 5 because the per-workflow step sequences and error-recovery feedback loops are delegated to external runbooks not shown in the body.

4 / 5

Progressive Disclosure

References to `workflows/product.md` through `workflows/maintain.md` and `src/*.mjs` are clearly signaled and one level deep, but scoring against the actual bundle (only `assets/` with config.json, schema.json, and templates/ exists), none of the referenced workflow or src files are present — the navigation chain cannot be completed. Structure and signaling are good, but the referenced content is not verifiable in the bundle.

3 / 5

Total

14

/

20

Passed

Description

86%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 with comprehensive, natural trigger phrases and excellent negative-scope routing that minimizes cross-skill conflicts. Its main weakness is that the skill's actual capabilities are only implied through the trigger list rather than explicitly stated.

DimensionReasoningScore

Specificity

The description names many concrete actions ("seed Ubiquitous Language glossary and feature inventory", "map actor workflows and alternate flows", "sequence development plan", "migrate model v1 to v2"), matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because the skill's actual function (a facade/orchestrator over planning workflows) is never stated as a capability — the 'what' surfaces only through trigger verbs.

4 / 5

Completeness

The 'when' is explicit and excellent ("Use this skill when the user asks to..." with concrete trigger phrases, plus explicit "Do NOT use this skill for..." negative routing). It is not a 5 because the 'what' is never directly stated — capabilities are only implied through the enumerated user requests.

4 / 5

Trigger Term Quality

Comprehensive natural trigger phrasing with explicit synonyms: "plan this product", "define the product", "plan a feature", "document a use case"/"document the use case", "sequence development plan"/"dependency-ordered development plan", "order delivery steps", "upgrade planning docs". This matches the anchor for comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The description carves out a clear product-planning niche and explicitly disambiguates against five sibling skills ("route to dev-delivery", "route to dev-standards", "route to dev-learnings", "route to dev-ship", "route to plugin-builder"), giving minimal conflict risk.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 possibly missing (workflows/concept.md, workflows/development-plan.md, workflows/feature.md, workflows/maintain.md, workflows/product.md, +1 more)

Warning

Total

15

/

16

Passed

Repository

NyssaAI/product-planning

Path

skills/plan-product/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.