Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/skill-quick/SKILL.mdFast-track execution for small tasks that don't need full Double Diamond workflow overhead.
Bug Fixes:
Configuration Changes:
Small Refactorings:
Documentation:
Dependency Management:
Complex Work:
Use full workflows for complex work to ensure quality.
Quick mode follows a streamlined process:
User Request → Direct Implementation → Atomic Commit → SummaryWhat Quick Mode SKIPS:
What Quick Mode KEEPS:
/octo:quick "add dark mode toggle to settings"Use skill: octopus-quick
Task: "fix typo in README.md line 42"/octo:quick "update Next.js to v15"
/octo:quick "fix the broken import in auth.ts"
/octo:quick "add error handling to login function"
/octo:quick "remove console.log statements"Quickly assess:
Inspect the existing index and working-tree diff before editing. Select only task-owned paths. If a selected file already contains unrelated changes, use a deliberate partial-commit workflow instead of quick mode. Leave unrelated files and their staged changes intact.
Implement directly using appropriate tools:
Always create a descriptive commit:
# Replace this array with the exact task-owned paths, including deletions.
QUICK_FILES=("path/to/task-file")
git --literal-pathspecs add -- "${QUICK_FILES[@]}" || exit 1
# Commit only those paths; preserve unrelated staged files in the index.
git --literal-pathspecs commit --only -m "quick: [brief description]
[Detailed explanation if needed]
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>" -- "${QUICK_FILES[@]}" || exit 1If staging or committing fails, stop the workflow. Do not record successful execution, generate a completion summary, or report an earlier commit as this task's result. Preserve the edits for recovery.
Commit message format:
quick: to indicate quick mode# Update state with quick task execution
"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}/.claude-octopus/plugin}}/scripts/state-manager.sh" write_decision \
"quick" \
"$(git log -1 --pretty=%s)" \
"Ad-hoc task executed in quick mode"
# Update metrics
"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}/.claude-octopus/plugin}}/scripts/state-manager.sh" update_metrics \
"execution_time" \
"1" # Estimated in minutes# Create quick task summary
mkdir -p .claude-octopus/quick
summary_file=".claude-octopus/quick/$(date +%Y%m%d-%H%M%S)-summary.md"
cat > "$summary_file" <<EOF
# Quick Task: $(git log -1 --pretty=%s)
## Task Description
$TASK_DESCRIPTION
## Changes Made
$(git diff HEAD~1..HEAD --stat)
## Files Modified
$(git diff --name-only HEAD~1..HEAD)
## Commit
$(git rev-parse HEAD)
## Timestamp
$(date -u +%Y-%m-%dT%H:%M:%SZ)
---
*Executed in Quick Mode - minimal overhead execution*
EOF
echo "📝 Summary saved to: $summary_file"User Request:
/octo:quick "fix typo in README - change 'recieve' to 'receive'"Execution:
Read the file
Read README.md to locate the typoMake the change
Edit README.md: replace "recieve" with "receive"Commit atomically
git --literal-pathspecs add -- README.md || exit 1
git --literal-pathspecs commit --only -m "quick: fix typo in README (recieve → receive)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>" -- README.md || exit 1Record in state
state-manager.sh write_decision "quick" \
"Fixed typo in README" \
"Ad-hoc documentation fix"Generate summary
Created: .claude-octopus/quick/20260129-143045-summary.mdReport to user
✅ Fixed typo in README.md
📝 Commit: abc123f
📋 Summary: .claude-octopus/quick/20260129-143045-summary.mdIf 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:
Quick mode creates summaries in a dedicated directory:
.claude-octopus/
└── quick/
├── 20260129-143045-summary.md
├── 20260129-150122-summary.md
└── 20260129-161530-summary.mdEach summary includes:
| 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 |
→ Task is probably too complex. Escalate to full workflow.
→ Quick mode assumes simple, safe changes. Use full workflow for risky changes.
→ Quick mode is for known solutions only. Use /octo:discover for research.
→ Consider /octo:develop for coordinated multi-file changes.
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.
nyldn/claude-octopus
9a6967a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.