Scan New Specs logo

Scan New Specs

Organization
warpdotdev
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 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.

Overview

Publisherwarpdotdev
Repositorycommon-skills
Skill namescan-new-specs
Stars
597
Forks
33
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by warpdotdev on GitHub. Read the source before you install it.

Installation

Install the Scan New Specs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/warpdotdev/common-skills/tree/main/.agents/skills/scan-new-specs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/warpdotdev/common-skills.git /tmp/common-skills
mkdir -p .claude/skills
cp -r /tmp/common-skills/.agents/skills/scan-new-specs .claude/skills/scan-new-specs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scan New Specs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scan New Specs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scan New Specs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.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.
  • Gated on worthiness. Every candidate is evaluated against .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.

If you were about to run this

  • Looking for docs gaps? Run missing_docs in drift-watch mode from the warpdotdev/docs repo.
  • You are an engineer who wants docs for your feature? Invoke 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.
  • 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 (in warpdotdev/docs) — the release-triggered, worthiness-gated replacement
  • write-feature-docs — still supported for direct, interactive use by an engineer

Frequently asked questions

What does the Scan New Specs AI 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 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.

Why use Scan New Specs on TypingMind?

Because you install it once and use it with any model. Scan New Specs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scan New Specs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/warpdotdev/common-skills/tree/main/.agents/skills/scan-new-specs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Scan New Specs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scan New Specs?

As many as you like. As long as a model supports skills, you can use Scan New Specs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scan New Specs AI skill free?

Yes. It is published on GitHub by warpdotdev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇