|
| 1 | +# Quick Extension - Session-Based Ad-Hoc Task Execution |
| 2 | + |
| 3 | +A streamlined, session-based workflow for ad-hoc task execution without file artifacts. Quick compresses the full spec-driven workflow into a single command with conversation-only interactions. |
| 4 | + |
| 5 | +## Overview |
| 6 | + |
| 7 | +Quick follows the 12-factors methodology in a compact, single-command session: |
| 8 | + |
| 9 | +``` |
| 10 | +Mission Brief → Context Discovery → Plan Generation → Task Breakdown → Execution |
| 11 | +``` |
| 12 | + |
| 13 | +**No file artifacts are created** - everything happens in the conversation with your AI agent. |
| 14 | + |
| 15 | +## Quick Start |
| 16 | + |
| 17 | +```bash |
| 18 | +/quick.implement "fix authentication bug in login flow" |
| 19 | +``` |
| 20 | + |
| 21 | +## How It Works |
| 22 | + |
| 23 | +### Phase 1: Mission Brief |
| 24 | +Quick asks 2-3 questions to understand what you're doing: |
| 25 | +- What needs to be done? |
| 26 | +- What defines success? |
| 27 | +- Any constraints? |
| 28 | + |
| 29 | +**Approval #1**: You see the Mission Brief and confirm before proceeding. |
| 30 | + |
| 31 | +### Phase 2: Context Discovery |
| 32 | +You provide any relevant context: |
| 33 | +- Project files to examine |
| 34 | +- Documentation to reference |
| 35 | +- Technical constraints |
| 36 | +- Examples to follow |
| 37 | + |
| 38 | +### Phase 3: Plan Generation (Internal) |
| 39 | +Quick mentally plans the approach based on your brief and context. This is AI internal reasoning - not displayed. |
| 40 | + |
| 41 | +### Phase 4: Task Breakdown |
| 42 | +Quick generates a concrete task checklist: |
| 43 | +```markdown |
| 44 | +- [ ] Add error handling to login API |
| 45 | +- [ ] Update session token validation |
| 46 | +- [ ] Add unit tests for auth flow |
| 47 | +- [ ] Update documentation |
| 48 | +``` |
| 49 | + |
| 50 | +**Approval #2**: You see the full task list and confirm before execution. |
| 51 | + |
| 52 | +### Phase 5: Sequential Execution |
| 53 | +Quick executes tasks one at a time: |
| 54 | +- Displays task being executed |
| 55 | +- Makes necessary code changes |
| 56 | +- Shows what was done |
| 57 | +- Confirms completion |
| 58 | + |
| 59 | +**Stop on error**: If a task fails, Quick stops and asks what to do next. |
| 60 | + |
| 61 | +### Phase 6: Summary |
| 62 | +Quick shows completion status: |
| 63 | +- All tasks completed ✅ |
| 64 | +- Files modified |
| 65 | +- Next steps (testing, review, etc.) |
| 66 | + |
| 67 | +## When to Use Quick |
| 68 | + |
| 69 | +### Perfect For: |
| 70 | +- Ad-hoc bug fixes |
| 71 | +- Small features |
| 72 | +- Refactoring tasks |
| 73 | +- Documentation updates |
| 74 | +- Quick experiments |
| 75 | + |
| 76 | +### Not For: |
| 77 | +- Large-scale features (use full spec-driven workflow) |
| 78 | +- Architecture changes (use `/architect` extension) |
| 79 | +- Complex multi-phase projects (use `/spec.specify`, `/spec.plan`, `/spec.tasks`, `/spec.implement`) |
| 80 | +- Projects requiring extensive documentation (use full workflow) |
| 81 | + |
| 82 | +## Commands |
| 83 | + |
| 84 | +| Command | Purpose | |
| 85 | +|---------|---------| |
| 86 | +| `/quick.implement` | Session-based ad-hoc task execution | |
| 87 | + |
| 88 | +## Key Differences from Full Workflow |
| 89 | + |
| 90 | +| Aspect | Quick | Full Workflow | |
| 91 | +|--------|-------|---------------| |
| 92 | +| File Artifacts | None (session-only) | spec.md, plan.md, tasks.md, etc. | |
| 93 | +| Commands | 1 (`/quick.implement`) | 4+ commands | |
| 94 | +| Interaction | 2 approval points | Review at each stage | |
| 95 | +| Task Complexity | Simple checklist | Detailed task breakdown with phases | |
| 96 | +| Use Case | Ad-hoc, small tasks | Full-featured spec-driven development | |
| 97 | + |
| 98 | +## Execution Flow |
| 99 | + |
| 100 | +```text |
| 101 | +/quick.implement "your task description" |
| 102 | + ↓ |
| 103 | +Phase 1: Mission Brief (2-3 questions) |
| 104 | + ↓ |
| 105 | +Approval #1: "Proceed with this brief?" |
| 106 | + ↓ |
| 107 | +Phase 2: Context Discovery (user provides context) |
| 108 | + ↓ |
| 109 | +Phase 3: Plan Generation (AI internal planning) |
| 110 | + ↓ |
| 111 | +Phase 4: Task Breakdown (show checklist) |
| 112 | + ↓ |
| 113 | +Approval #2: "Proceed with these tasks?" |
| 114 | + ↓ |
| 115 | +Phase 5: Sequential Execution |
| 116 | + ↓ |
| 117 | +Phase 6: Summary |
| 118 | +``` |
| 119 | + |
| 120 | +## Error Handling |
| 121 | + |
| 122 | +If a task fails during execution: |
| 123 | + |
| 124 | +```markdown |
| 125 | +❌ Task Failed: Add error handling to login API |
| 126 | + |
| 127 | +Error: TypeError: Cannot read property 'token' of undefined |
| 128 | + |
| 129 | +What would you like to do? |
| 130 | +- Retry this task |
| 131 | +- Skip and continue to next task |
| 132 | +- Stop execution |
| 133 | +``` |
| 134 | + |
| 135 | +Quick **always stops on error** and waits for your decision. |
| 136 | + |
| 137 | +## Examples |
| 138 | + |
| 139 | +### Example 1: Bug Fix |
| 140 | + |
| 141 | +```bash |
| 142 | +/quick.implement "fix login page not redirecting after authentication" |
| 143 | +``` |
| 144 | + |
| 145 | +**Mission Brief**: |
| 146 | +- Goal: Fix login redirect issue |
| 147 | +- Success: Login redirects to dashboard after successful auth |
| 148 | +- Constraints: Must work with existing session token |
| 149 | + |
| 150 | +**Task Breakdown**: |
| 151 | +- [ ] Investigate login component redirect logic |
| 152 | +- [ ] Fix redirect condition bug |
| 153 | +- [ ] Test redirect flow |
| 154 | +- [ ] Verify integration |
| 155 | + |
| 156 | +### Example 2: Small Feature |
| 157 | + |
| 158 | +```bash |
| 159 | +/quick.implement "add dark mode toggle to settings page" |
| 160 | +``` |
| 161 | + |
| 162 | +**Mission Brief**: |
| 163 | +- Goal: Add dark mode toggle |
| 164 | +- Success: Button toggles theme, persists preference |
| 165 | +- Constraints: Use existing theme system |
| 166 | + |
| 167 | +**Task Breakdown**: |
| 168 | +- [ ] Add toggle UI component |
| 169 | +- [ ] Implement theme switch logic |
| 170 | +- [ ] Persist theme preference |
| 171 | +- [ ] Test theme switching |
| 172 | + |
| 173 | +## Installation |
| 174 | + |
| 175 | +Quick is **bundled by default** in new projects: |
| 176 | + |
| 177 | +```bash |
| 178 | +specify init my-project |
| 179 | +# Quick extension is automatically included |
| 180 | +``` |
| 181 | + |
| 182 | +For manual installation: |
| 183 | + |
| 184 | +```bash |
| 185 | +specify extension add quick |
| 186 | +``` |
| 187 | + |
| 188 | +## Configuration |
| 189 | + |
| 190 | +Quick requires **no configuration** - it's designed to work out-of-the-box for session-based tasks. |
| 191 | + |
| 192 | +## Limitations |
| 193 | + |
| 194 | +1. **No file artifacts** - Quick doesn't save workflow state to files |
| 195 | +2. **Session-only** - History is lost after conversation ends |
| 196 | +3. **Sequential execution** - One task at a time, no parallel work |
| 197 | +4. **Simple task structure** - No complex phases, dependencies, or sync/async modes |
| 198 | +5. **Error handling required** - Must interact with user on failures |
| 199 | + |
| 200 | +## Comparison to Full Spec-Driven Workflow |
| 201 | + |
| 202 | +### Full Workflow (spec.md, plan.md, tasks.md, implement.md) |
| 203 | +- Comprehensive documentation |
| 204 | +- Multiple review checkpoints |
| 205 | +- Complex task breakdown with phases |
| 206 | +- Sync/async execution modes |
| 207 | +- Atomic commits (configurable) |
| 208 | +- File-based state management |
| 209 | + |
| 210 | +### Quick (/quick.implement) |
| 211 | +- No documentation files |
| 212 | +- 2 approval points only |
| 213 | +- Simple task checklist |
| 214 | +- Sequential execution only |
| 215 | +- No auto-commits |
| 216 | +- Session-only workflow |
| 217 | + |
| 218 | +## Related Extensions |
| 219 | + |
| 220 | +- **architect** - Architecture decision records and documentation |
| 221 | +- **levelup** - Context module discovery and contribution |
| 222 | + |
| 223 | +## License |
| 224 | + |
| 225 | +MIT |
| 226 | + |
| 227 | +## Author |
| 228 | + |
| 229 | +Agentic SDLC Team |
| 230 | + |
| 231 | +## Repository |
| 232 | + |
| 233 | +https://github.com/tikalk/agentic-sdlc-spec-kit/tree/main/extensions/quick |
0 commit comments