CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-complete-milestone

Archive completed milestone and prepare for next version

Quality

67%

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 ./pi/package-skills/gsd-complete-milestone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured dispatcher skill: a clearly sequenced 0-8 workflow with audit validation, feedback loops, and confirmation gates, plus concrete paths and commands throughout. Its main weaknesses are redundancy (the pre-flight template block, critical_rules, and success criteria repeat process content) and reliance on engine-placeholder file references that cannot be verified from the bundle.

Suggestions

Remove the duplicated Pre-flight Check markdown block in step 0 (or the bullets above it) — one of the two presentations is sufficient and would trim ~15 lines.

Consolidate critical_rules entries that merely restate process steps ("Archive before deleting", "One-line summary") into the steps themselves, keeping critical_rules for genuinely new constraints only.

Add an explicit verification step after archiving (e.g., confirm both milestone archive files exist and are non-empty before deleting .planning/REQUIREMENTS.md) to close the destructive-operation validation gap.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 17-line Pre-flight Check markdown block in step 0 restates the four bullets directly above it, the critical_rules section echoes process steps ("Archive before deleting", "One-line summary"), and success_criteria restate step outcomes. Fits anchor 3 (mostly efficient but could be tightened); not 4 because the duplication is more than minor, and not 2 because there is no conceptual over-explanation of things Claude already knows.

3 / 5

Actionability

Provides concrete executable guidance: exact file paths (`.planning/milestones/v{{version}}-ROADMAP.md`), exact commands (`git tag -a v{{version}} -m "[milestone summary]"`, commit message `chore: archive v{{version}} milestone`), and exact skill invocations (`/skill:gsd-phase --insert <N>`). Anchor 4 (mostly executable with minor gaps); not 5 because the archive-filling and stats-gathering detail is delegated to the external workflow file rather than specified inline.

4 / 5

Workflow Clarity

Clear numbered 0-8 sequence with explicit checkpoints: audit pre-flight with branch handling (gaps → insert closure phases), confirmation gates at steps 1-3, and the archive-before-delete rule guards the destructive REQUIREMENTS.md deletion, so no cap applies. Anchor 4 rather than 5 because there is no verification that archive files were successfully written before deletion proceeds, and no check that the commit/tag succeeded before offering next steps.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep in a dedicated <execution_context> section with an explicit "Load these files NOW" instruction, and the process overview is appropriately split from the detailed workflow. Anchor 4 rather than 5 because the referenced paths are unresolvable engine placeholders with no bundle files present to verify, and the inline process (full step list plus the pre-flight template block) substantially overlaps the external workflow content.

4 / 5

Total

15

/

20

Passed

Description

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

The description is concise and names a clear domain with two high-level actions, but it is uniformly mediocre across dimensions: no trigger guidance, no enumeration of the concrete actions (archiving roadmap/requirements, tagging), and overlap risk with sibling milestone skills. All four dimensions sit at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to complete, close, or ship a milestone/version, or to archive milestone artifacts after all phases are done."

Enumerate the concrete actions so the "what" is comprehensive: "Archive milestone roadmap and requirements to .planning/milestones/, collapse ROADMAP.md to a one-line summary, update PROJECT.md, and git tag the version."

Sharpen distinctiveness by dropping or qualifying "prepare for next version" (which invites confusion with a new-milestone skill) in favor of milestone-completion-specific wording like "archive shipped version artifacts and tag the release."

DimensionReasoningScore

Specificity

Names the domain (milestone/version management) and two actions — "Archive completed milestone" and "prepare for next version" — but neither is detailed; no mention of ROADMAP.md/REQUIREMENTS.md updates or git tagging. Matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because there is no list of several specific actions, and not 2 because it goes beyond bare domain naming.

3 / 5

Completeness

Has a clear "what" ("Archive completed milestone") but the "when" is entirely absent — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Exact match for anchor 3; not 2 because the "what" is clear rather than vague, and not 4 because no "when" information exists even weakly.

3 / 5

Trigger Term Quality

Contains some relevant domain keywords ("milestone", "archive", "version") a GSD user might say, but misses common variations and natural trigger phrases like "finish a milestone" or "ship a version". Fits anchor 3; not 4 since no natural user phrasing is present, and not 2 since the terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The milestone niche is somewhat specific, but "prepare for next version" overlaps with a sibling gsd-new-milestone skill, and with no trigger guidance the description alone cannot disambiguate which skill should fire. Anchor 3 (somewhat specific but could overlap with similar skills); not 4 because the next-version framing creates real overlap risk within the same skill family.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

open-gsd/gsd-core

Path

pi/package-skills/gsd-complete-milestone/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.