executing-plans
Execute detailed plans in batches with review checkpoints
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Execute detailed plans in batches with review checkpoints
Create isolated git worktrees with smart directory selection and safety verification
Complete feature development with structured options for merge, PR, or cleanup
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Validate at every layer data passes through to make bugs impossible
Replace arbitrary timeouts with condition polling for reliable async tests
Write the test first, watch it fail, write minimal code to pass
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Check all external inputs for validity - garbage in, nothing out, never garbage out
Maintain skills wiki health - check links, naming, cross-references, and coverage
Write comments explaining WHAT and WHY, never temporal context or history
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring g...
Use when working with VueUse composables - provides reactive utilities for state, browser APIs, sensors, network, animations. Check VueUse before writing custom composables - most patterns already implemented.
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
Create micro-commits (minimal incision) with at least one validation signal per commit.
Generate iterative `plan-N.md` files in the repo root (max N=5). Use only when asked; clarify before `plan-1.md`; stop at `plan-5.md`.
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
TRACE (Type/Readability/Atomic/Cognitive/Essential) lens for explaining code and proposing improvements (no edits applied).
Software surgery: contract → invariants → creative search → inevitable incision; minimal diff, compositional core, proof signal.
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity); requires a validation signal.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.