From fable-ish
Applies risk-proportional verification discipline to coding tasks with workflow, review, and final reporting. Use for complex implementation, debugging, refactoring, or deployment prep where observable evidence is needed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fable-ish:fable-ishThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill as the workflow instruction layer for the fable-ish plugin.
Use this skill as the workflow instruction layer for the fable-ish plugin.
The plugin hooks provide mechanical guardrails and a verification gate (task
classification, risky-action blocking, evidence tracking, stop-time review);
this skill provides the human-readable workflow.
Treat fablish as a common typo alias for fable-ish; do not rename the plugin, skill, or directory.
Match verification depth to task risk.
Do not claim verification that was not observed.
Read only the reference needed for the current task:
references/workflow.md: mode selection, work-unit loop, optional review passes.references/verification.md: choosing and reporting proof.references/final-report.md: concise final report format.npx claudepluginhub chrisryugj/fable-ish --plugin fable-ishApplies Fable-inspired discipline to coding work: inspect before acting, track goals and findings, ground conclusions in evidence, verify before completion.
Enforces structured multi-step task execution with verification checkpoints. Use for autonomous work, debugging investigations, or building renderable artifacts (HTML, SVG).
Applies adversarial fresh-context review to non-trivial decisions in code. Use when correctness matters more than speed, in unfamiliar code, or for high-stakes operations.