write-tech-spec

Draft a TECH.md specification for a Warp feature from codebase research.

37|1|Updated Apr 28, 2026

Search Tags:#planning #architecture #documentation #codebase #spec-writing #tech-spec #warp

Ready to run

npx skills add https://github.com/terzigolu/warp-lite --skill write-tech-spec-terzigolu

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tech spec should translate product intent into an implementation plan that fits the existing codebase, documents architectural choices, and makes the work easier for agents to execute and reviewers to evaluate.

Core Features & Use Cases

Provides a structured template for cross-module architectural planning.
Guides reviewers with explicit context, changes, and validation criteria.
Example: When a Warp feature spans UI, core runtime, and networking, this spec outlines required APIs and milestones.

Quick Start

Draft a TECH.md spec for the chosen Warp feature based on current codebase research.

Frequently Asked Questions about write-tech-spec

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

FAQPage Schema

How do I write a tech spec for cross-module feature architecture?▼

To write a tech spec for cross-module architecture, draft a TECH.md file translating product intent into an implementation plan that documents API choices and fits the existing codebase. This structured template explicitly guides reviewers with required context, proposed changes, and validation criteria.

What should be included in a TECH.md specification for implementation planning?▼

A TECH.md specification for implementation planning must include Context, Proposed changes, and Testing and validation sections. It should reference the PRODUCT.md for behavior anchors and document architectural choices to make the work easier for agents to execute and reviewers to evaluate.

When do I need a formal tech spec for codebase development?▼

You need a formal tech spec for codebase development when a feature spans multiple modules like UI, core runtime, and networking. This cross-module architectural work requires detailed design and review to outline required APIs and milestones before implementation begins.

How do I translate product intent into a codebase implementation plan?▼

To translate product intent into a codebase implementation plan, draft a TECH.md spec based on current codebase research. It anchors product behavior to the PRODUCT.md and translates that intent into a structured plan fitting the existing architecture.

Does this tech spec template work for features spanning UI, core runtime, and networking?▼

Yes, this tech spec template works for features spanning UI, core runtime, and networking. It provides a structured template for cross-module architectural planning, outlining required APIs and milestones to guide reviewers evaluating the significant feature.

What is the best way to document architectural choices for agent execution?▼

The best way to document architectural choices for agent execution is to draft a TECH.md specification outlining required APIs, milestones, and validation criteria. This makes the implementation work easier for agents to execute and reviewers to evaluate.