56 lines
2.0 KiB
Markdown
56 lines
2.0 KiB
Markdown
---
|
|
name: org-agent-memex-workbreakdown
|
|
description: "Break down complex tasks into atomic TODOs before execution. Use when: a task feels complex, involves multiple files, or may cause context saturation. Prevents procrastination by forcing decomposition. NOT for: simple single-step tasks."
|
|
homepage: ""
|
|
metadata: { "openclaw": { "emoji": "🔨", "requires": { "bins": [] }, "user-invocable": true } }
|
|
---
|
|
|
|
# GTD Work Breakdown Skill
|
|
|
|
Meta-cognitive protocol to prevent stalling and context saturation.
|
|
|
|
## When to Use
|
|
|
|
✅ **USE this skill when:**
|
|
- A task feels "complex" or overwhelming
|
|
- It involves editing more than 3 files
|
|
- It requires holding multiple concepts in working memory
|
|
- You feel the urge to apologize or hesitate (procrastination signal)
|
|
- The task description is longer than 2 sentences
|
|
|
|
❌ **DON'T use this skill when:**
|
|
- Simple single-file edit
|
|
- Direct question/answer
|
|
- Already-broken-down TODO from GTD
|
|
|
|
## Instructions
|
|
|
|
### The Decomposition Protocol
|
|
|
|
When invoked, BEFORE executing any other action:
|
|
|
|
1. **Analyze Complexity**: Ask "How many discrete steps does this actually require?"
|
|
2. **Breakdown Threshold**: If >3 steps or >2 files affected, MUST decompose
|
|
3. **Create TODOs**: Write each atomic step as a separate `TODO` in `GTD.org` under appropriate project
|
|
4. **Assign Ownership**: Each TODO gets `:ASSIGNED: $MEMEX_USER` or `:ASSIGNED: $MEMEX_ASSISTANT`
|
|
5. **Set FIRST**: Mark only the first TODO as `NEXT`, rest remain `TODO`
|
|
6. **Execute First**: Complete ONLY the `NEXT` item
|
|
7. **Yield**: After completion, report to user: "[X] Completed [first task]. [N] tasks remaining in GTD. Continue?"
|
|
|
|
### Anti-Pattern Detection
|
|
|
|
If you find yourself:
|
|
- Thinking "I'll just do it all at once"
|
|
- Planning to edit >5 files before committing
|
|
- Writing conditional logic on the fly
|
|
|
|
STOP. Invoke this skill immediately.
|
|
|
|
## Complexity Checklist
|
|
|
|
Before executing any task, ask:
|
|
- [ ] Can I complete this in under 5 minutes?
|
|
- [ ] Does it touch only 1 file?
|
|
- [ ] Is the outcome predictable?
|
|
|
|
If ANY answer is "No", decompose first. |