skills.rest
MatheusBBarni
MatheusBBarniCOMMUNITY
Explore all skills by this author →
Website𝕏@matheusBBarniGitHub

cy-create-techspec

Convert PRD requirements into a technical specification with ADRs.

1|Updated May 3, 2026
Search Tags:#design#architecture#documentation#review#prd#adrs#techspec
One-click install
npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-create-techspec-matheusbbarni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-create-techspec
Source: https://github.com/MatheusBBarni/symphony-orchestrator/tree/main/.agents/skills/cy-create-techspec
Command: npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-create-techspec-matheusbbarni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts PRD requirements into actionable technical design through guided clarification, ensuring architecture decisions are captured before implementation. Use when a PRD exists and a technical plan is required, or when architectural decisions need documenting. Do not use for PRD creation, task breakdown, or direct code implementation.

Core Features & Use Cases

  • Interactive requirement clarification that informs TechSpec drafting
  • ADR creation to record architectural decisions
  • Drafting the TechSpec using the canonical template from references/techspec-template.md
  • Review and iteration with the user until approved
  • Save the final _techspec.md under .compozy/tasks/<name>/

Quick Start

Initiate a TechSpec session by providing the PRD or describing the technical goals.

Frequently Asked Questions about cy-create-techspec

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

FAQPage Schema
How do I convert a PRD into a technical specification?▼

To convert a PRD into a technical specification, the Skill gathers context, asks technical questions, generates ADRs, drafts a canonical TechSpec, and saves the approved result to a designated _techspec.md path.

What is the best way to document architecture decisions before implementation?▼

Documenting architecture decisions is handled by creating Architecture Decision Records (ADRs) during the TechSpec drafting process, ensuring design choices are captured and reviewed before moving into implementation.

How does architecture exploration work when planning technical design from business requirements?▼

Architecture exploration works by interactively clarifying business requirements from a PRD, resolving technical questions, and translating those answers into a concrete technical design documented within the TechSpec.

Can I use this to create a PRD or break down implementation tasks?▼

You cannot use this for PRD creation, task breakdown, or direct code implementation, as it is strictly designed to convert existing PRD requirements into an actionable technical design and ADRs.

Do I need an existing PRD to start drafting a TechSpec?▼

Yes, you need an existing PRD or a description of technical goals to initiate a TechSpec session, which then guides requirement clarification and generates the technical specification.

Where are the generated technical specifications and ADRs saved?▼

Generated technical specifications are saved as a final _techspec.md file under the designated .compozy/tasks/<name>/ directory path after user review and iteration are completed.

Related Skills

Explore More Software Engineering Skills→
elihuvillarauselihuvillaraus
2

architect

Audit a codebase for architectural issues and generate a Product Requirement Document.

Community
Advanced
rhuangabrielsantosrhuangabrielsantos

cy-execute-task

Execute PRD tasks end-to-end from specification to tracking updates.

Community
Advanced
ViniciuscarvalhoViniciuscarvalho
11

techspec-validator

Validate PRD-to-TechSpec coverage and generate a techspec-validation.md report.

Community
Advanced
Razmik-KutinavaRazmik-Kutinava

technical-spec-document

Generates technical specification documents for software development projects.

Community
Intermediate