gen-techspec

Consolidate modernization analysis into a cross-referenced technical specification document.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill gen-techspec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-techspec
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/techspec-writer
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill gen-techspec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This TECHNICAL SPEC WRITER converts scattered modernization inputs (analysis, funcspec, and source extracts) into a single, comprehensive technical specification that guides modernization efforts. It reorganizes details by technical concerns (APIs, data model, SQL, security, etc.), cross-references functional requirements, and produces a complete techspec document for developers.

Core Features & Use Cases

  • Consolidates API contracts, data models, SQL logic, error handling, concurrency, messaging contracts, security implementation, performance characteristics, configuration, and infrastructure dependencies into a unified techspec.
  • Cross-references functional requirements (FRs) and behavioral inventory to ensure traceability and alignment with business goals.
  • Outputs modernization-output/{slug}/techspec.md with sectioned content, architecture diagrams, and step-by-step flows to guide implementation.

Quick Start

Trigger the generation with /gen-techspec <slug> to produce a complete techspec for the modernization project.

Frequently Asked Questions about gen-techspec

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

FAQPage Schema
How do I generate a technical specification for legacy modernization?

To generate a technical specification for legacy modernization, use the /gen-techspec command with a project slug. The tool consolidates scattered analysis, functional specs, and source extracts into a unified techspec.md document with 13 structured sections.

How do I consolidate API contracts and data models into a single document?

Consolidating API contracts and data models is achieved by processing analysis.md, funcspec.md, and source-extracts.md inputs. The tool reorganizes these scattered details by technical concerns, cross-referencing functional requirements to produce a single authoritative engineering blueprint.

What is a living techspec and when do I need one for modernization?

A living techspec is a comprehensive technical specification that guides modernization efforts by cross-referencing functional requirements and behavioral inventory. You need one when consolidating scattered legacy analysis into a single, authoritative engineering blueprint for developers.

Can I use this techspec generator for SQL logic and security implementation documentation?

Yes, the techspec generator handles SQL logic and security implementation documentation. It consolidates API contracts, data models, error handling, concurrency, messaging contracts, and infrastructure dependencies into a unified technical specification.

What's the best way to ensure traceability between functional requirements and technical specs?

The best way to ensure traceability is using a techspec generator that cross-references functional requirements and behavioral inventory. It maps technical concerns like APIs and data models directly to business goals within the generated specification document.

Do I need separate analysis files before generating a comprehensive techspec?

Yes, you need analysis.md, funcspec.md, and source-extracts.md files prepared before generation. The tool parses these scattered modernization inputs to produce a cross-referenced engineering blueprint output at modernization-output/{slug}/techspec.md.