Borrowing it
Nothing to install: this file belongs to rmjosea/agentic-sdlc-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rmjosea/agentic-sdlc-kit/main/.agents/skills/write-spec/SKILL.mdgit clone --depth 1 https://github.com/rmjosea/agentic-sdlc-kitWrote 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.
[](https://agentmods.dev/skills/rmjosea/agentic-sdlc-kit/write-spec)<a href="https://agentmods.dev/skills/rmjosea/agentic-sdlc-kit/write-spec"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/write-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.
<a href="https://agentmods.dev/skills/rmjosea/agentic-sdlc-kit/write-spec"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/write-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00810 |
| Opus 5.5 | $0.00025 | $0.00324 |
| Sonnet 5.5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
write-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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Product Specifications
Create the first stable artifact in the workflow. Define what must be true, not the implementation that will make it true.
Do not create a spec merely because code will change. Use one when product
behavior needs a durable acceptance contract; use the direct or plan-only path
from AGENTS.md when that contract would add no value.
Preconditions
Require an explicitly approved conversational understanding or equivalent
authoritative input. If material product ambiguity remains, return to
shape-idea.
Choose spec boundaries
Prefer one specification when the change has one cohesive outcome and shared rules. Split into multiple specifications when capabilities:
- deliver independent user value;
- can be accepted or released separately;
- have distinct actors, rules, or lifecycles;
- require independent planning;
- would force multiple primary objectives into one document.
Split by capability, never by technical layer. Do not create separate frontend, backend, database, or API specs for one product capability.
Before writing multiple specs, show the proposed boundaries, dependencies, and rationale. Ask for confirmation when the decomposition materially affects scope or delivery.
Write
Use assets/spec.template.md. Remove sections that do not add information. Store:
specs/<NNN-capability>/spec.md
When more than one spec exists, maintain a concise specs/README.md containing
only the capability list, state, and functional dependencies. Use
assets/spec-index.template.md.
Assign each spec a stable ID and one lifecycle state:
draft -> approved -> [planned] -> implemented -> verified
draft: still being authored or awaiting product approval.approved: product behavior and acceptance criteria are confirmed.planned: an approved technical plan covers the spec.implemented: the implementation is complete but not yet verified by review evidence.verified: review evidence confirms the acceptance criteria.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 111 lines · 62 tokens per session scan A 70ea2e32219b
write-spec is a skill published in the GitHub repository rmjosea/agentic-sdlc-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 810 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-31.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…