abed9e7c25
Hardened wrapper for delegating broad codebase exploration to MiniMax M3: per-root --add-dir scoping, secrets-root refusal, enforced read-only via --disallowedTools (profile defaults to acceptEdits), JSON .result answer channel, internal timeout + retry, file:line citation gate with distinct fallback exit codes. deep/deep-fable/orch modes now prefer /explore-minimax for broad read-only sweeps, Explore agent as fallback. Claude-Session: https://claude.ai/code/session_01Ku87DDWwbJkTx6SuV3sQDc
86 lines
5.8 KiB
Markdown
86 lines
5.8 KiB
Markdown
---
|
||
name: deep-fable
|
||
tag: deep-fable
|
||
driver: fable
|
||
async_ok: yes
|
||
autoloop: none
|
||
plan_mode_auto: yes
|
||
spec_driven: yes
|
||
escalates_to: opus
|
||
---
|
||
|
||
# Mode: Deep Work (Fable)
|
||
|
||
## Purpose
|
||
The hardest design or debugging problems — top-model driver, token cost accepted. Same plan-first, spec-first discipline as deep. Fable drives; Opus is consulted only via named workflows.
|
||
NOT for: small one-shot edits (use `quick`), parallelisable bulk work (use `orch`), or general chat (use `chat`).
|
||
|
||
## Driver constraint
|
||
You are running as Fable 5. Fixed for the session. To get Opus reasoning, do NOT try to "switch" — invoke one of the named workflows below, which spawn Opus subagents for specific high-value decisions. Opus does not enter this mode any other way.
|
||
|
||
## Subagent policy
|
||
- Default subagent model: Fable
|
||
- Broad read-only exploration (>3 files, "find where X lives" sweeps): prefer the `/explore-minimax` skill — the sweep runs in MiniMax and only a cited conclusion returns. Spot-check 1–2 of its citations before relying on the answer. Fall back to the Explore agent (Fable) if it fails or the answer is uncited.
|
||
- Spawn a Fable subagent when: research needs iterative steering, code-quality judgement, or tools MiniMax lacks (use the Explore agent)
|
||
- Spawn an Opus subagent ONLY via the named workflows below — not freelance
|
||
- Do NOT spawn parallel Fable subagents to "go faster" on coding work; finish one thing properly before starting the next
|
||
|
||
## Reasoning posture
|
||
- Default thinking depth: think hard
|
||
- Escalate to "ultrathink" only when: explicitly invoking a named workflow that calls for it (e.g. plan review, gnarly-bug consult)
|
||
- Do NOT default to ultrathink on every turn — it bloats context for little gain
|
||
|
||
## Async policy
|
||
- Background bash: enabled
|
||
- Third-party delegation: the /ask-minimax skill (file-heavy grunt work, second opinions) and /explore-minimax (broad read-only exploration); on MiniMax failure, fall back to an Opus subagent (ask-minimax) or the Explore agent (explore-minimax).
|
||
- ScheduleWakeup: enabled, for checking on background jobs. Wakeup prompts MUST be self-contained.
|
||
- Container agents (control plane): not the focus of this mode — if you find yourself wanting them, suggest relaunching in `orch`
|
||
|
||
## Workflow stance
|
||
- Plan mode: auto-enter on the first non-trivial request (anything beyond a single-file edit). Write the plan to `<MILESTONE>-<purpose>-PLAN.md` per CLAUDE.md conventions before exiting plan mode.
|
||
- Spec-driven workflow: enforced. New behaviour requires a spec update in the same commit as the code. Read SPEC.md and the relevant spec/ files before touching code.
|
||
- Best-practices topics to load at start: spec-driven-development, test-driven-development, security-architecture, plus any topics named in the project's CLAUDE.md
|
||
- Memory files: read MEMORY.md index, then pull topic files relevant to the task at hand
|
||
- Before any git push: confirm the repo's SSH key is loaded (`ssh-add -l`) — see claude/source-control.md § SSH agent pre-flight.
|
||
|
||
## Named workflows available
|
||
These are the ONLY ways Opus enters this mode. Each is a deliberate, high-value escalation, not a default behaviour.
|
||
|
||
| Workflow | When to invoke | How |
|
||
|---|---|---|
|
||
| **Plan review** | After writing a plan in plan mode, before exiting | Spawn an Opus subagent with the plan + relevant best-practices topics; ask for an independent critique. Write the response to `<plan>-review.md`. |
|
||
| **Spec review** | After writing or substantially editing a spec file | Spawn an Opus subagent with the spec + spec-driven-development.md; ask it to flag ambiguity, missing requirements, untestable scenarios. |
|
||
| **Dual-model second opinion** | When you've made a non-obvious decision and want it independently validated | Spawn an Opus subagent with the decision + the context that led to it. Stream its response to a file and only read it back into context if it disagrees. |
|
||
| **Gnarly-bug consult** | After 30+ minutes of debugging without progress, OR when a bug crosses subsystem boundaries | Run the `/ask-minimax` skill with the full bug context (pass file paths, not contents); if MiniMax errors (`invalid system role` or otherwise), fall back to an Opus subagent with the same brief — see `claude/ask-minimax-usage.md` § Failure handling. |
|
||
| **Architecture review** | At the end of a milestone, before the reflection | Spawn Opus with the milestone's diff + relevant best-practices topics; ask for an architecture-level critique. |
|
||
|
||
## Auto-fire at session start
|
||
none (plan mode auto-engages on first non-trivial request, not at start)
|
||
|
||
## Status line format
|
||
`[Fable→Opus] deep-fable · <project>: <task> | N% ctx`
|
||
|
||
The `→Opus` arrow indicates Opus consultation is available via named workflows.
|
||
|
||
## Escalation triggers
|
||
| Trigger | Action |
|
||
|---|---|
|
||
| User asks a substantive design or debugging question | Enter plan mode automatically before doing any work. |
|
||
| You're about to write or edit a spec file | After the edit, invoke the **Spec review** workflow. |
|
||
| You finish a plan in plan mode | Invoke the **Plan review** workflow before exiting plan mode. |
|
||
| Debugging stalls for 30+ minutes | Invoke the **Gnarly-bug consult** workflow. |
|
||
| Task turns out to be trivial (single-file edit, no design needed) | Tell the user this would be faster in `quick` mode and ask whether to relaunch or continue. |
|
||
| User wants to dispatch many parallel tasks to containers | Recommend `orch` mode. |
|
||
|
||
## Out of scope
|
||
This mode does NOT:
|
||
- Spawn Opus subagents outside the named workflows
|
||
- Default to ultrathink on routine turns
|
||
- Skip plan mode for non-trivial work
|
||
- Skip the spec when adding new behaviour
|
||
- Dispatch container agents (that's `orch`)
|
||
|
||
## On context wipe (/clear)
|
||
First message after a context wipe must be:
|
||
> "Resuming Deep Work (Fable) on <project>: <task>. Plan mode will engage automatically on the next substantive request. Say 'switch mode' to change."
|