write-tech-spec

Draft TECH.md specifications for cross-module Warp features with testing strategies.

Updated Apr 28, 2026

Search Tags:#planning #architecture #engineering #docs #software-design #tech-spec #warp

Ready to run

npx skills add https://github.com/89jobrien/warpx --skill write-tech-spec

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate product intent and implementation constraints into a concise, executable TECH.md specification for Warp features, enabling clear engineering guidance and review.

Core Features & Use Cases

Context-driven: Captures relevant problem space, current codebase constraints, and risk factors.
Proposed changes: Outlines modules, APIs, data flow, and ownership boundaries.
Validation plan: Defines tests, verification steps, and acceptance criteria aligned with the product spec.

Quick Start

Provide a structured TECH.md draft for a Warp feature, using the product spec and code review findings to populate specs/<id>/TECH.md.

Frequently Asked Questions about write-tech-spec

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

FAQPage Schema

How do I draft a tech spec for cross-module software architecture?▼

To draft a tech spec for cross-module software architecture, research the relevant codebase to document architectural decisions, data flows, and ownership boundaries into a concise, executable specification.

What should be included in a TECH.md validation plan?▼

A TECH.md validation plan should include defined tests, verification steps, and acceptance criteria that are strictly aligned with product-facing expectations and the software design constraints.

How do I translate product intent into engineering docs?▼

Translate product intent into engineering docs by capturing the problem space, current codebase constraints, and risk factors, then outlining proposed modules and APIs to provide clear engineering guidance.

When do I need a tech spec for cross-module features?▼

You need a tech spec for cross-module features when a change spans multiple components, requiring explicit documentation of architectural decisions, data flows, and testing strategies to ensure alignment.

What is the best way to document software design for engineering review?▼

The best way to document software design for review is to structure specifications with Context, Proposed changes, and Testing and validation sections, translating implementation constraints into executable guidance.