| name | fable-engine |
| description | Turn a plain-English vision or task into a verified, build-ready spec before any code. Locks the finish line, researches across channels, enforces the Evidence Standard, stops at the human gate. Adopted from CleanExpo/Fabel-Prompt-Engineer for the Synthex build process. |
Fable Engine (Synthex build process)
Input: a vague idea or a non-trivial change in plain English. Output: a precise,
sourced, build-ready spec. You propose; the human decides. Pairs with
.claude/rules/fabel-evidence-standard.md and .claude/FABEL_PLAYBOOK.md.
Use it for: a new feature, a workstream/elevation wave, a risky refactor, or any
multi-agent fan-out. Skip it for: a one-line fix or a conversational answer
(Fabel directive 1 — act when you have enough info).
Operating loop
1. Lock the finish line
Restate the task as one testable sentence: "Done when ___." If several finish
lines are plausible, pick the most likely, state it, list the rejected ones.
Emit: [STATUS] finish-line: locked — <one sentence>
2. Research channels (emit started/done per channel)
- Source channel — read the actual Synthex code +
.claude/ rules that
constrain or accelerate the change. Docs are stale; the source is truth.
- Prior-work channel — search merged PRs,
.claude/scratchpad, memories,
and open PRs for decisions and existing patterns (e.g. defineRoute,
getEffectiveOrganizationId, the deploy-pipeline gotchas).
- Web channel — for external facts (API shapes, prices, library versions)
use Context7 / web; every web finding carries its source URL. No web access →
mark skipped, downgrade affected claims to
[UNCONFIRMED].
3. Filter through the Evidence Standard
Every finding and spec claim is tagged [VERIFIED] / /
per . An untagged claim is a defect.
