1. Habit
  2. Skills
  3. Write Tech Spec skill
warpdotdev · 29K installs

Write Tech Spec skill
Runs by itself, product spec approved.

Plans grounded in the real code.

Install the Write Tech Spec skill and make it a habit: follow https://gethabit.dev/skills/warpdotdev/write-tech-spec.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

29K installs628 starsMIT licenceSource on GitHub ↗

Write Tech Spec

by warpdotdev · 29K installs

The skill

The write tech spec skill writes TECH.md for a significant feature after researching the codebase: context with commit-pinned references, proposed changes, testing mapped to product behavior and a parallel plan.

Only when you ask.

The habit

Plans grounded in the real code.

↻ Runs by itselfproduct spec approved

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

product spec approved. Runs in Claude Code routine or GitHub Actions.

  • ↻ product spec approved
  • specs/<id>/PRODUCT.md merged or approved

02

It checks its work

required sections present. If a check fails, it tells you.

  • ✓specs/<id>/TECH.md exists next to PRODUCT.md
  • ✓Context, Proposed changes and Testing and validation sections are present
  • ✓code references carry a commit SHA
  • ✓each key Behavior invariant maps to a test or check

03

It remembers

tech spec. The next run reads it first: PRODUCT.md, the current TECH.md and DECISIONS.md if present.

specs/<id>/TECH.md

One run, step by step.
Then it stops.

Stop ruleOne TECH.md per run, one fix retry on missing sections.

  1. 01

    Read the product spec

    The agent reads PRODUCT.md and uses the same id for the directory.

  2. 02

    Research the code

    It inspects the relevant files, types and data flow, and captures the commit with git rev-parse HEAD.

  3. 03

    Write context

    It describes the current system with commit-pinned file links.

  4. 04

    Propose changes

    It lists module changes, new types and tradeoffs that fit existing patterns.

  5. 05

    Plan testing

    It maps numbered Behavior items from PRODUCT.md to concrete tests and checks.

  6. 06

    Parallelization

    If run_agents exists, it proposes sub-agents with worktrees and branches, or says why not.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Write Tech Spec skill helps.

Use it when

  • ✓ A feature spans several modules
  • ✓ Reviewers need the plan before the code
  • ✓ A PRODUCT.md is already agreed

Skip it when

  • – The change is a single obvious fix
  • – The approach is too uncertain to plan yet

Questions

Write Tech Spec skill, answered.

Does every change need a tech spec?

No. Pure UI changes and straightforward fixes often skip it.

What if the approach is still unclear?

Build an end-to-end prototype first, then write the tech spec from what you learned.

How do I install the Write Tech Spec skill?

Copy the prompt at the top into your agent. It installs the skill from warpdotdev/common-skills and sets up the habit. Or run npx skills add warpdotdev/common-skills --skill write-tech-spec.

Is the Write Tech Spec skill free?

Yes. It is published under MIT. Habit is free too.

Write Tech Spec. Now as a habit.

Install the Write Tech Spec skill and make it a habit: follow https://gethabit.dev/skills/warpdotdev/write-tech-spec.md

  • Free
  • No account
  • Undo in one line

All warpdotdev skills →More planning skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by warpdotdev, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.