write-techspec

Convert a PRD into a structured TechSpec with milestones and GitHub issues.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ischung/go-sdlc-gan --skill write-techspec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-techspec
Source: https://github.com/ischung/go-sdlc-gan/tree/main/write-techspec-skill
Command: npx skills add https://github.com/ischung/go-sdlc-gan --skill write-techspec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the transformation of PRDs into a structured TechSpec and generates implementable issues, enabling faster and consistent handoffs to engineering teams.

Core Features & Use Cases

  • Analyze a PRD to produce a comprehensive TechSpec with sections like architecture, data models, API definitions, and milestones.
  • Automatically publish GitHub issues from the TechSpec via the /generate-issues command, organized into DAG levels (L0 walking skeleton and L2 vertical slices) and governed by deployment profiles.
  • Support both local (L) and web deployment (W) workflows to tailor scope and CI/CD coverage for different environments.

Quick Start

Provide the PRD path or paste PRD content after triggering /write-techspec, and the system will generate a TechSpec and prepare actionable issues.

Frequently Asked Questions about write-techspec

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

FAQPage Schema
How do I convert a PRD into a structured TechSpec for engineering handoff?

To convert a PRD into a structured TechSpec, provide the PRD content or file path to trigger the automated generation of architecture, data models, API definitions, and milestone sections for consistent engineering handoffs.

Can I automatically generate GitHub issues from a technical specification?

Yes, you can automatically generate and publish GitHub issues from a technical specification by using the /generate-issues command, which organizes implementation tasks into DAG levels like L0 walking skeletons and L2 vertical slices.

What is the best way to structure incremental planning for architecture decisions?

The best way to structure incremental planning for architecture decisions is to use a STEP-based flow that organizes implementation tasks into L0 walking skeletons and L2 vertical slices governed by specific deployment profiles.

Does this TechSpec generation workflow support both local and web deployment environments?

Yes, the TechSpec generation workflow supports both local (L) and web deployment (W) workflows, allowing you to tailor project scope and CI/CD coverage to match the specific requirements of different deployment environments.

Do I need frontmatter requirements in my PRD to generate a TechSpec?

Yes, frontmatter requirements are imposed during the TechSpec generation process to ensure the resulting technical specification and automatically generated issues meet the necessary structural standards for engineering implementation.

What sections are included when automating PRD analysis for engineering documentation?

Automating PRD analysis for engineering documentation produces a comprehensive TechSpec that includes sections for architecture decisions, data models, API definitions, and milestones to facilitate faster and consistent engineering team handoffs.