agentmods.dev

spec

A command for turning product-design documents into a technical specification. A technical specification describes the data, interfaces, rules, and quality requirements engineers need to build a product.

In plain words
What is it for?
Use it to define data models, API endpoints, business rules, non-functional requirements such as reliability or performance, and a complete technical specification.
Why use it?
It connects design decisions to implementation details and highlights missing design information. It can still proceed with stated assumptions when required documents are unavailable.

Command

3 6d ago A scan 8 tokens original Apache-2.0
View the source file clownware/product-dev
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.

agentmods
npx agentmods add commands/clownware/product-dev/spec
Clone the repo
git clone --depth 1 https://github.com/clownware/product-dev
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00302
Opus 5 $0.00004 $0.00151
Sonnet 5 $0.00002 $0.00060
Haiku 4.5 $0.00001 $0.00030

Measured yesterday against content hash d7f4c5f88f9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec 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 yesterday.

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.

plugin/commands/spec.md · 32 lines

What it actually says

Start a technical specification session using the tech-spec skill.

Gate Check

  1. Read .product-dev/context.json. Verify these artifacts exist:

    • solution_concept (required)
    • user_flow (required)

  2. If either is missing, report what's needed:

    "Technical specs require design artifacts that don't exist yet. Missing: [list]. Run /product-dev:idea to build a solution concept, then use the product-flow skill to map the user flow."

    Do not hard-block — if the user insists, proceed with available artifacts and note assumptions.

  3. Also check for optional artifacts that improve spec quality: screen_inventory, prototype_scope, hypothesis_statement.

Execution

  1. Spawn the Tech Spec Writer subagent (plugin/agents/tech-spec-writer.md).

  2. If $ARGUMENTS specifies a focus area, direct the subagent to that section only. Otherwise, run the full sequence: data models → API endpoints → business rules → NFRs.

  3. The subagent writes intermediate artifacts (data_models, api_contracts, business_rules, nfr) and a final technical_spec to the registry.

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. yesterday First seen · 32 lines · 8 tokens per session scan A d7f4c5f88f9f

Subscribe to this mod's changes

spec is a command published in the GitHub repository clownware/product-dev (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 8 tokens to every session and 302 once invoked, about $0.0000 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.

Backend and APIsData and AIFrontendclaude-codeclaude-code-pluginclaude-skillsmcpprompt-toolkitui
Related

Other commands, from other repositories

start

Front door. Reads the current project (framework, tokens, brief, spec, harness) and reports what ui-craft can do right now, then routes you to the right next step. Run this first if you're new or unsure where to begin. No code changes.

educlopez/ui-craft · 54 tokens

tokens

Audit or establish the project's 3-layer token spine.

educlopez/ui-craft · 11 tokens

remember

Record a learned design constraint from a correction into the project brief.

educlopez/ui-craft · 13 tokens

craft

One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.

educlopez/ui-craft · 64 tokens

audit

Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table.

educlopez/ui-craft · 19 tokens

brief

Write or update the project's durable design brief at .ui-craft/brief.md.

educlopez/ui-craft · 17 tokens