write-tech-spec

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

Updated Apr 30, 2026

Search Tags:#planning #architecture #documentation #specification #tech-spec #warp

Ready to run

npx skills add https://github.com/lalaABC/waprcn --skill write-tech-spec-lalaabc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts detailed technical specifications that translate product intent into concrete implementation plans, ensuring alignment with the existing Warp codebase.

Core Features & Use Cases

Contextual research: reviews the current codebase and constraints before drafting.
Structured TECH.md output: provides sections like Context, Proposed Changes, Testing, and Validation.
Alignment: ties the tech spec to a product spec and code ownership.

Quick Start

Provide the product intent and codebase context to generate a TECH.md spec for a Warp feature.

Frequently Asked Questions about write-tech-spec

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

FAQPage Schema

How do I generate a technical specification from product intent for a Warp feature?▼

To generate a technical specification, you provide the product intent and codebase context to draft a structured TECH.md document. This document aligns proposed changes with existing Warp architecture patterns and implementation constraints for PR review.

What sections should be included in a TECH.md specification for software engineering?▼

A TECH.md specification should include sections like Context, Proposed Changes, Testing, and Validation. Structuring the technical specification with these specific sections ensures the implementation plan is clear, reviewable, and tied to code ownership.

How to align a tech spec with existing architecture patterns and codebase constraints?▼

You align a tech spec by researching the current codebase and identifying implementation constraints before drafting. The generated specification ties the proposed changes directly to existing architecture patterns and the original product intent.

Do I need to provide codebase context to draft a technical specification?▼

Yes, you need to provide codebase context to draft an accurate technical specification. Supplying the current codebase context and product intent allows the tool to review implementation constraints and generate a properly aligned TECH.md document.

What is the best way to turn product intent into a concrete implementation plan?▼

The best way to turn product intent into a concrete implementation plan is to generate a TECH.md specification. By researching the existing codebase first, the drafted specification translates intent into a clear, reviewable document ready for PR review.