agentmods.dev

common-skills: Skill for Claude Code

.agents/skills/spec-driven-implementation/SKILL.md

spec-driven-implementation is a skill for Claude Code, Codex from warpdotdev/common-skills. It costs 61 tokens per session (1,227 once invoked), scanned A, original, MIT.

A spec-first workflow for substantial software features. It records what the feature should do in a product specification and, when needed, how it should be built in a technical specification.

In plain words
What is it for?
Use it to create and maintain PRODUCT.md and TECH.md files for significant features, usually alongside a corresponding Linear issue.
Why use it?
Writing the decisions down before coding reduces ambiguity and gives implementation and review a shared reference.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is warpdotdev/common-skills's own configuration. It tells Claude Code and Codex how to work on common-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything common-skills configures →

not rated 636repo +6 today A scan Socket: passSnyk: passSkillSpector: pass 61 tokens original MIT
View source ↗ warpdotdev/common-skills
Reuse

Borrowing it

Nothing to install: this file belongs to warpdotdev/common-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/warpdotdev/common-skills/main/.agents/skills/spec-driven-implementation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/warpdotdev/common-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spec-driven-implementation

README.md
[![agentmods](https://agentmods.dev/badge/skills/warpdotdev/common-skills/spec-driven-implementation/github.svg)](https://agentmods.dev/skills/warpdotdev/common-skills/spec-driven-implementation)
Your own site
<a href="https://agentmods.dev/skills/warpdotdev/common-skills/spec-driven-implementation"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/spec-driven-implementation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for spec-driven-implementation

Your own site · 80×15
<a href="https://agentmods.dev/skills/warpdotdev/common-skills/spec-driven-implementation"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/spec-driven-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 15 Sept 2026
  • Snyk pass 15 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.01227
Opus 5.5 $0.00024 $0.00491
Sonnet 5.5 $0.00012 $0.00245
Haiku 4.5 $0.00006 $0.00123

Measured 1mo ago against content hash 242028fe3ed0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-driven-implementation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/spec-driven-implementation/SKILL.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

spec-driven-implementation

Drive a spec-first workflow for substantial features in Warp.

Overview

Use this skill for significant features where a written spec will improve implementation quality, reduce ambiguity, or make review easier. Be pragmatic: not every change needs specs.

Specs should usually live in:

  • specs/<linear-ticket-number>/PRODUCT.md
  • specs/<linear-ticket-number>/TECH.md

For example:

  • specs/APP-1234/PRODUCT.md
  • specs/APP-1234/TECH.md

specs/ should contain only ticket-named directories as direct children. Do not create engineer-named subdirectories or feature-slug directories there.

If a relevant Linear issue does not already exist, create one before writing specs. Use the Linear MCP tools directly:

  • list_teams to find the appropriate team
  • list_issue_labels to inspect the expected labels/tags
  • save_issue to create the issue with the appropriate team and labels

If the correct team or labels are not obvious from the request and surrounding context, use ask_user_question to clarify rather than guessing.

These specs should largely be written by agents, not by hand, and should be checked into source control so they can be reviewed and kept current with the code.

When specs are required

Strongly prefer specs when the change is substantial, such as:

  • product or architectural ambiguity
  • expected implementation size around 1k+ LOC
  • deep or cross-cutting stack changes
  • risky behavior changes where regressions would be expensive
  • work where agent quality will improve materially from clearer inputs

Specs are often unnecessary for:

  • small, local bug fixes
  • straightforward refactors
  • narrow UI tweaks with little ambiguity

For pure UI changes, the product spec is often useful while the tech spec may be unnecessary.

Workflow

1. Decide whether the feature needs specs

Evaluate the size, ambiguity, and risk of the feature. If specs will not meaningfully improve execution or review, skip them and focus on verification instead.

Read the full file on GitHub · 144 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 144 lines · 61 tokens per session scan A 242028fe3ed0

Subscribe to this mod's changes

spec-driven-implementation is a skill published in the GitHub repository warpdotdev/common-skills (636 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,227 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens