Skip to content

LiorCohen/sdd / .claude/skills/tasks

Manage tasks and plans using the .tasks/ directory.

FileKindSize
SKILL.mdskill md12.5 KB
reference.mdmarkdown3.2 KB
schemas.mdmarkdown9.0 KB
workflows.mdmarkdown18.8 KB

reference.md

View on GitHub
# Task Management Reference

Best practices, conventions, and lifecycle documentation.

---

## Task Numbering

- Task numbers are permanent identifiers (never reused)
- Find highest number across ALL subdirs, increment by 1
- Numbers may have gaps (merges, deletions)
- Reference as `#N` or `task N`

---

## Best Practices

1. **Commit every transition** - Every state change (add, plan, plan-review, implement, review, complete, reject, consolidate, prioritize) must be committed immediately. Never leave task changes uncommitted. Use the commit skill with `-m` flag and the `Tasks:` prefix (e.g., `Skill(commit, args: '-m "Tasks: Move #19 to planning"')`). The commit skill ensures proper Co-Authored-By attribution
2. **Verify clean state after every command** - After every `/tasks` command completes, run `git status` to confirm no uncommitted changes remain in `.tasks/`. If any exist, stage and commit them before returning to the user
3. **Inbox first** - New tasks go to inbox, prioritize later
4. **Keep atomic** - One clear outcome per task
5. **Worktree per task** - `/tasks implement` creates a worktree at `.worktrees/task-<id>/`, keeping main clean
6. **Never lose work** - Before removing a worktree, always verify all commits are merged and no uncommitted changes exist
7. **Only `/tasks complete` cleans up** - Never merge the feature branch or delete the worktree during implementation or reviewing phases. Only `/tasks complete` may merge, remove the worktree, and delete the branch
8. **Consolidate related** - Don't duplicate effort
9. **Preserve on consolidate** - Never lose original task content when consolidating
10. **Update both** - Task folder AND INDEX.md must stay in sync
11. **Add context** - When completing, summarize what was done
12. **Date everything** - Completion dates help track velocity
13. **Branch isolation** - Feature branches only modify their associated task; new tasks go on main

---

## Lifecycles

### Task Lifecycle

```
                  0-inbox/ (open tasks)
                           ↓
                     [/tasks spec]
                           ↓
                     1-speccing/
                           ↓
                     [/tasks plan]
                           ↓
                     2-planning/
                           ↓
                 [/tasks plan-review]
                           ↓
                    3-plan-review/
                           ↓
                  [/tasks implement]
                           ↓
                   4-implementing/
                           ↓
                   [/tasks review]
                           ↓
                    5-reviewing/
                           ↓
                   [/tasks complete]
                           ↓
                     6-complete/

Any status → 8-consolidated/ (if combined with another)
Any status → 7-rejected/ (if irrelevant or out of scope)
```

**Priority** (high/medium/low) can be set at any point and only affects INDEX.md grouping (sub-sections under Inbox).

Plans are execution plans created during the planning phase — they define implementation order and sequencing for changes already fully specified in the spec. They move with their task folder through the lifecycle.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall