Define → Ship, one command per phase
Most skill packs are a flat list. agent-skills is organized the way software actually gets built - six phases, eight commands, with a human checkpoint at each step and the right skills loading automatically.
- Define Idea Refine
/spec - Plan Spec PRD
/plan - Build Code Impl
/build - Verify Test Debug
/test - Review QA Gate
/review - Ship Go Live
/ship
The eight commands
/spec Define what to build
Spec before code
/plan Plan how to build it
Small, atomic tasks
/build Build incrementally
One slice at a time
/test Prove it works
Tests are proof
/review Review before merge
Improve code health
/webperf Audit web performance
Measure before you optimize
/code-simplify Simplify the code
Clarity over cleverness
/ship Ship to production
Faster is safer
Want fewer manual steps? /build auto generates the plan and
implements every task in one approved pass - you approve the plan once, then it runs
autonomously. It removes the human stepping between tasks, not the verification:
every task is still test-driven and committed individually, and it pauses on failures.
Skills by phase
Reach for any skill directly, or let the meta-skill route you.
Meta
Route work to the right skill and set shared operating rules.
Define
/spec Clarify what to build before a line of code is written.
Plan
/plan Break the spec into small, verifiable, ordered tasks.
Build
/build Write the code in thin, tested vertical slices.
- incremental-implementation Thin vertical slices - implement, test, verify, commit. Rollback-friendly changes.
- test-driven-development Red-Green-Refactor, the test pyramid, DAMP over DRY, the Beyoncé Rule.
- context-engineering Feed agents the right information at the right time - rules files, context packing, MCP.
- source-driven-development Ground every framework decision in official docs - verify, cite, flag the unverified.
- doubt-driven-development Adversarial fresh-context review of every non-trivial decision, in-flight.
- frontend-ui-engineering Component architecture, design systems, state, responsive, WCAG 2.1 AA accessibility.
- api-and-interface-design Contract-first design, Hyrum’s Law, the One-Version Rule, error semantics.
Verify
/test Prove it works with real runtime evidence.
Review
/review Quality, security and performance gates before merge.
- code-review-and-quality Five-axis review, ~100-line change sizing, severity labels, review-speed norms.
- code-simplification Chesterton’s Fence, the Rule of 500 - cut complexity while preserving behavior.
- security-and-hardening OWASP Top 10 prevention, auth patterns, secrets, dependency auditing.
- performance-optimization Measure-first - Core Web Vitals targets, profiling, bundle analysis, N+1 fixes.
Ship
/ship Deploy with confidence - rollout, rollback, observe.
- git-workflow-and-versioning Trunk-based development, atomic commits, ~100-line changes, commit-as-save-point.
- ci-cd-and-automation Shift Left, Faster is Safer, feature flags, quality-gate pipelines.
- deprecation-and-migration Code-as-liability mindset, compulsory vs advisory deprecation, zombie-code removal.
- documentation-and-adrs Architecture Decision Records, API docs, inline standards - document the why.
- observability-and-instrumentation Structured logging, RED metrics, OpenTelemetry tracing, symptom-based alerting.
- shipping-and-launch Pre-launch checklists, feature-flag lifecycle, staged rollouts, rollback procedures.