agentmods.dev

tech-spec-status

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

A command for viewing a technical specification's details or moving it through its lifecycle. It can show the document's metadata and summary, or change its status and link it to an RFC, a Request for Comments document used to propose and review technical decisions.

In plain words
What is it for?
Use it to find a specification by ID, inspect its location and summary, change its status, or attach an RFC number.
Why use it?
It keeps specification status and related decision records in one place. This makes it easier to tell whether a design is still being written, approved for implementation, complete, or obsolete.

Skill for Claude CodeCodex

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

not rated 15 6mo ago A scan 13 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/jpoutrin/product-forge/tech-spec-status
Any agent
npx skills add jpoutrin/product-forge --skill tech-spec-status
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code, Codex.

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 tech-spec-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/tech-spec-status.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/tech-spec-status)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/tech-spec-status"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/tech-spec-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 968 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.1 $0.00013 $0.00968
Opus 5 $0.00006 $0.00484
Sonnet 5 $0.00003 $0.00194
Haiku 4.5 $0.00001 $0.00097

Measured 5d ago against content hash 1eb9494d04a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

tech-spec-status 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 5d 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/tech-spec-status/SKILL.md · 174 lines

How it starts

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

tech-spec-status

Category: Technical Architecture

Usage

/tech-spec-status <spec-id> [options]

Arguments

  • <spec-id>: Required - Tech Spec identifier (e.g., TS-0042 or just 0042)

Options

Option Description
--set <status> Transition to new status
--link-rfc <RFC-XXXX> Link to an RFC

Valid Statuses

  • DRAFT - Being written
  • APPROVED - Ready for implementation
  • REFERENCE - Implementation complete
  • ARCHIVED - Superseded or deprecated

Execution Instructions

View Status (no --set)

When viewing a Tech Spec:

  1. Find the Spec file

    • Search all tech-specs/ subdirectories
    • Match by Spec ID in filename or frontmatter

  2. Display Spec Details

TS-0042: Payment Gateway Integration
======================================

Status:      APPROVED
Author:      Jane Doe
Created:     2025-12-01
Updated:     2025-12-05
RFC Link:    RFC-0042
Location:    tech-specs/approved/TS-0042-payment-gateway-integration.md

Summary:
  [First 2-3 sentences of the Executive Summary]

Valid Transitions:
  → REFERENCE  (implementation complete)
  → ARCHIVED   (superseded or deprecated)

Commands:
  /tech-spec-status TS-0042 --set REFERENCE

Update Status (with --set)

When updating status:

  1. Validate Transition

    Valid transitions:

    From To
    DRAFT APPROVED
    APPROVED REFERENCE, ARCHIVED
    REFERENCE ARCHIVED

  2. Perform Pre-transition Checks

    For DRAFT → APPROVED:

    • Check all required sections are complete
    • Warn if placeholders remain
    • Suggest running checklist

    For APPROVED → REFERENCE:

    • Ask for implementation link (repo, PR)
    • Ask about deviations from spec

    For any → ARCHIVED:

    • Prompt for archive reason
    • Ask for link to replacement spec (if superseded)

  3. Update Spec File

    • Update status in frontmatter
    • Update last_updated to today
    • Add archive_date if archiving
    • Add archive_reason if archiving

Read the full file on GitHub · 174 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. 5d ago First seen · 174 lines · 13 tokens per session scan A 1eb9494d04a1

Subscribe to this mod's changes

tech-spec-status is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 968 once invoked, about $0.0001 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-30.

Planning
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