build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Start spec-driven development — write a structured specification before writing code
> /plugin marketplace add addyosmani/agent-skills > /plugin install agent-skills@addy-agent-skills
How it fires
How this command gets triggered: by you, by Claude, or both.
/specContext preview
What this command does when you run it.
Start spec-driven development — write a structured specification before writing code
description: Start spec-driven development — write a structured specification before writing code
Invoke the agent-skills:spec-driven-development skill.
Begin by understanding what the user wants to build. Ask clarifying questions about: 1. The objective and target users 2. Core features and acceptance criteria 3. Tech stack preferences and constraints 4. Known boundaries (what to always do, ask first about, and never do)
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
If the request bundles several independently testable capabilities, first propose a capability map (module ids, dependency direction, build order) per the skill's Phase 0 and get it approved, then spec each module in dependency order.
Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
Production-grade engineering skills for AI coding agents. Skills encode the workflows, quality gates, and best practices that senior engineers use when building software.
Get the whole plugin, auto-invokedRepo: addyosmani/agent-skills
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Simplify code for clarity and maintainability — reduce complexity without changing behavior
Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md
Break work into small verifiable tasks with acceptance criteria and dependency ordering
Conduct a five-axis code review — correctness, readability, architecture, security, performance
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision