write-feature-docs

Agent skill from warpdotdev/common-skills.

warpdotdev 146 ↓ 5.7k MIT updated 27d ago

Claude Code

View source ↗

What it does

A Linear ticket number: APP-1234, REMOTE-1234, QUALITY-408
A GitHub issue (prefixed with gh-): gh-4567
A short kebab-case feature name: vertical-tabs-hover-sidecar
specs/<id>/PRODUCT.md — primary source: user-facing behavior, what and why
specs/<id>/TECH.md — secondary source: implementation, data model
UI strings: search for user-visible button labels, menu item names, or setting names referenced in the spec
Settings paths: confirm exact Settings menu paths (e.g., Settings > AI > Knowledge)

Requirements & configuration

2. Research the codebase to verify technical claims — minimize what the engineer needs to check
Generate a concise outline — no prose. The outline shows what you've confirmed from research and exactly what still needs engineer input.
NEEDS YOUR CONFIRMATION ⚠️
[e.g., "Step 3 — does the sync trigger automatically or require a manual action?"]
[Optional: key context the reader needs upfront — a prerequisite, a limitation,

Configuration: REMOTEQUALITYPRODUCTTECHFEATURE_TOKENSPEC_IDEMAIL

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

Source

Repository: https://github.com/warpdotdev/common-skills

write-feature-docs FAQ

What does the write-feature-docs skill do?

Draft a complete documentation page for a new Warp feature from its PRODUCT.md and/or TECH.md spec. Use when an engineer has written a spec and needs to produce a first-pass MDX draft for the warpdotdev/docs repo. Also handles features without specs by researching the codebase first. Invoke this skill whenever an engineer mentions writing docs for a feature, drafting a docs page, creating feature documentation, starting the eng-docs workflow, or converting a spec into documentation. Works from warp-internal or warp-server. A Linear ticket number: APP-1234, REMOTE-1234, QUALITY-408 A GitHub issue (prefixed with gh-): gh-4567

What does write-feature-docs require?

2. Research the codebase to verify technical claims — minimize what the engineer needs to check Generate a concise outline — no prose. The outline shows what you've confirmed from research and exactly what still needs engineer input. NEEDS YOUR CONFIRMATION ⚠️ [e.g., "Step 3 — does the sync trigger automatically or require a manual action?"] [Optional: key context the reader needs upfront — a prerequisite, a limitation, Configuration keys: REMOTE, QUALITY, PRODUCT, TECH, FEATURE_TOKEN, SPEC_ID, EMAIL.

How do I install write-feature-docs?

Run: npx -y skills add https://github.com/warpdotdev/common-skills --skill write-feature-docs --agent claude-code — the source lives at github.com/warpdotdev/common-skills.

Maintain write-feature-docs?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![write-feature-docs on getagentictools](https://getagentictools.com/badge/skills/warpdotdev-common-skills-write-feature-docs.svg)](https://getagentictools.com/skills/warpdotdev-common-skills-write-feature-docs?ref=badge)

npx agentictools info skills/warpdotdev-common-skills-write-feature-docs

The second line is the CLI lookup for this page — handy in READMEs and docs.