Spec-driven development loop: RFC → code → drift-checked validation
Turn RFCs and specs into SDD drafts, set up spec-to-implementation drift gates, and run an automated validation loop with codex or claude
- What
- Turn RFCs and specs into SDD drafts, set up spec-to-implementation drift gates, and run an automated validation loop with codex or claude
- Cost
- Free
- Needs
- the indexion CLI installed (verify with indexion --version); a spec-driven workflow tool such as cc-sdd (installable via npx, e.g. npx cc-sdd@latest --codex-skills --lang en --yes) or an agent with a codex/claude runtime; a specification document (RFC, ISO, markdown) to implement
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @trkbt10's bridge between indexion's quantitative spec-alignment tools and SDD agent workflows: draft SDD requirements from RFCs, specs or ISO documents (`indexion spec draft`, with supported formats — RFC plaintext, technical documents, markdown — and an ISO PDF text-extraction script), run a specification fidelity check so the draft covers the source without inverting its intent, then trace the full chain spec↔requirements↔design↔implementation with `indexion spec align diff` at each abstraction hop (never spec-vs-code directly — vocabulary spaces differ too much), and run an automated validation loop where indexion's quantitative drift results feed agent-driven qualitative review. Honest caveats: indexion must be installed first (verify with `indexion --version`); set the spec tooling language to the IMPLEMENTATION language, not the spec language (mismatched languages break vocabulary matching); drift gates run as CI checks; ISO spec extraction needs a page range. By @trkbt10, listed here with credit to its creator. Apache-2.0 licensed (declared in the source repo). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the indexion CLI installed (verify with indexion --version); a spec-driven workflow tool such as cc-sdd (installable via npx, e.g. npx cc-sdd@latest --codex-skills --lang en --yes) or an agent with a codex/claude runtime; a specification document (RFC, ISO, markdown) to implement Install "Spec-driven development loop: RFC → code → drift-checked validation" for me. It teaches an agent @trkbt10's indexion-SDD loop: verify indexion is available, scaffold the SDD project (cc-sdd install, project init, git), draft SDD requirements from the spec with indexion spec draft (set the tooling language to the implementation language), run the spec fidelity check, then implement and trace spec↔requirements↔design↔implementation with indexion spec align diff at each abstraction hop, and operate the drift gates as CI checks with an automated validation loop. Apache-2.0 licensed (declared in the source repo). Repository: https://github.com/trkbt10/indexion-skills/blob/main/skills/indexion-sdd/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "indexion-sdd". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the indexion CLI and cc-sdd, prepare the spec document, confirm the implementation language). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.