cy-create-techspec

Generate a _techspec.md file from a Product Requirements Document with interactive clarification.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-techspec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-create-techspec
Source: https://github.com/rhuangabrielsantos/skills/tree/main/skills/cy-create-techspec
Command: npx skills add https://github.com/rhuangabrielsantos/skills --skill cy-create-techspec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the creation of a detailed Technical Specification (TechSpec) from an existing Product Requirements Document (PRD), ensuring comprehensive architectural design, data modeling, and API definition through interactive clarification with the user.

Core Features & Use Cases

  • End-to-end TechSpec workflow: Gathers context, asks targeted technical questions, records Architecture Decision Records, and drafts a complete TechSpec following the canonical template.
  • Interactive clarification: Utilizes one‑question‑at‑a‑time prompts to capture missing architectural details before writing the document.
  • Update mode: Can revise an existing _techspec.md while preserving unchanged sections.
  • Use Case Example: When a new feature’s PRD is ready but the engineering team needs a concrete design document before implementation, invoke this skill to produce a ready‑to‑implement TechSpec.

Quick Start

Create a TechSpec for the feature user-profile using its PRD.

Frequently Asked Questions about cy-create-techspec

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

FAQPage Schema
How do I generate a technical specification from a PRD?

To generate a technical specification from a PRD, you need a guided workflow that asks targeted architectural questions and outputs a structured _techspec.md file. This process captures missing details interactively before drafting the document.

What is an Architecture Decision Record and when do I need it for feature design?

An Architecture Decision Record (ADR) documents significant technical choices made during software design. You need it when creating a TechSpec from a PRD to ensure architectural decisions, data models, and API definitions are explicitly recorded for engineering teams.

Can I update an existing techspec document without losing previous sections?

Yes, you can update an existing _techspec.md file using a dedicated update mode. This mode revises the technical specification by applying new PRD details while preserving unchanged sections and previously recorded architectural decisions.

How do interactive guided questions improve technical specification creation?

Interactive guided questions improve technical specification creation by capturing missing architectural details one question at a time before drafting. This ensures the final _techspec.md comprehensively defines data models, APIs, and architectural design.

What should I include in a technical specification for a new software feature?

A technical specification should include architectural design, data models, API definitions, and Architecture Decision Records. When generated from a PRD, it must adhere to a canonical template to provide a ready-to-implement document for the engineering team.

Does this technical specification workflow require any external dependencies?

No, this technical specification workflow does not require any external dependencies. It operates independently to collect interactive clarifications, generate Architecture Decision Records, and output the final _techspec.md file.