Name: full-sdc
Rating: 68 (1 reviews)
Author: SynkraAI

full-sdc

EXECUTE lean Full Story Development Cycle for one story: plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/. Use when: full-sdc, full cycle, SDC, run story end-to-end.

Quality

82%

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

The canonical home for this skill is full-sdc in SynkraAI/aiox-core

Quality

Content

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

A well-structured orchestrator skill with concrete CLI commands, an explicitly sequenced EXECUTE loop, and strong validation/feedback checkpoints. The main gaps are abstract 'materialize the payload' guidance and reliance on non-bundled external SOT references.

Suggestions

Add a concrete one-line example of how to materialize the child prompt/context files (e.g., a heredoc or write command) so the preflight step is fully executable.

Demystify the dense jargon (SOT, QG, ACK, GC, LOC) with a short glossary or inline expansion on first use.

Consolidate the duplicated preflight guidance into one section and cross-reference it to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean with tables and terse bullets, assuming Claude's domain knowledge and avoiding concept explanation; minor jargon density (SOT, QG, ACK, GC) and light redundancy of the preflight command keep it just below the leanest 5 anchor.	4 / 5
Actionability	Concrete, copy-paste-ready CLI commands (plan/next/verify/preflight/status) with arguments are provided throughout, but the 'materialize the exact payload/context in isolated files' step is described abstractly without a concrete file-creation example.	4 / 5
Workflow Clarity	The EXECUTE loop is explicitly sequenced with validation checkpoints (preflight HALT on non-zero, verify --mark after each phase), feedback loops (QG loop: review → apply_qa_fixes → re-review, max 3), and checklists (Sequence Lock, Strip checklist), matching the top anchor.	5 / 5
Progressive Disclosure	A lean orchestrator overview that points one level deep to phase skills and task SOTs via the Phase map table, with clear section structure; scored 4 rather than 5 because the referenced SOT files are not bundled/verifiable and the skill-SOT path is mentioned only once.	4 / 5
	Total	17 / 20 Passed

Description

83%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, concise description that explicitly states both what the skill does and when to use it, with concrete trigger phrases. Slight jargon density and a couple of generic trigger terms keep it just below maximum on specificity, trigger quality, and distinctiveness.

Suggestions

Soften internal jargon like 'EXECUTE lean' and 'Sequence Lock' in the description or pair them with a plain-language gloss so the capability reads concretely.

Add one or two more natural trigger variations (e.g., 'develop a story', 'story development cycle') to broaden trigger-term coverage.

Tighten the generic triggers ('full cycle', 'run story end-to-end') with a domain qualifier to reduce overlap with adjacent lifecycle skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('plan via CLI', 'validate → develop → review (QG loop) → close with Sequence Lock', 'durable progress under .aiox/sdc/') covering the full cycle, matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive 5 due to jargon like 'EXECUTE lean'.	4 / 5
Completeness	Clearly answers both 'what' (EXECUTE the Full Story Development Cycle: plan, validate, develop, review, close) and 'when' (explicit 'Use when:' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The explicit 'Use when: full-sdc, full cycle, SDC, run story end-to-end' provides good keyword coverage with synonyms a user would naturally say, falling just short of comprehensive (missing variations like 'develop a story').	4 / 5
Distinctiveness Conflict Risk	Niche triggers like 'full-sdc' and 'SDC' are highly distinct, but the more generic 'full cycle' and 'run story end-to-end' carry minor overlap risk with adjacent story-lifecycle skills.	4 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .claude/skills/full-sdc/SKILL.md
Commit: 4ef6530

Reviewed: 2 days 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.