agentmods.dev

dev-specification-qa

dev-specification-qa is a skill for Claude Code from cicababba/claude-plugins-marketplace. It costs 46 tokens per session (1,101 once invoked), scanned A, original, MIT.

A question-and-answer process for turning an initial development idea into a written specification. It asks one important question at a time and records requirements, constraints, and acceptance criteria.

In plain words
What is it for?
Use it to gather requirements for a feature, clarify constraints, define how success will be tested, and create a structured specification.
Why use it?
It helps uncover missing details before planning or implementation begins, reducing the risk of building the wrong thing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dev-workflow-automation plugin — 9 skills, 4 commands, 11 agents shipped together

not rated 3repo 9mo ago A scan 46 tokens original MIT

Good fit Use it to gather requirements for a feature, clarify constraints, define how success will be tested, and create a structured specification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cicababba/claude-plugins-marketplace/dev-specification-qa
View source ↗ cicababba/claude-plugins-marketplace
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cicababba/claude-plugins-marketplace --skill dev-specification-qa
Clone the repo
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplace

Made for: Claude Code.

Or install dev-workflow-automation, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 11 agents.

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 dev-specification-qa

README.md
[![agentmods](https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-specification-qa.svg)](https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-specification-qa)
Your own site
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-specification-qa"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-specification-qa.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,101 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.
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.00046 $0.01101
Opus 5 $0.00023 $0.00550
Sonnet 5 $0.00009 $0.00220
Haiku 4.5 $0.00005 $0.00110

Measured 8d ago against content hash fd37cf3fb3d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

dev-specification-qa 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 8d 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.

dev-workflow-automation/skills/dev-specification-qa/SKILL.md · 187 lines

How it starts

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

Dev Specification Q&A

This skill handles the specification gathering phase through iterative questioning.

When to Use

  • After context analysis is complete in /init
  • When gathering requirements for a new feature
  • When clarifying constraints and acceptance criteria
  • Before any planning or implementation begins

Input

  • sessionPath: Path to the current session directory
  • contextAnalysis: Content or reference to context-analysis.md
  • taskDescription: Initial task description from user
  • partialSpec (optional): Existing partial specification to continue from

Responsibilities

  • Drive an interactive Q&A loop
  • Ask exactly ONE high-impact question at a time
  • Ask follow-ups for unclear answers (max 4 sequential follow-ups)
  • Prioritize blocking unknowns (requirements, contracts, constraints)
  • Build a structured Specification including:
    • Overview
    • Functional requirements
    • Non-functional requirements
    • Constraints
    • Integration points
    • Error handling & edge cases
    • Test decision: testsRequired: true | false | "unclear"
  • Present a Quick Summary for user confirmation
  • Write specification.md via artifact-fs-manager only after confirmation

MUST NOT

  • Generate any "Plan", "Roadmap", or implementation tasks
  • Generate or change code
  • Make assumptions without clarification
  • Ask multiple questions at once
  • Proceed to planning or implementation
  • Skip user confirmation before saving specification

Process

Step 1: Initialize Q&A

  1. Review contextAnalysis to understand existing codebase
  2. Review taskDescription to understand the goal
  3. Identify the most critical unknown that blocks progress
  4. Formulate ONE targeted question

Step 2: Q&A Loop

For each question cycle:

  1. Identify highest-impact unknown:

    • What requirement is most unclear?
    • What constraint could change the approach?
    • What integration point needs clarification?

  2. Ask ONE question:

    • Be specific and targeted
    • Provide context why this question matters
    • Offer examples if helpful

Read the full file on GitHub · 187 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. 8d ago First seen · 187 lines · 46 tokens per session scan A fd37cf3fb3d5

Subscribe to this mod's changes

dev-specification-qa is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 46 tokens to every session and 1,101 once invoked, about $0.0002 per session on Opus 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-31.

PlanningWriting and docs
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens