spec

Generate technical specifications and acceptance criteria from product requirements documents.

42|5|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kazdenc/builder-skills --skill spec-kazdenc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/kazdenc/builder-skills/tree/main/.claude/skills/product/define/spec
Command: npx skills add https://github.com/kazdenc/builder-skills --skill spec-kazdenc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between product requirements (like PRDs or user stories) and engineering implementation by generating clear, structured technical specifications.

Core Features & Use Cases

  • Generate Tech Specs: Creates detailed technical specifications for features or systems.
  • Define Acceptance Criteria: Helps in writing precise acceptance criteria for engineering tasks.
  • Use Case: After a product manager writes user stories for a new feature, they can use this Skill to generate a technical specification that engineers can use to plan and build the feature.

Quick Start

Use the spec skill to write a technical specification for the new user authentication system.

Frequently Asked Questions about spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate technical specifications from product requirements documents?

To generate technical specifications from product requirements documents, you input your PRDs or user stories. The system translates these high-level product needs into detailed engineering plans covering technical approach, data models, API design, edge cases, and testing.

What is the best way to write acceptance criteria for engineering tasks?

The best way to write acceptance criteria for engineering tasks is to process your user stories through this specification generation tool. It facilitates translating product needs into precise, actionable criteria and detailed technical plans for engineers.

Can I use user stories to plan API design and data models for a new feature?

Yes, you can use user stories to plan API design and data models. The system processes user stories to generate structured technical specifications that explicitly cover technical approaches, data models, API design, and rollout strategies.

How do I define edge cases and testing strategies when translating product requirements?

To define edge cases and testing strategies when translating product requirements, the system automatically extracts these details from the input PRDs. It structures the engineering plans to include specific edge cases and comprehensive testing strategies.

Does generating a technical specification help with rollout strategies for engineering teams?

Yes, generating a technical specification helps with rollout strategies for engineering teams. The output engineering plans specifically include rollout strategies alongside technical approaches and API designs to guide implementation.