协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
fable-review【开发与工程】Launch an independent Fable code review and return it verbatim. Use only when the user explicitly invokes /fable-review.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
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.