specgen-ts-cli

Generate TypeScript CLI specification blueprints from PRD and MODEL inputs.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill specgen-ts-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specgen-ts-cli
Source: https://github.com/rashidee/co2-skills/tree/main/skills/specgen-ts-cli
Command: npx skills add https://github.com/rashidee/co2-skills --skill specgen-ts-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates comprehensive, implementation-ready specification documents for TypeScript CLI tools from PRD and MODEL inputs, reducing manual drafting time and ensuring consistency.

Core Features & Use Cases

  • Produces a root SPECIFICATION.md and per-command SPEC.md files from PRD.md and MODEL.md
  • Enforces versioning and a consistent dependency-to-component mapping for CLI tooling
  • Supports an automated, template-driven workflow that aligns with the repository's references guidelines
  • Generates a machine-readable outline for consumption by automation tools and AI agents

Quick Start

Provide your CLI name and version to generate a full specification blueprint.

Frequently Asked Questions about specgen-ts-cli

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

FAQPage Schema
How do I generate a specification document for a TypeScript CLI tool?

You generate a TypeScript CLI specification by providing PRD and MODEL inputs to produce a root SPECIFICATION.md and per-command SPEC.md files, ensuring structured architecture and packaging guidance.

How do I structure a new CLI project architecture from a PRD?

Structuring a CLI project from a PRD involves mapping product requirements to a consistent TypeScript project structure, enforcing dependency-to-component mapping, and defining command-level specifications.

What is the best way to automate developer utility documentation for TypeScript?

Automating TypeScript documentation uses a template-driven workflow to generate machine-readable outlines and specification blueprints, reducing manual drafting time and ensuring consistency for automation tools.

Do I need a MODEL.md file to generate CLI specifications?

Yes, a MODEL.md file is required alongside PRD.md inputs to map data structures and dependencies to specific SPEC files, enabling accurate versioning and optional component generation.

Can I use generated CLI specs with AI agents for automated implementation?

Yes, the generated specification blueprint produces a machine-readable outline specifically designed for consumption by automation tools and AI agents to guide structured implementation.

Why does my CLI specification blueprint include optional components?

Optional components are included in the CLI specification blueprint based on project dependencies, enforcing a strict dependency-to-component mapping to ensure the architecture scales accurately with required tooling.