From fable-discipline
Use when planning, building, or reviewing a software milestone/release/version — any task framed as "ship vX", "build the next milestone", "plan and execute a feature set", "do a research + build pass", or "review what we shipped". Establishes a three-phase discipline (research & design → build from the design → adversarial review) with verify-after-each-step and honest-classification rigor. Reads the repo's own CLAUDE.md for project-specific commands and conventions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fable-discipline:milestone-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A disciplined way to take a milestone from idea to shipped, distilled from real
A disciplined way to take a milestone from idea to shipped, distilled from real high-quality milestone cycles. Three phases, each with a dedicated command:
/milestone-research) — figure out what's worth
building before writing code; produce an approved design doc./milestone-build) — execute the design in atomic, verified steps./milestone-review) — a cross-perspective pass that
catches what self-review can't, before declaring done.Run them in order across a milestone. You don't have to use the commands — when you recognize a phase, apply its discipline directly.
This workflow is generic. Before acting, read the repo's CLAUDE.md (and
.planning/STATE.md / ROADMAP.md if present) to learn the project-specific:
Never hardcode another project's commands. If CLAUDE.md doesn't state a verify
command, ask or infer from package.json scripts — don't guess silently.
These are the through-lines that made the reference cycles work:
The full, paste-ready instructions for each phase live in references/:
references/phase-research.mdreferences/phase-build.mdreferences/phase-review.mdThe /milestone-* commands are thin entry points to these same files, so the
skill and commands never duplicate the prompt text.
This skill is the generalized form of the patterns observed across real milestone cycles (research-rounds + cross-AI consult → P0 design → phased build with verify-after-each-wave → numbered adversarial-fix batches). It is the HOW; each repo's CLAUDE.md + design doc is the WHAT.
npx claudepluginhub petrkindlmann/fable-discipline --plugin fable-disciplineGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.