write-tech-spec
Write a
TECH.md
spec for a significant feature in Warp.
Overview
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.
Write specs to
specs//TECH.md
, where
is one of:
a Linear ticket number (e.g.
specs/APP-1234/TECH.md
)
a GitHub issue id, prefixed with
gh-
(e.g.
specs/gh-4567/TECH.md
)
a short kebab-case feature name (e.g.
specs/vertical-tabs-hover-sidecar/TECH.md
)
Match the id used by the sibling
PRODUCT.md
when one exists.
specs/
should contain only id-named directories as direct children.
Ticket / issue references are optional. If the user has a Linear ticket or GitHub issue, use its id. If they don't, ask them for a feature name to use as the directory. Only create a new Linear ticket or GitHub issue when the user explicitly asks for one; in that case use the Linear MCP tools or
gh
CLI respectively (and
ask_user_question
if team, labels, or repo are unclear).
When to use
Show more