Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Check work and detect drift before committing. A second opinion that catches misalignment early. Use at natural pause points, before PRs, or when something feels off.

Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.

Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.

Use this skill when working with the lightweight GitHub Flow branching model. Ideal for projects with continuous deployment where 'main' is always deployable.

Automatically discover workflow and task management skills when working with Beads. Activates for workflow development tasks.

Deliver code to users. Optimize the path from merged code to working install. Use when execution is complete and you need to get changes into users' hands.

Multi-specialist collaborative analysis to understand how features, functions, or components work

Git-aware undo by logical work unit (track, phase, or task)

Git-aware undo by logical work unit (track, phase, or task)

Git-aware undo by logical work unit (track, phase, or task)

Manage git worktrees for parallel development. Use to work on multiple branches simultaneously without stashing or switching contexts.