Creates feature specifications capturing requirements and acceptance criteria. Use when writing specs, documenting features, or defining requirements.
/plugin marketplace add jkappers/claude-code-software-delivery-plugin/plugin install jkappers-software-delivery-pack-claude@jkappers/claude-code-software-delivery-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create specifications capturing WHAT and WHY. Do not include implementation details (those belong in technical-details.md).
Feature Overview (2-3 paragraphs) - What it does, who uses it, what problem it solves
Success Criteria - Measurable outcomes defining "done"
Design Goals - Primary (must achieve) and secondary (nice to have)
User Experience (1-2 paragraphs) - How users interact, expected journey
Design Rationale (1-2 paragraphs) - Why this approach, key trade-offs
Constraints and Assumptions - Technical constraints, business assumptions
Functional Requirements (FR-N format) - Max 6-8 per spec, each specific and testable, with Given-When-Then acceptance criteria
Edge Cases and Error Handling - Unusual inputs, failure scenarios, expected behaviors
- [ ] Given [context], when [action], then [expected result]
Include 2-4 criteria per requirement covering happy path and key failure cases.
Do not include: architecture diagrams, code examples, database schemas, API signatures, development estimates, timeline references, or phase sections.
Before completing:
If more than 6-8 requirements, the feature is too large. Identify 3-4 core requirements and flag the rest for a separate spec. Document in a "Scope Notes" section.
specs/
├── YYYY-MM-DD-feature-name/
│ ├── README.md # Spec (WHAT and WHY)
│ └── technical-details.md # Implementation (HOW)
└── historical/
templates/spec-readme.md - New spec templatereferences/spec-guide.md - Guidelines and examplesCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.