create-specification

Convert PRD requirements into technical specifications with categorized acceptance criteria.

Updated Aug 23, 2026

Search Tags:#documentation #specification #requirements #technical design #framework #prd

Ready to run

npx skills add https://github.com/msageha/maestro_v2 --skill create-specification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/msageha/maestro_v2/tree/main/templates/skills/planner/create-specification
Command: npx skills add https://github.com/msageha/maestro_v2 --skill create-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms high-level Product Requirements Documents (PRDs) or user stories into detailed technical specifications that developers can directly implement.

Core Features & Use Cases

Requirement Categorization: Organizes requirements into functional, security, constraints, guidelines, and patterns using clear prefixes (REQ, SEC, CON, GUD, PAT).
Acceptance Criteria Formatting: Enforces the Given-When-Then (GWT) format for clear, testable acceptance criteria.
Template Generation: Provides a structured template for the technical specification, covering overview, requirements, design, and testing.
Maestro Task Mapping: Clearly maps specification elements to Maestro task fields like content, acceptance_criteria, and constraints.
Use Case: After a PRD is finalized, use this skill to generate a detailed technical specification document that outlines the implementation details, including specific requirements, security considerations, and design patterns, ensuring all stakeholders have a clear understanding before development begins.

Quick Start

Use the create-specification skill to convert the PRD requirements in the attached document into a technical specification.

Frequently Asked Questions about create-specification

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

FAQPage Schema

How do I convert a PRD into a technical specification for software development?▼

To convert a PRD into a technical specification, you map high-level requirements into detailed, actionable tasks using structured prefixes like REQ, SEC, CON, GUD, and PAT. This process ensures functional, security, and design guidelines are clearly defined for implementation.

What is the Given-When-Then format for technical specifications?▼

The Given-When-Then format structures acceptance criteria into testable statements. Given a specific context, When an action occurs, Then a specific outcome results. Enforcing this format ensures technical specifications have clear, verifiable conditions for development.

How do I categorize requirements in a technical design document?▼

You categorize requirements in a technical design document by applying defined prefixes: REQ for functional requirements, SEC for security, CON for constraints, GUD for guidelines, and PAT for patterns. This systematically organizes specifications for stakeholders.

Can I map technical specification elements directly to Maestro task fields?▼

Yes, you can map technical specification elements directly to Maestro task fields. The specification generation process explicitly aligns requirement categories and acceptance criteria with Maestro fields like content, acceptance_criteria, and constraints.

What is the best way to structure acceptance criteria for implementable tasks?▼

The best way to structure acceptance criteria for implementable tasks is using the Given-When-Then format. This enforces clear, testable conditions within the technical specification template, covering overview, requirements, design, and testing sections.