brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
fable-reviewLaunch an independent Fable code review and return it verbatim. Use only when the user explicitly invokes /fable-review.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use Fable 5.1 Extra High through Claude Code, using the configured orchestration tool.
Read the orchestration tool's instructions and follow its launch checks. Discover provider/model/effort IDs rather than guessing. Reuse the current environment, including uncommitted work, and use the tool's coordination options when coordinating.
If the user names another harness, read its skill and use it with the same model, effort, workspace, brief, and output requirements. Report unavailable model/effort as blockers; never silently downgrade.
Give neutral context: scope, paths, intended behavior, and diff/base revision. Ask for a thorough senior-developer review, including related code and tests, without steering toward suspected bugs, solutions, or verdicts. Review only; do not change files. Request a concise plain-English report of serious or critical issues, fixes, and production merge readiness. Distinguish verified findings from uncertainty and identify validation gaps.
Use the orchestration tool's wait and output functions (or the selected harness's equivalents). Verify this review actually completed; idle status, timeouts, and queued retries are not completion. Report blockers rather than presenting partial output as a finished review.
Return the completed reviewer's full final response verbatim.