If during execution you realize the task is more complex than expected:
**Stop and escalate to full workflow:**
```
This task is more complex than anticipated. I recommend using the full
workflow instead:
- For research: /octo:discover "research authentication patterns"
- For planning: /octo:define "define auth requirements"
- For building: /octo:develop "implement auth system"
- For validation: /octo:deliver "validate auth implementation"
Would you like me to switch to a full workflow?
```
**Indicators to escalate:**
- Multiple files need changes
- Requires architectural decisions
- Needs research or comparison
- Security implications
- Performance implications
- Breaking changes
---
## Directory Structure
Quick mode creates summaries in a dedicated directory:
```
.claude-octopus/
└── quick/
├── 20260129-143045-summary.md
├── 20260129-150122-summary.md
└── 20260129-161530-summary.md
```
Each summary includes:
- Task description
- Changes made
- Files modified
- Commit hash
- Timestamp
---
## Comparison: Quick Mode vs Full Workflow
| Aspect | Quick Mode ⚡ | Full Workflow 🐙 |
|--------|-------------|------------------|
| **Time** | 1-3 minutes | 5-15 minutes |
| **Cost** | Claude only | Claude plus available external providers |
| **Providers** | 1 (Claude) | Available provider fleet |
| **Research** | None | Comprehensive |
| **Planning** | None | Detailed |
| **Validation** | Basic | Multi-AI review |
| **Best For** | Simple fixes | Complex features |
| **When to Use** | Known solution | Unknown solution |
---
## Best Practices
### DO:
- ✅ Use quick mode for straightforward tasks
- ✅ Create descriptive commit messages
- ✅ Generate summaries for audit trail
- ✅ Update state even in quick mode
- ✅ Escalate to full workflow if complexity increases
### DON'T:
- ❌ Use quick mode for new features
- ❌ Skip commits (always commit atomically)
- ❌ Skip state updates (maintain consistency)
- ❌ Use quick mode for security-sensitive changes
- ❌ Force quick mode when full workflow is appropriate
---
## Troubleshooting
### "Quick mode is taking too long"
→ Task is probably too complex. Escalate to full workflow.
### "Change broke tests"
→ Quick mode assumes simple, safe changes. Use full workflow for risky changes.
### "Need to research best approach"
→ Quick mode is for known solutions only. Use /octo:discover for research.
### "Multiple files need changes"
→ Consider /octo:develop for coordinated multi-file changes.
---
## Summary
Quick mode is the right tool for simple, straightforward tasks with known solutions. It provides fast execution while maintaining essential tracking and documentation.
For everything else, use the full Double Diamond workflow to ensure quality through multi-AI orchestration.
**Remember: Fast is good, but correct is better. When in doubt, use the full workflow.**
