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

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and a rigorously sequenced workflow including validation gates and feedback loops. The only weakness is minor redundancy in restating the preflight and verify steps across multiple sections.

Suggestions

Consolidate the 'aiox sdc preflight' and 'verify … --mark' instructions into one canonical block and reference it from the Invocation, EXECUTE loop, and Grok sections to remove repetition.

Consider moving the long pseudocode EXECUTE loop into a referenced file (e.g. EXECUTE-loop.md) and keeping only a compact decision summary inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-oriented, but preflight and 'verify --mark' instructions are restated across the Invocation, CLI, EXECUTE loop, and Grok sections; tightening the repetition would approach a 3.	2 / 3
Actionability	Provides copy-paste-ready CLI commands with exact flags, exit codes (0/5), state-file paths, and a phase map — fully executable guidance.	3 / 3
Workflow Clarity	The EXECUTE loop is explicitly sequenced with a preflight gate, HALT conditions, and a review→apply_qa_fixes feedback loop capped at 3 iterations with escalation.	3 / 3
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled external task SOT references (e.g. .aiox-core/development/skills/<name>/SKILL.md); no deep nesting and no bundle files present to mis-organize.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 third-person, dense with concrete actions, and supplies an explicit 'Use when' trigger list — strong across all dimensions. It avoids fluff and over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/' — far beyond a single named action.	3 / 3
Completeness	Explicitly states both what (EXECUTE the SDC: plan, run phases, close) and when ('Use when: full-sdc, full cycle, SDC, run story end-to-end').	3 / 3
Trigger Term Quality	'Use when: full-sdc, full cycle, SDC, run story end-to-end' gives natural terms a user would actually say rather than only jargon.	3 / 3
Distinctiveness Conflict Risk	Niche is narrow (one-story SDC orchestrator) with distinct triggers ('full-sdc', 'full cycle', 'SDC') unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: .aiox-core/development/skills/full-sdc/SKILL.md
Commit: 0b32b68

Reviewed: about 14 hours 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.