domain-modeling
Use when designing a product or feature and the project lacks shared, agreed terminology - builds and maintains a pure domain glossary so agents speak one language
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when designing a product or feature and the project lacks shared, agreed terminology - builds and maintains a pure domain glossary so agents speak one language
Use when building a high-stakes or hard-to-reverse change - schema/data migrations, auth, payments, public API surface, destructive operations, or concurrency - to adversarially refute the chosen approach BEFORE committing to it
Validate the Groundwork plugin for common issues. Usage /groundwork:groundwork-check
List all Groundwork skills with descriptions. Usage /groundwork:groundwork-help
Use when ending a session or passing work to another agent - produces a compact handoff document that transfers context, state, and next objective without copying source material
Dispatches a planned task/feature to the task-executor agent for worktree-isolated TDD implementation
Instrument a change with structured logging, RED metrics, trace spans, and symptom-based alerts - use while building the change, not after an incident proves it was unobservable
Execute all remaining tasks in sequence until completion. Usage /groundwork:just-do-it
Execute all remaining tasks using agent teams for context isolation. Each task runs in its own session. Usage /groundwork:just-do-it-swarming [--parallel]
Plans a task or feature - loads context, optionally clarifies requirements, spawns Plan agent, persists plan to .groundwork-plans/
Review a GitHub PR using multi-agent verification. Usage /groundwork:review-pr [PR number or URL]. Pass --no-interactive to skip all prompts and auto-publish.
This skill should be used when the user wants to switch between projects in a monorepo - lists projects from .groundwork.yml and sets the active project
Rules for HTTP API endpoints. Use when adding or changing any endpoint (route, request or response shape, status codes), especially login and ones that read or change other users' data.
Rules for code that writes to the database where two requests, retries or jobs can run at once. Use for anything that changes money, stock, balances, counters or statuses, creates rows that must be unique, or calls a payment provider, email or other outside service. Applies in en
Rules for database schema changes. Use for any new table, column, index, constraint, enum or trigger, any data backfill, and any migration file.
API security best practices and common vulnerability prevention. Enforces security checks for authentication, input validation, SQL injection, XSS, and OWASP Top 10 vulnerabilities. Use when building or modifying APIs.
Catalog captured:2026-11-21