| name | work |
| description | Use when executing an approved plan - implements with TDD discipline, systematic debugging, worktree isolation, and progress tracking |
Work
Execute an approved plan; track completion in progress/feature-list.md.
Core principle: no production code without a failing test first. Evidence at every step.
When to Use
- User runs
/work after /plan produced an intent and feature list
- Resuming work on an in-progress task
Permission
| Directory | Access |
|---|
| decisions | R |
| progress | RW |
| solutions | R |
| reviews | — |
reviews/ is intentionally locked — work must not self-select based on pending review verdicts.
Routing
- Behavior:
src/commands/work.ts (runWork)
- State I/O: feature-list + current-task files in
src/dispatcher/state.ts
- TDD / debugging / worktree discipline: authoritative in the user's global spec
(
~/.claude/CLAUDE.md §7 validate, CLAUDE-extended.md §6 debug / §7-EXT evidence ladder),
not duplicated here.
- System overview:
plugins/sgc/CLAUDE.md
Execution
When this skill is invoked, dispatch to the sgc CLI:
bun src/sgc.ts work $ARGUMENTS
work does NOT spawn review agents. Call sgc review (and sgc qa for L2+) when all features are done.
Delegation hint
For TDD discipline during implementation:
sp:test-driven-development — write failing test first, then implement
