get-fablelisted

Route and orchestrate the canonical get-fable coding lifecycle — discover, research, plan, build, verify, review, secure, release, recover — from durable .fable state and incoming intent. Use when starting any substantial engineering task, resuming from a handoff, navigating lifecycle phase transitions, or determining the next load-bearing specialist when the current path is ambiguous. Do NOT use when a specific fable-* specialist already has clear, still-valid ownership of an in-progress bounded task.
imMamdouhaboammar/get-fable · ★ 6 · AI & Automation · score 71

Install: claude install-skill imMamdouhaboammar/get-fable

# get-fable — Repository-Local Lifecycle Adapter This is the host-installed adapter. The **canonical semantic source** lives in: - `skills/get-fable/SKILL.md` — full orchestration protocol - `skills/get-fable/registry.json` — all 25 skill nodes, routing graph, precedence gates - Root `skills/fable-*/SKILL.md` — specialist skill instructions - Root `AGENTS.md` — working contract, invariants, verification commands --- ## What get-fable does `get-fable` is a lifecycle harness, not a prompt pack. It surrounds any coding agent with: ``` DISCOVER → RESEARCH → PLAN → TDD → DELEGATE → EXECUTE ↓ VERIFY → REVIEW → SECURITY ↓ RELEASE or RECOVER → HANDOFF ``` Every transition is **evidence-gated**. Completion cannot be claimed unless fresh, mutation-current evidence passes. Research receipts and execution logs do not substitute for behavior verification. --- ## Routing Decision Table | Situation | Specialist to activate | |---|---| | Repository/runtime facts unknown | `fable-discover` | | External API / current version uncertain | `fable-research` | | Architecture or contract decision needed | `fable-plan` | | Testable behavior change or bug fix | `fable-tdd` | | Genuinely independent, disjoint bounded cards | `fable-delegate` | | Single accepted bounded implementation card | `fable-execute` | | Fresh falsification evidence required | `fable-