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 missing_docs skill in warpdotdev/docs. If you were about to run this skill to find docs gaps, run missing_docs in drift-watch mode instead.
75
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Retired 2026-08-20. Do not invoke this skill and do not schedule it.
Its scheduled agent (0ITuF9vNJ1RiO00Szlm1fW) is paused and stays paused.
The skill fired on spec merge, which happens before a feature ships. Two failures followed from that single design choice:
The missing_docs skill in warpdotdev/docs, running in drift-watch mode. It differs in the two ways that matter:
scripts/check_new_release.py gates 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..agents/references/docs-worthiness-criteria.md before anything is drafted, with a default of no docs and a requirement to name concrete evidence. Verdicts, including rejections, are recorded in references/changelog_decisions.md so nothing is re-litigated.Anything genuinely worth documenting re-surfaces there once it ships.
missing_docs in drift-watch mode from the warpdotdev/docs repo.write-feature-docs directly and interactively. It still works, and it still walks you through spec research and outline confirmation. It no longer runs headlessly.missing_docs, not this. Scheduling this skill reintroduces exactly the flooding it was retired for.missing_docs (in warpdotdev/docs) — the release-triggered, worthiness-gated replacementwrite-feature-docs — still supported for direct, interactive use by an engineer69b4753
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.