aiox-full-sdc

Orchestrates the full story development cycle through validate, develop, review, and close phases.

3.1k|952|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/SynkraAI/aios-core --skill aiox-full-sdc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-full-sdc
Source: https://github.com/SynkraAI/aios-core/tree/main/.grok/skills/aiox-full-sdc
Command: npx skills add https://github.com/SynkraAI/aios-core --skill aiox-full-sdc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running a user story end-to-end through validation, development, QA review, and closure requires coordinating multiple agents and phases manually, which is error-prone and hard to track. This Skill orchestrates the entire Story Development Cycle (SDC) for one story with durable state, CLI-enforced sequencing, and a quality-gate loop.

Core Features & Use Cases

  • Phase Orchestration: Runs validate → develop → review → apply_qa_fixes (loop) → close, dispatching each phase to the matching agent persona (@po, @dev, @qa) or running inline.
  • CLI-Driven State Management: Uses aiox sdc plan/next/verify/status commands with durable progress persisted under .aiox/sdc/ so cycles can be resumed.
  • Quality Gate Loop: Enforces a review loop with a maximum of 3 iterations, anti-self-validation (executor ≠ quality_gate), and preflight budget/intent gating before any model or subagent call.
  • Use Case: A developer has a drafted story file and wants it validated, implemented, QA-reviewed, and closed autonomously in yolo mode, with the CLI halting and escalating on any failed verification.

Quick Start

Run the full story development cycle on your story file by invoking /full-sdc with the story path, optionally adding yolo for autonomous mode or interactive for step-by-step pauses.

Frequently Asked Questions about aiox-full-sdc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a story end-to-end with the full SDC workflow?

Invoke /full-sdc with the story path, or run aiox sdc plan {story-path} --mode yolo for autonomous execution. The orchestrator then loops through validate, develop, review, and close phases, verifying each with aiox sdc verify before advancing.

What is the difference between yolo and interactive mode in the SDC cycle?

Interactive mode reports between phases and pauses on decisions or failed reviews without explicit fix approval. Yolo mode runs autonomously between phases, automatically triggering apply-qa-fixes on review failure, and stops only on absolute blockers or circuit breakers.

How does the QA review loop work in the story development cycle?

After develop, the review phase runs a QA gate. On FAIL, apply-qa-fixes runs and the cycle returns to review, up to a maximum of 3 iterations tracked as qgIterations. A third failed re-review halts the cycle and escalates to a human.

Why does the SDC preflight command block a phase from running?

The aiox sdc preflight gate validates the exact child prompt, context files, story path, and budget ceiling before any model or subagent call. Exit code 5 is a governance rejection, meaning the model must not be invoked with that payload.

Can the full SDC skill push code or create pull requests?

No. Push and PR creation are explicitly handed off to the @devops agent and are never performed by this skill. The deploy phase is also skipped when no deploy configuration exists.

Where is SDC progress state stored and can a cycle be resumed?

State is persisted in .aiox/sdc/{story-id}/state.json, which is gitignored runtime data. Running aiox sdc plan again initializes or resumes the durable state, and aiox sdc status inspects progress at any time.