cy-create-techspec

Generates a complete draft of TechSpec and companion documents from your uploaded files.

2.5k|134|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill cy-create-techspec-compozy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-create-techspec
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/cy-create-techspec
Command: npx skills add https://github.com/compozy/compozy --skill cy-create-techspec-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates PRDs and architectural input into a formal Technical Specification, ensuring decisions are captured and traceable.

Core Features & Use Cases

  • Gather context from PRDs, ADRs, and codebase exploration to ground the TechSpec in real project context.
  • Generate ADRs documenting significant technical decisions (architecture pattern, technology choices, data model approach) and link them from the TechSpec.
  • Produce a canonical TechSpec draft aligned to the project template, including Architecture, Data Models, API Design, Testing approach, and Development Sequencing.

Quick Start

Provide a PRD and any architectural input to generate a complete TechSpec draft for review.

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?

Generating ADRs from codebase analysis involves exploring existing code and architectural input to document significant technical decisions like architecture patterns and technology choices, linking them directly from the TechSpec for traceability.

What is the best way to document architecture decisions for a new feature?

Documenting architecture decisions for a new feature is best handled by generating Architecture Decision Records (ADRs) that capture technology choices and data model approaches, maintaining a complete and structured ADR log linked to the TechSpec.

Can I generate a tech spec without an existing PRD?

A canonical TechSpec draft includes structured sections for Architecture, Data Models, API Design, Testing approach, and Development Sequencing, ensuring all technical planning aspects are covered and traceable to ADRs.

How do I maintain traceability between technical decisions and project requirements?

To maintain traceability between technical decisions and project requirements, the Skill links generated ADRs from the canonical TechSpec draft back to the original PRD context, preserving a complete architecture decision log.