This commit is contained in:
2026-03-10 13:09:47 +00:00
parent e0c4c2ed7b
commit ffd0d31fa5
43 changed files with 532 additions and 749 deletions

View File

@@ -1,6 +1,8 @@
---
name: work-decomposition
description: Procedure for decomposing multi-feature requests into independent workstreams — load when user requests 3+ features or features span independent domains
description: Procedure for decomposing multi-feature requests into independent workstreams
— load when user requests 3+ features or features span independent domains
permalink: opencode-config/skills/work-decomposition/skill
---
## When to Load
@@ -106,7 +108,7 @@ When triggering a checkpoint, present:
Do not interrupt the user for:
- Implementation details (naming, file organization, code patterns)
- Choices fully determined by existing codebase conventions
- Decisions already covered by prior user answers or cached guidance in `.memory/decisions.md`
- Decisions already covered by prior user answers or cached guidance in basic-memory project `decisions/` notes
## Coder Dispatch Rules
@@ -132,7 +134,7 @@ Each coder dispatch MUST include:
2. **Specific file paths and edit points** from discovery (not vague references)
3. **Discovered values verbatim**: i18n keys, API signatures, component names, existing patterns
4. **Worktree path** for all file operations
5. **Active plan file path** for the task (for example: `.memory/plans/<feature>.md`)
5. **Active plan note** for the task (for example: a basic-memory project `plans/<feature>` note)
6. **Quality tier** so coder understands the expected rigor
### Anti-patterns — Never Do These
@@ -196,4 +198,4 @@ Decomposition:
- One worktree, one branch, one PR
- Coder A: toggle + persistence together (they share state)
- Or split if toggle is pure UI and persistence is API: two coder calls
```
```