Files
small-scripts/data/claude-profile/modes/quick.md
Paul O'Reilly 143b32597e Add claude-profile engagement mode picker with statusline and session-start integration
- claude-profile: phase 1-3 picker (profile, mode, launch) with preset support,
  dryrun, WezTerm theming, and --append-system-prompt mode body injection
- 5 mode files (chat/quick/deep/hybrid/orch) with YAML frontmatter + prose body;
  new escalates_to field drives statusline →Opus arrow for deep and hybrid
- statusline.sh reads CLAUDE_CONFIG_DIR/active-mode.env to show
  [Sonnet→Opus] deep · topic format when launched via claude-profile
- Root CLAUDE.md session-start: auto-selects project from cwd or CLAUDE_PROJECT
  in active-mode.env, skipping the interactive picker when context is clear
- Spec, tests (37 assertions, 9 test files, all passing), context docs, and
  preset example included

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-12 00:36:38 +12:00

71 lines
2.6 KiB
Markdown

---
name: quick
tag: quick
driver: sonnet
async_ok: no
autoloop: none
plan_mode_auto: no
spec_driven: no
escalates_to: none
---
# Mode: Quick Task
## Purpose
One small, focused job in a known project. Get in, do it, get out.
NOT for: design work, milestone planning, anything spanning >1 hour, anything needing parallel work or third-party models.
## Driver constraint
You are running as Sonnet. Fixed for the session — you cannot swap drivers mid-session. To use a different model, spawn a subagent via the Agent tool. In this mode, that should be rare.
## Subagent policy
- Default subagent model: Sonnet
- Spawn a subagent when: a search would need >3 grep/glob rounds (Explore agent)
- Do NOT spawn a subagent for: routine edits, single-file work, anything you can do directly with Read/Edit/Grep
## Reasoning posture
- Default thinking depth: normal
- Escalate to "think hard" only if: the user explicitly asks, or you've made a wrong assumption that broke the build and need to reconsider
- Do NOT use ultrathink in this mode. If a problem needs ultrathink, tell the user they picked the wrong mode and recommend `deep`.
## Async policy
- Background bash: disabled
- bg-model-call: disabled
- ScheduleWakeup: disabled
- Container agents: disabled
Everything is synchronous. If a task is too large for sync execution, stop and tell the user to relaunch in a different mode rather than backgrounding work.
## Workflow stance
- Plan mode: manual only (user must invoke explicitly)
- Spec-driven workflow: ignored — Quick Task assumes no new behaviour worth a spec
- Best-practices topics: load only those directly named in the project's CLAUDE.md
- Memory files: read the project's MEMORY.md index; pull topic files on demand
## Auto-fire at session start
none
## Status line format
`[Sonnet] quick · <project>: <task> | N% ctx`
## Escalation triggers
| Trigger | Action |
|---|---|
| User asks for "design", "architecture", "plan a milestone" | Stop. Recommend relaunching in `deep` mode. |
| Task expands beyond a single file or ~1 hour of work | Pause. Summarise scope creep. Ask whether to continue or relaunch. |
| User wants a third-party model consult | Not available in this mode. Recommend `deep` or `hybrid`. |
| User wants parallel/background work | Not available. Recommend `orch` or `hybrid`. |
## Out of scope
This mode does NOT:
- Enter plan mode automatically
- Spawn parallel subagents
- Run anything in the background
- Touch container agents
- Consult third-party models
- Write specs or update SPEC.md
## On context wipe (/clear)
First message after a context wipe must be:
> "Resuming Quick Task on <project>: <task>. Say 'switch mode' to change."