tech-spec

Design typed call-stack architecture handoffs for TypeScript software changes.

345|9|Updated Jun 19, 2026

Search Tags:#typescript #design #testing #architecture #refactoring #call stack #technical spec

Ready to run

npx skills add https://github.com/dmmulroy/skills --skill tech-spec-dmmulroy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-spec
Source: https://github.com/dmmulroy/skills/tree/main/tech-spec
Command: npx skills add https://github.com/dmmulroy/skills --skill tech-spec-dmmulroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague change requests into precise, implementation-ready technical specifications for TypeScript systems, reducing ambiguity before coding begins.

Core Features & Use Cases

It analyzes current code, docs, and standards to identify goals, constraints, invariants, and open questions.
It compares multiple architectural alternatives and recommends a design based on typed contracts, seams, and call stacks.
It produces a practical RGR TDD plan and file-by-file implementation map for refactors, features, and architecture handoffs.

Quick Start

Use the tech-spec skill to turn the provided change request and relevant code context into an implementation-ready TypeScript architecture spec.

Frequently Asked Questions about tech-spec

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

FAQPage Schema

How do I write a technical spec for a TypeScript refactoring?▼

A technical spec for a TypeScript refactoring requires explicit contracts, seams, call stacks, alternatives, test plans, and open questions grounded in existing code and standards. It turns vague change requests into precise, implementation-ready typed architecture handoffs.

What is a typed call-stack architecture handoff?▼

A typed call-stack architecture handoff is a design specification that defines typed contracts and seams for software changes. It maps the execution flow and dependencies for new features or refactors to reduce ambiguity before coding begins.

How do I plan a Red Green Refactor TDD strategy for a new TypeScript feature?▼

Planning a Red Green Refactor TDD strategy for a new TypeScript feature involves analyzing current code and standards to produce a practical test plan. It requires identifying architectural alternatives and mapping file-by-file implementation steps grounded in existing constraints.

Does this technical spec design process work for reviewing existing architecture?▼

Yes, this technical spec design process works for reviewing existing architecture by comparing multiple architectural alternatives and recommending a design based on typed contracts and call stacks. It analyzes current code, docs, and standards to identify invariants and open questions.

What do I need to provide to generate an implementation-ready TypeScript architecture spec?▼

To generate an implementation-ready TypeScript architecture spec, you need to provide a change request and relevant code context. The system uses this input to identify goals, constraints, and open questions to produce a file-by-file implementation map.