Loading...
Loading...
Found 102 Skills
Backend-agnostic task management. Use when: (1) creating, listing, updating, or archiving tasks; (2) analysing task status; (3) setting up task backend. NOT for: memory population (use memory); session management (use memory session).
Daily/weekly/monthly/git log population and session context management. Use when: (1) writing daily closeout log; (2) rolling up weekly/monthly memory; (3) recording git summary; (4) starting/ending sessions; (5) creating specs or docs. NOT for: task management (use task); compound loop (use work).
Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.
Create outcome spec (overview, decisions, steps, edge cases). Use $ARGUMENTS as spec topic if provided.
Execute the implementation plan, track progress in the task backend. Use after planning.
Create a 'how does X work' documentation file for a codebase component or concept. Use $ARGUMENTS as the doc topic if provided.
Capture and resolve deferred items from a session ('we'll come back to that'). Use $ARGUMENTS as the promise text, or --list / --resolve N.
Analyse task status and distribution across the configured backend.
List active tasks in the configured backend. Use to see current task status.
Analyse workflow trends: session ratings, recurring mistakes, and learnings over a period. Use for weekly or monthly reflection.
Clarify scope through dialogue, surface key decisions and open questions. Use before planning.
Research codebase, write concrete implementation plan. Use after brainstorming.