continue-spec

Continue a multi-phase engineering spec from its progress table. Use when the user says /continue-spec, "continue the spec", "continue the operations feature", or asks what the next phase is. Runs the next step (plan, implement, review) in this session on the model the spec names, stopping at the spec's gates. Never uses subagents.

Quality

93%

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

92%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 tight, well-structured workflow with explicit gates and validation checkpoints that assume Claude's competence. It is appropriately scoped with no padding and clear navigation.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; every line directs action or states a rule.	5 / 5
Actionability	Provides concrete, executable guidance — specific slash commands ('/code-review high'), named skills ('superpowers:writing-plans'), and a default spec path — though some execution detail is deferred to the external spec.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow with explicit validation checkpoints (gates G0–G3), a 'wait for the answer' feedback loop, and an escalation path (G5) for blocked decisions.	5 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no nested references; the only referenced path is the working spec artifact, appropriate for this simple, single-purpose skill.	5 / 5
	Total	19 / 20 Passed

Description

95%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 precise, trigger-rich, and clearly distinguishes the skill from others via a specific slash command and explicit scope boundaries. It fully answers both what and when with concrete phrasing.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'Runs the next step (plan, implement, review)', 'stopping at the spec's gates', 'Never uses subagents' — with minor gaps in coverage of the underlying mechanics.	4 / 5
Completeness	Explicitly answers both what ('Continue a multi-phase engineering spec... Runs the next step') and when ('Use when the user says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural triggers including the exact slash command '/continue-spec' and multiple paraphrases ('continue the spec', 'continue the operations feature', 'asks what the next phase is') a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	A narrow niche (spec continuation from a progress table) with a distinct slash-command trigger and explicit 'never uses subagents' boundary, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: karanhudia/borg-ui
Path: .claude/skills/continue-spec/SKILL.md
Commit: c7f32d1

Reviewed: 1 day 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.