skills.rest
lucasocosta
lucasocostaCOMMUNITY
Explore all skills by this author →
GitHub

cy-create-techspec

Creates technical specifications from PRDs through interactive clarification and ADR documentation.

Updated May 19, 2026
Search Tags:#documentation#adr#codebase analysis#architecture design#technical specification#prd#techspec
One-click install
npx skills add https://github.com/lucasocosta/reeve --skill cy-create-techspec-lucasocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-create-techspec
Source: https://github.com/lucasocosta/reeve/tree/main/skills/cy-create-techspec
Command: npx skills add https://github.com/lucasocosta/reeve --skill cy-create-techspec-lucasocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Translating a PRD into an actionable technical design often skips architecture review and decision documentation, causing integration failures. This Skill guides an interactive process that turns business requirements into a reviewed, codebase-informed technical specification. ## Core Features & Use Cases - Interactive Technical Clarification: Asks targeted one-at-a-time questions on architecture, data models, APIs, and testing before drafting. - ADR Generation: Records significant technical decisions as numbered Architecture Decision Records in the task's adrs/ directory. - Template-Based TechSpec: Produces a canonical _techspec.md with architecture, core interfaces, build order, and an ADR summary section. - Use Case: After approving a PRD for a new feature, run this Skill to explore the existing codebase, decide the technical approach with the user, and produce a TechSpec ready for task breakdown. ## Quick Start Create a technical specification for the feature described in the PRD at .compozy/tasks/my-feature/_prd.md.

Frequently Asked Questions about cy-create-techspec

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

FAQPage Schema
How do I create a technical specification from a PRD?▼

Provide the feature name and PRD file, then answer targeted questions about architecture, data models, APIs, and testing. The Skill explores the codebase, drafts a TechSpec from a canonical template, and saves it after your approval.

What is an Architecture Decision Record and when should I create one?▼

An ADR documents a significant technical decision, its rejected alternatives, and trade-offs. This Skill creates numbered ADRs for choices like architecture patterns, technologies, and data model approaches during TechSpec creation.

Can I update an existing TechSpec instead of creating a new one?▼

Yes. If a _techspec.md already exists in the task directory, the Skill operates in update mode, preserving sections you have not asked to change while revising the rest.

What happens if no PRD exists for my feature?▼

The Skill proceeds using a description you provide and notes the missing PRD in the Executive Summary. However, it works best when a PRD exists, since every PRD goal should map to a technical component.

When should I not use this TechSpec creation workflow?▼

Do not use it for PRD creation, task breakdown, or direct code implementation. It only covers the technical design phase; task breakdown is handled by the follow-up cy-create-tasks step.

Related Skills

Explore More Software Engineering Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
RefractSystemsRefractSystems

planning-and-task-breakdown

Break down specifications into ordered tasks with acceptance criteria and dependencies.

Official
Intermediate
paxlabs-incpaxlabs-inc
7

technical-architecture-proposal

Generate technical architecture proposals from codebase analysis and seam-finding.

Community
Advanced
claushaasclaushaas

docs-adr

Capture architecture decisions and ADRs with context, decision, and consequences.

Community
Basic