spec-driven-development-template CLAUDE.md

spec-driven-development-template CLAUDE.md is an instructions file for coding agents from juanklagos/spec-driven-development-template. It costs 627 tokens per session, scanned A, original, MIT.

A template for specification-driven development, where an approved written specification and consistent plan must come before code. It includes guidance for AI-assisted projects and MCP support.

In plain words
What is it for?
Use it to organize requirements, approve plans, set up a specification sidecar for an existing project, and guide implementation from the agreed design.
Why use it?
It prevents implementation from starting before the intended behavior is agreed and defines where project code or a lightweight specification folder should live.

Instructions file

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 instructions/juanklagos/spec-driven-development-template/claude-md
Clone the repo
git clone --depth 1 https://github.com/juanklagos/spec-driven-development-template

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 spec-driven-development-template CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/juanklagos/spec-driven-development-template/claude-md.svg)](https://agentmods.dev/instructions/juanklagos/spec-driven-development-template/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/juanklagos/spec-driven-development-template/claude-md"><img src="https://agentmods.dev/badge/instructions/juanklagos/spec-driven-development-template/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 627 This file is loaded in full into every session.
When invoked 627 The same file — it is already loaded in full.
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.00627 $0.00627
Opus 5 $0.00313 $0.00313
Sonnet 5 $0.00125 $0.00125
Haiku 4.5 $0.00063 $0.00063

Measured 3d ago against content hash 96d4fcf42999, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-driven-development-template CLAUDE.md 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 3d 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.

CLAUDE.md · 47 lines

What it actually says

Claude Operating Rules for this Template

Canonical source:

  • template-context/core-instructions/AGENT_OPERATING_SYSTEM.md
  • sdd.policy.yaml

Hard stop:

  • No code before approved spec and consistent plan.
  • No hay código sin spec aprobada y plan consistente.

Execution workspace:

  • Inside THIS template repository, put runnable code under www/<project-name>/.
  • For a project that already exists somewhere else — the common case — install the compact spec/ sidecar in it and leave the code where it is. That is the recommended default workspace for real work.
  • Dentro de ESTA plantilla, el código ejecutable va en www/<nombre-proyecto>/.
  • Para un proyecto que ya existe en otro sitio —el caso normal— instala el sidecar compacto spec/ y deja el código donde está. Ese es el espacio de trabajo recomendado por defecto para el trabajo real.
  • The user may choose another target path.
  • If the target project lives inside this template, keep it under www/.
  • For real external projects, install the compact spec/ sidecar and keep code in the project root.
  • Para proyectos reales externos, instala el sidecar compacto spec/ y mantén el código en la raíz del proyecto.

Behavior requirements:

  1. Treat this repo as SDD starter template by default.
  2. Ask concise clarification when required data is missing.
  3. Keep changes traceable in specs/ and bitacora/.
  4. Run validation scripts before closing.

Decision log:

  • Record a decision in bitacora/decisiones/YYYY-MM-DD-<slug>.md (use /sdd:decision) when it chose between real alternatives, when it will be expensive to reverse, or when a future reader would ask "why is it like this?".
  • Registra una decisión cuando eligió entre alternativas reales, cuando revertirla será caro, o cuando alguien preguntaría después "¿por qué es así?".
  • Every record includes a "when to revisit" section, and every rationale points at a source (commit, file:line, spec history, CHANGELOG, idea/). Never invent rationale or dates.

Approval and record rule:

  • Approval evidence records WHAT was approved, its scope, the document or proposal it was approved against, and the date. Never a transcription of the chat.
  • La evidencia de aprobación registra QUÉ se aprobó, con qué alcance y contra qué documento, con la fecha. Nunca la transcripción del chat.
  • "hazlo", "dale", "arranca" and the like are not evidence: they say nothing about what was approved.
  • The same rule governs bitacora/ and the summary of each .sdd/user-consent.log line.
  • Correcting the wording of an existing record is legitimate; changing what was approved, by whom, or when is not.

Session close contract:

  • objective
  • active_spec
  • changes
  • validation
  • risks
  • decision_recorded
  • next_step
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. 3d ago First seen · 47 lines · 627 tokens per session scan A 96d4fcf42999

Subscribe to this mod's changes

spec-driven-development-template CLAUDE.md is an instructions file published in the GitHub repository juanklagos/spec-driven-development-template (15 stars, last pushed 3d ago), licensed MIT. It adds 627 tokens to every session, about $0.0031 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.