Skills MCP Plugins Subagents

Browse by category

DevOps & CI/CD Skills Productivity & Workflow Skills Other Skills Product & Project Management Skills Documentation & Knowledge Skills Code Review & Refactor Skills Backend & APIs Skills Agent Meta & Communication Skills Research Skills Security Skills UX UI & Design Skills Testing & QA Skills See all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →

Agent Skills MCP Servers Plugins Subagents Coding Agents

Collections Official publishers Glossary FAQ Blog Search Saved Feedback

Privacy Terms llms.txt Sitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/etr/groundwork

home/skills/etr/groundwork

etr/groundwork

41 skills

$npx skills add etr/groundwork

SkillInstalls

build-unplannedBuild a feature from description with worktree isolation and TDD. Usage /groundwork:build-unplanned "Add user login—check-specs-alignmentVerify alignment between code and specs. Usage /groundwork:check-specs-alignment—create-tasksGenerate implementation tasks from architecture document. Usage /groundwork:create-tasks—debugThis skill should be used when investigating bugs, unexpected behavior, test failures, or any code that does not work as expected - enforces systematic root…—design-architectureThis skill should be used when the user asks to design system architecture, make architectural decisions, or translate PRD into technical design—design-it-twiceUse before committing to a non-trivial module, service boundary, or public API - generate 2-3 divergent interface designs, compare them on depth/locality/seam,…—design-productCreate detailed product requirements document (PRD) for a feature. Usage /groundwork:design-product—domain-modelingUse when designing a product or feature and the project lacks shared, agreed terminology - builds and maintains a pure domain glossary so agents speak one…—doubt-driven-developmentUse when building a high-stakes or hard-to-reverse change - schema/data migrations, auth, payments, public API surface, destructive operations, or concurrency…—groundwork-checkValidate the Groundwork plugin for common issues. Usage /groundwork:groundwork-check—groundwork-helpList all Groundwork skills with descriptions. Usage /groundwork:groundwork-help—handoffUse when ending a session or passing work to another agent - produces a compact handoff document that transfers context, state, and next objective without…—implement-taskDispatches a planned task/feature to the task-executor agent for worktree-isolated TDD implementation—instrument-observabilityInstrument a change with structured logging, RED metrics, trace spans, and symptom-based alerts - use while building the change, not after an incident proves…—just-do-itExecute all remaining tasks in sequence until completion. Usage /groundwork:just-do-it—just-do-it-swarmingExecute all remaining tasks using agent teams for context isolation. Each task runs in its own session. Usage /groundwork:just-do-it-swarming [--parallel]—plan-taskPlans a task or feature - loads context, optionally clarifies requirements, spawns Plan agent, persists plan to .groundwork-plans/—review-prReview 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.—select-projectThis 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—setup-repoThis skill should be used when configuring a repository for groundwork - detects single-project or monorepo structure and creates .groundwork.yml—shipShip a validated change to production - sequences observability and a staged rollout, then gates the outward-facing deploy behind a final go/no-go.—skillsList all available Groundwork skills with descriptions. Usage /groundwork:skills—source-architecture-from-codeSynchronize architecture document with codebase changes. Usage /groundwork:source-architecture-from-code—source-product-specs-from-codeSynchronize PRD with implemented codebase changes. Usage /groundwork:source-product-specs-from-code—source-ux-design-from-codeSynchronize design system document with codebase changes. Usage /groundwork:source-ux-design-from-code—split-architectureThis skill should be used when converting a single-file architecture doc to directory-based format for better organization of large architecture documents—split-specsThis skill should be used when converting a single-file spec to directory-based format for better organization of large specifications—staged-rolloutRoll out a change in stages behind a feature flag with a monitoring window and a written rollback plan - use before shipping anything user-facing, instead of…—statuslineUse when installing or uninstalling Groundwork's optional statusline configuration—swarm-debugStart swarm debugging with parallel hypothesis investigation. Usage /groundwork:swarm-debug [bug description]—swarm-design-architectureDesign architecture using parallel advocate agents for adversarial technology comparison. Usage /groundwork:swarm-design-architecture—task-validation-loopThis skill should be used when the task list is complete to run multi-agent verification ensuring tasks cover PRD, follow architecture, and respect design…—test-driven-developmentThis skill should be used when implementing any feature or bugfix, before writing implementation code—understanding-feature-requestsThis skill should be used when clarifying feature requests, gathering requirements, or checking for contradictions in proposed changes—use-git-worktreeThis skill should be used when starting feature work that needs isolation from current workspace - creates isolated git worktrees with smart directory…—using-groundworkThis skill should be used when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response…—ux-designCreate design system with foundations, brand identity, and UX patterns. Usage /groundwork:ux-design—validateThis skill should be used when implementation is complete to run multi-agent verification with autonomous fix-and-retry until all agents approve—vertical-sliceUse when building a feature large enough to span multiple layers - structure the work as thin, end-to-end, independently-shippable slices behind a feature flag…—work-onskill to "execute a task", "work on task N", or "implement TASK-NNN" - orchestrates worktree isolation, TDD implementation, validation, and merge.—work-on-next-taskExecute next uncompleted task with full project context (PRD, architecture, tasks). Usage /groundwork:work-on-next-task—