scan-new-specs

Agent skill from warpdotdev/common-skills.

warpdotdev 146 ↓ 5.7k MIT updated 27d ago

Claude Code

View source ↗

What it does

If the spec is thin — ping the engineer directly to either flesh out the spec or kick off the docs workflow manually
File is at least 40 lines long
Contains a ## Behavior section (or equivalent) with numbered invariants or user-facing steps
Describes at least one concrete user action (not just a summary paragraph)
write-feature-docs — the skill engineers run to generate the docs draft after being nudged

Requirements & configuration

| SLACKBOTTOKEN | From buzz environment | Slack bot token for posting via API (already available in the buzz Oz environment) |
A spec is uncovered if neither query returns results. Closed-unmerged PRs do not count as coverage — a closed PR signals abandoned work that needs re-triggering.
Please check the items marked [UNVERIFIED] and [TODO] in the PR — those are the only things that need your input.
📋 New spec needs docs — not enough detail to auto-draft

Configuration: LOOKBACK_DAYSSLACK_CHANNELSLACK_BOT_TOKENENG_EMAILSLACK_USER_IDENG_MENTIONENG_NAMEENG_GITHUB

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

Source

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

scan-new-specs FAQ

What does the scan-new-specs skill do?

Scan warpdotdev/warp and warp-server for recently merged PRODUCT.md specs that don't yet have a corresponding docs PR in warpdotdev/docs. When a complete spec is found, auto-generates a full docs draft PR and tags the engineer. When a spec is too thin to draft from, pings the engineer directly. Designed to run as a scheduled Oz ambient agent (e.g., every 2-3 days). Use when setting up the automated docs trigger or running a manual docs coverage sweep. If the spec is thin — ping the engineer directly to either flesh out the spec or kick off the docs workflow manually File is at least 40 lines long

What does scan-new-specs require?

| SLACKBOTTOKEN | From buzz environment | Slack bot token for posting via API (already available in the buzz Oz environment) | A spec is uncovered if neither query returns results. Closed-unmerged PRs do not count as coverage — a closed PR signals abandoned work that needs re-triggering. Please check the items marked [UNVERIFIED] and [TODO] in the PR — those are the only things that need your input. 📋 New spec needs docs — not enough detail to auto-draft Configuration keys: LOOKBACK_DAYS, SLACK_CHANNEL, SLACK_BOT_TOKEN, ENG_EMAIL, SLACK_USER_ID, ENG_MENTION, ENG_NAME, ENG_GITHUB.

How do I install scan-new-specs?

Run: npx -y skills add https://github.com/warpdotdev/common-skills --skill scan-new-specs --agent claude-code — the source lives at github.com/warpdotdev/common-skills.

Maintain scan-new-specs?

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

[![scan-new-specs on getagentictools](https://getagentictools.com/badge/skills/warpdotdev-common-skills-scan-new-specs.svg)](https://getagentictools.com/skills/warpdotdev-common-skills-scan-new-specs?ref=badge)

npx agentictools info skills/warpdotdev-common-skills-scan-new-specs

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