scan-new-specs
DEPRECATED and retired as of 2026-08-20. Do not invoke, and do not schedule. This skill scanned for merged PRODUCT.md specs and auto-drafted docs PRs, which produced documentation for features that had not shipped. Docs for newly shipped features are now triggered by the weekly release and gated on documentation-worthiness by the missingdocs skill in warpdotdev/docs. If you were about to run this skill to find docs gaps, run missingdocs in drift-watch mode instead.
- Installs
- 19.1K
- Last 24h
- +26
- Trending rank
- #4782
- Security
- Warn
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/warpdotdev/common-skills --skill scan-new-specs- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads scan-new-specs automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
What replaces it
The missing_docs skill in warpdotdev/docs, running in drift-watch mode. It differs in the two ways that matter:
- Release-triggered.
scripts/check_new_release.pygates each run on a new stable release, so the pipeline sees what actually shipped rather than what was planned. A daily schedule does per-release work. - Gated on worthiness. Every candidate is evaluated against
.agents/references/docs-worthiness-criteria.mdbefore anything is drafted, with a default of no docs and a requirement to name concrete evidence. Verdicts, including rejections, are recorded inreferences/changelog_decisions.mdso nothing is re-litigated.
Anything genuinely worth documenting re-surfaces there once it ships.
If you were about to run this
- Looking for docs gaps? Run
missing_docsin drift-watch mode from thewarpdotdev/docsrepo. - You are an engineer who wants docs for your feature? Invoke
write-feature-docsdirectly and interactively. It still works, and it still walks you through spec research and outline confirmation. It no longer runs headlessly. - Setting up a scheduled docs agent? Use
missing_docs, not this. Scheduling this skill reintroduces exactly the flooding it was retired for.
Related skills
missing_docs(inwarpdotdev/docs) — the release-triggered, worthiness-gated replacementwrite-feature-docs— still supported for direct, interactive use by an engineer
FAQ
What does the scan-new-specs skill do?
DEPRECATED and retired as of 2026-08-20. Do not invoke, and do not schedule. This skill scanned for merged PRODUCT.md specs and auto-drafted docs PRs, which produced documentation for features that had not shipped. Docs for newly shipped features are now triggered by the weekly release and gated on documentation-worthiness by the missingdocs skill in warpdotdev/docs. If you were about to run this skill to find docs gaps, run missingdocs in drift-watch mode instead.
How do I install scan-new-specs?
Run npx skills add https://github.com/warpdotdev/common-skills --skill scan-new-specs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/scan-new-specs/ (personal) or .claude/skills/scan-new-specs/ (project).
Which AI agents can use scan-new-specs?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is scan-new-specs safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk flagged items to review. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains scan-new-specs?
It is published by warpdotdev in warpdotdev/common-skills. It has 19,126 recorded installs.
More from warpdotdev/common-skills
review-pr
warpdotdev/common-skills
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like prdiff.txt and prdescription.txt and producing machine-readable review output instead of posting directly to GitHub.
spec-driven-implementation
warpdotdev/common-skills
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
write-product-spec
warpdotdev/common-skills
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
write-tech-spec
warpdotdev/common-skills
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
resolve-merge-conflicts
warpdotdev/common-skills
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when git status shows unmerged paths, or when files contain conflict markers.
fix-errors
warpdotdev/common-skills
Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown：查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件，或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.