agentmods.dev

create-tech-spec

create-tech-spec is a skill for Claude Code from jpoutrin/product-forge. It costs 12 tokens per session (735 once invoked), scanned A, original, MIT.

A template-driven workflow for creating a technical specification, a document that records implementation details and design decisions.

In plain words
What is it for?
Use it to create a draft specification with a generated filename, identifier, dates, and the project’s required directory structure.
Why use it?
It gives new specifications consistent numbering, metadata, folders, status, and optional links to related RFCs.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the devops-data plugin — 17 skills, 4 agents shipped together

not rated 16repo 7mo ago A scan 12 tokens original MIT

Good fit Use it to create a draft specification with a generated filename, identifier, dates, and the project’s required directory structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/create-tech-spec
View source ↗ jpoutrin/product-forge
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 jpoutrin/product-forge --skill create-tech-spec
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install devops-data, the plugin that ships this one along with the rest of its 17 skills, 4 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 create-tech-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-tech-spec/github.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/create-tech-spec)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/create-tech-spec"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-tech-spec/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 create-tech-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/create-tech-spec"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-tech-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 735 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.00012 $0.00735
Opus 5.5 $0.00005 $0.00294
Sonnet 5.5 $0.00002 $0.00147
Haiku 4.5 $0.00001 $0.00073

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

Security

Grade A, and why

create-tech-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 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.

plugins/devops-data/skills/create-tech-spec/SKILL.md · 107 lines

How it starts

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

create-tech-spec

Category: Technical Architecture

Usage

/create-tech-spec <spec-title> [--rfc RFC-XXXX]

Arguments

  • <spec-title>: Required - Descriptive title for the Tech Spec (will be kebab-cased for filename)
  • --rfc RFC-XXXX: Optional - Link to RFC that this spec implements

Execution Instructions

When this command is run, Claude Code should:

  1. Determine Tech Spec Number

    • Scan tech-specs/ directory (all subdirectories) for existing files
    • Find highest TS-XXXX number
    • Increment by 1 for new spec
    • If no specs exist, start with TS-0001

  2. Create Directory Structure (if not exists)

    tech-specs/
├── draft/
├── approved/
├── reference/
└── archive/
    └── YYYY/

  3. Generate Tech Spec File

    • Convert title to kebab-case: "User Authentication API" → "user-authentication-api"
    • Create file: tech-specs/draft/TS-XXXX-<kebab-title>.md
    • Use template from skill references

  4. Populate Metadata

    • Set tech_spec_id to new number
    • Set title from argument
    • Set status to DRAFT
    • Set decision_ref to RFC if provided
    • Set created and last_updated to today's date
    • Leave author for user to fill

  5. If RFC provided, validate and link

    • Check RFC exists
    • Add link in metadata
    • Suggest copying relevant technical details from RFC

  6. Confirm Creation

    Created TS-XXXX: <title>

Location: tech-specs/draft/TS-XXXX-<kebab-title>.md
Status: DRAFT
RFC Link: RFC-XXXX (if provided)

Next steps:
1. Fill in the Executive Summary
2. Document the Design Overview with architecture diagram
3. Complete API and Data Model sections
4. When ready: /tech-spec-status TS-XXXX --set APPROVED

Template Reference

Use the template from: plugins/devops-data/skills/technical-specification/references/tech-spec-template.md

Example Usage

# Standalone tech spec
/create-tech-spec User Authentication API

# Tech spec implementing an RFC
/create-tech-spec Payment Gateway Integration --rfc RFC-0042

Read the full file on GitHub · 107 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 · 107 lines · 12 tokens per session scan A d56eb048db0a

Subscribe to this mod's changes

create-tech-spec is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 735 once invoked, about $0.0000 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.

PlanningWriting and docs
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

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

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens