Skip to content

Add spec-driven-slicing skill#1450

Open
uesugitorachiyo wants to merge 1 commit into
obra:mainfrom
uesugitorachiyo:spec-driven-slicing-skill
Open

Add spec-driven-slicing skill#1450
uesugitorachiyo wants to merge 1 commit into
obra:mainfrom
uesugitorachiyo:spec-driven-slicing-skill

Conversation

@uesugitorachiyo
Copy link
Copy Markdown

Summary

Adds the spec-driven-slicing skill, which guides Claude through prompt-pack-style spec-driven builds — one slice at a time, with TDD discipline, gated red-test verification, and per-slice implementation reports.

What it does

When a project ships as a numbered prompt pack (e.g. S00 → S21), the skill walks Claude through each slice deterministically:

  1. Read the slice spec.
  2. Write the failing test(s) first — verify red.
  3. Implement until green.
  4. Emit a 6-section Slice Implementation Report.
  5. Stage + commit.
  6. Move to the next slice.

This is the discipline that drove the AO Runtime build to feature-completion (187 Rust tests + 4 eval scenarios green, all 22 slices shipped, cargo fmt --check and cargo clippy --all-targets -D warnings clean).

Files

  • skills/spec-driven-slicing/SKILL.md — the skill itself
  • skills/spec-driven-slicing/README.md — operator-facing docs

Test plan

  • Authored against the AO Runtime prompt pack format
  • Smoke-tested in /tmp/sds-smoke against a synthetic 3-slice pack
  • Used to drive AO Runtime S00 → S21 + 5 post-pack follow-ups end-to-end

🤖 Generated with Claude Code

Rigid process skill that executes one slice from a prompt-pack-style
spec-driven build. Hard gates against scope creep and skipped tests;
deterministic 3-rule slice picker; mandatory Slice Implementation
Report. Composes with test-driven-development for the test-first phase.

Variant B delivery: skill ships without bundled examples/. The AO
Runtime prompt pack is referenced externally in the "Worked example"
section; users obtain or write their own pack and point the skill at it
via the pack-shape contract.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant