Scan New Specs

Automates the gap between product specs landing and docs getting written. Scans warpdotdev/warp and warp-server every few days for merged PRODUCT.md files that don't have a corresponding docs PR yet. If the spec has enough detail (behavior section, concrete user actions, 40+ lines), it kicks off write-feature-docs in ambient mode and opens a draft PR with review requests. If the spec is too thin, it pings the engineer in Slack to either flesh it out or hand it off to docs manually. Built to run as a scheduled Oz agent so docs coverage doesn't depend on someone remembering to file a ticket. Uses the Slack API for real user pings, not just name mentions.

skills.sh installs: 19.3K
GitHub stars: 684
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add warpdotdev/common-skills --skill scan-new-specs --agent claude-code

Installs into .claude/skills of the current project.

Files

scan-new-specs (deprecated)

Retired 2026-08-20. Do not invoke this skill and do not schedule it.

Its scheduled agent (0ITuF9vNJ1RiO00Szlm1fW) is paused and stays paused.

Why it was retired

The skill fired on spec merge, which happens before a feature ships. Two failures followed from that single design choice:

It drafted docs for unreleased and sometimes abandoned work. A merged spec is not a shipped feature. The agent had no evidence of what users had actually received, so pages were written for behavior that had not landed, or had landed differently, or never landed at all.
It treated every spec as a docs task. Nothing asked whether a change warranted documentation. Pure UI changes, small intuitive additions, and behind-the-scenes work all became draft PRs, and the docs repo accumulated unvetted content debt faster than anyone could review it.