CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-execute-phase

SDD phase execution — execute all plans in a phase with dependency-aware wave parallelization

Quality

68%

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-execute-phase/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 disciplined, fail-closed orchestration shim: it delegates the heavy workflow to explicitly-loaded external files and gives concrete dispatch and error-handling rules. Its main weakness is redundancy — the flag-activation logic and --wave documentation appear twice — and the absence of a literal gsd_dispatch example.

Suggestions

Deduplicate the flag rules: state the literal-token activation rule once (in <context>) and remove the 'Flag handling rule' bullets from <objective>, keeping only the one-line --wave mention.

Add a short concrete example of the dispatch contract, e.g. 'gsd_dispatch(role: implementer, task: <step prompt>)', and of the --wave flag syntax ('--wave 2').

Clarify what 'Preserve all workflow gates' concretely requires (checkpoint handling, verification, state updates are listed but not what each gate demands), or trust the referenced workflow file explicitly and drop the enumeration.

DimensionReasoningScore

Conciseness

The body is mostly lean and operational ('Orchestrator stays lean', 'Context budget: ~15% orchestrator, 100% fresh per subagent'), but the flag-activation rule is stated twice in near-verbatim form — the 'Flag handling rule' bullets in <objective> and the 'Active flags must be derived' bullets in <context>, with --wave documented in both sections. That duplication goes beyond the 'minor instances of over-explanation' of score 4, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact tool contract ('call gsd_dispatch with role ... and task ...'), fail-closed error handling ('STOP that step and surface the error', offer to skip if optional), and a concrete query ('gsd-tools query init.execute-phase'). It falls short of 5 because no literal invocation example of gsd_dispatch or the wave-filter syntax is shown, leaving minor gaps.

4 / 5

Workflow Clarity

The sequence is coherent — read execution_context files first ('Before doing anything else, read every file listed'), then execute the loaded workflow end-to-end — with explicit validation checkpoints for a batch operation: fail-closed dispatch handling and 'phase verification/completion still only happens when no incomplete plans remain'. Not score 5 because the actual step-by-step wave workflow is delegated to the external workflow file, so checkpoints like verification routing are named ('Preserve all workflow gates') rather than spelled out.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (<objective>, <execution_context>, <context>, <process>) with clearly signaled one-level-deep references to the workflow and brand files, and no bundle files exist to nest. It misses 5 because flag documentation is inlined and duplicated across two sections rather than living once in the appropriate place, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

53%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 specific, distinctive capability, but it reads as a title-plus-mechanics summary rather than a discovery description. It lacks any 'when to use' trigger guidance and natural trigger phrasing, which caps completeness and trigger-term quality at the midpoint.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to run or execute a phase of plans, parallelize plan execution, or run only Wave N of a phase.'

Expand the action list slightly for fuller coverage: e.g. mention analyzing plan dependencies, grouping plans into waves, and collecting subagent results.

Include natural synonyms users would actually type ('run the phase', 'execute plans', 'spec-driven development') alongside the SDD jargon.

DimensionReasoningScore

Specificity

The description names its domain ('SDD phase execution') and two concrete actions — 'execute all plans in a phase' and 'dependency-aware wave parallelization' — matching the anchor for naming domain plus 1-2 concrete actions. It is not the level-4 anchor because it stops at two actions rather than listing several with only minor coverage gaps.

3 / 5

Completeness

The 'what' is clear (execute all plans in a phase with wave parallelization), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above score 2 because the 'what' is concrete rather than vague, and below 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Phrases like 'phase', 'plans', and 'execute' are relevant keywords a user in an SDD workflow might say, but the description offers no synonyms or natural variations (e.g. 'run the phase', 'spec-driven development'), fitting the 'some relevant keywords but missing common variations' anchor. Not score 4 because keyword coverage is thin, not just missing a few terms.

3 / 5

Distinctiveness Conflict Risk

'SDD phase execution' carves out a clear niche with domain-specific vocabulary unlikely to trigger generic skills, fitting 'mostly distinct; minor overlap risk'. Not score 5 because within the same GSD/SDD toolchain it plausibly overlaps with sibling skills (e.g. execute-plan, verify-phase) and no distinct trigger phrases are given to disambiguate.

4 / 5

Total

13

/

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-execute-phase/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.