skynet/small-scripts
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

claude-profile modes: add deep-fable, orch pre-flight gate, ask-minimax re-point

Browse Source 
deep-fable.md (new):
- driver: fable (claude-fable-5), same plan-first/spec-first discipline as deep
- escalates_to: opus — Opus named workflows remain available
- status line: [Fable→Opus] deep-fable · <project>: <task> | N% ctx
- on context wipe mentions "Deep Work (Fable)"

deep.md:
- Gnarly-bug consult: bg-model-call -> /ask-minimax skill with Opus fallback
- Async policy: replace bg-model-call bullet with /ask-minimax + Opus-subagent-fallback
- Workflow stance: add SSH key pre-flight check before git push

quick.md:
- Workflow stance: add SSH key pre-flight check before git push

hybrid.md:
- Async policy: replace bg-model-call reference with /ask-minimax + Opus-subagent-fallback

orch.md:
- New section "Pre-flight gate (before the autoloop)" placed before Auto-fire
- Auto-fire step 1 rewritten: run pre-flight gate first, then /loop 2m /orchestrate
- Escalation triggers: add stuck-queue row (5 iterations no change -> stop, report)
- Out of scope: add "Run the autoloop without the pre-flight gate"

context/claude-profile-modes.md:
- Status line: 47 assertions; driver table updated; 6 mode files noted
- Remaining follow-ups: bg-model-call replaced by /ask-minimax; deep-fable noted
This commit is contained in:
Paul O'Reilly
2026-06-12 21:34:20 +12:00
parent 16586541ea
commit 864960cbbb
6 changed files with 107 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
data/claude-profile/modes/deep.md
View File

@@ -31,7 +31,7 @@ You are running as Sonnet. Fixed for the session. To get Opus reasoning, do NOT
## Async policy
- Background bash: enabled
- bg-model-call (third-party containers like MiniMax): enabled, via the `bg-model-call` wrapper. Results stream to files to keep context lean.
- Third-party delegation: the /ask-minimax skill (file-heavy grunt work, second opinions); on MiniMax failure, fall back to an Opus subagent.
- 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`
@@ -40,6 +40,7 @@ You are running as Sonnet. Fixed for the session. To get Opus reasoning, do NOT
- 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.
@@ -49,7 +50,7 @@ These are the ONLY ways Opus enters this mode. Each is a deliberate, high-value
| **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 | Use `bg-model-call` to consult MiniMax in the background with the full bug context written to a file. ScheduleWakeup to check the result. |
| **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