groundwork

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

Generate implementation tasks from architecture document. Usage /groundwork:create-tasks

Create detailed product requirements document (PRD) for a feature. Usage /groundwork:design-product

Create design system with foundations, brand identity, and UX patterns. Usage /groundwork:ux-design

Build a feature from description with worktree isolation and TDD. Usage /groundwork:build-unplanned "Add user login"

Verify alignment between code and specs. Usage /groundwork:check-specs-alignment

This skill should be used when investigating bugs, unexpected behavior, test failures, or any code that does not work as expected - enforces systematic root cause analysis before any fix

This skill should be used when the user asks to design system architecture, make architectural decisions, or translate PRD into technical design

Dispatches a planned task/feature to the task-executor agent for worktree-isolated TDD implementation

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.

Synchronize architecture document with codebase changes. Usage /groundwork:source-architecture-from-code

Synchronize PRD with implemented codebase changes. Usage /groundwork:source-product-specs-from-code

Synchronize design system document with codebase changes. Usage /groundwork:source-ux-design-from-code

Start swarm debugging with parallel hypothesis investigation. Usage /groundwork:swarm-debug [bug description]

Design architecture using parallel advocate agents for adversarial technology comparison. Usage /groundwork:swarm-design-architecture

This skill should be used when the task list is complete to run multi-agent verification ensuring tasks cover PRD, follow architecture, and respect design system

This skill should be used when clarifying feature requests, gathering requirements, or checking for contradictions in proposed changes

This skill should be used when implementation is complete to run multi-agent verification with autonomous fix-and-retry until all agents approve

Execute next uncompleted task with full project context (PRD, architecture, tasks). Usage /groundwork:work-on-next-task

skill to "execute a task", "work on task N", or "implement TASK-NNN" - orchestrates worktree isolation, TDD implementation, validation, and merge.

Use before committing to a non-trivial module, service boundary, or public API - generate 2-3 divergent interface designs, compare them on depth/locality/seam, and recommend one

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

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

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

Ship a validated change to production - sequences observability and a staged rollout, then gates the outward-facing deploy behind a final go/no-go. Usage /groundwork:ship

Roll 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 flipping it on for everyone at once

This skill should be used when implementing any feature or bugfix, before writing implementation code

This skill should be used when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use 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 instead of building layer-by-layer

Validate the Groundwork plugin for common issues. Usage /groundwork:groundwork-check

List all Groundwork skills with descriptions. Usage /groundwork:groundwork-help

This skill should be used when configuring a repository for groundwork - detects single-project or monorepo structure and creates .groundwork.yml

List all available Groundwork skills with descriptions. Usage /groundwork:skills

This skill should be used when converting a single-file architecture doc to directory-based format for better organization of large architecture documents

This skill should be used when converting a single-file spec to directory-based format for better organization of large specifications

This skill should be used when starting feature work that needs isolation from current workspace - creates isolated git worktrees with smart directory selection and safety verification