An implementation-session workflow for building one planned software feature at a time. BDD means describing expected behavior through scenarios, while TDD means writing tests before the code; DoD means the agreed definition of finished.

It helps agents select the active feature, create its worktree and branch, review behavior scenarios, implement and test the feature, and update the project state and worklog in one commit.

It keeps implementation tied to the project plan, records where work stops, and checks that dependencies, tests, reviews, and completion conditions are handled.

How dbareagimeno/enu configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dbareagimeno/enu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dbareagimeno/enu/develop/.claude/skills/sesion/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/dbareagimeno/enu

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dbareagimeno/enu/sesion/github.svg)](https://agentmods.dev/skills/dbareagimeno/enu/sesion)

Your own site

<a href="https://agentmods.dev/skills/dbareagimeno/enu/sesion"><img src="https://agentmods.dev/badge/skills/dbareagimeno/enu/sesion/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dbareagimeno/enu/sesion"><img src="https://agentmods.dev/badge/skills/dbareagimeno/enu/sesion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,403 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.

Model	Per session	Once invoked
Fable 5.1	$0.00092	$0.01403
Opus 5.5	$0.00037	$0.00561
Sonnet 5.5	$0.00018	$0.00281
Haiku 4.5	$0.00009	$0.00140

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

Security

Grade A, and why

sesion 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.

.claude/skills/sesion/SKILL.md · 81 lines

How it starts

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

Sesión de implementación (BDD → TDD → juicio → DoD)

Una sesión = una feature. El estado vive en el repo, no en tu memoria. Este protocolo envuelve el de docs/plan/implementacion.md §"Protocolo de cada sesión" con las disciplinas BDD y TDD y el juicio clean-room.

Pasos

Sitúate. Lee el puntero ▶ y «Último cierre» en docs/plan/estado.md (el estado vivo); el registro por sesión —dónde se quedó lo anterior— vive en docs/worklog/ (un fichero por sesión + índice). El detalle de la sesión —su enunciado, dependencias y fase— está en docs/plan/implementacion.md. Implementa solo la sesión que marca el puntero; verifica que sus dependencias ("Depende de") están cerradas. Si el puntero está en —, no hay nada que implementar: ofrece /planificar-sesion. Crea el worktree y la rama de la tarea con EnterWorktree y renombra la rama a claude/<tema> — la convención completa vive en CLAUDE.md §"Convenciones de Git".
Escenarios BDD (antes de una línea de código). Lanza el agente escenarista-bdd en modo sesión con la S## y sus §N de espec. Revisa los escenarios devueltos: son tu lista de casos. Si el escenarista reporta un candidato a hallazgo (la espec no da para escribir un escenario), trátalo ya: /hallazgo. Los escenarios que blindan un G## lo nombran en comentario.
TDD: rojo → verde → refactor.
- Rojo: escribe los escenarios como subtests table-driven (t.Run("dado_X_cuando_Y_entonces_Z", ...), testing estándar, sin testify) y compruébalos fallar por la razón correcta.
- Verde: el mínimo que cumple la espec — la firma y semántica exactas del §N, marcadores ⏸/[W] incluidos, ni una función de más.
- Refactor con los tests en verde.
- Si la API no basta para implementar la espec: PÁRATE. Es un hallazgo G##: /hallazgo primero (documentos), código después. Nunca al revés.
Mutación (solo sesiones 🔒). Si la sesión está en el inventario 🔒 (docs/plan/inventario-tests.md), ejecuta /mutacion acotada a los ficheros tocados. Cada mutante LIVED: o un test nuevo que lo mata, o queda anotado como equivalente en el worklog de la sesión.

Read the full file on GitHub · 81 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.

2mo ago First seen · 81 lines · 92 tokens per session scan A 7aa791b44fba

Subscribe to this mod's changes

sesion is a skill published in the GitHub repository dbareagimeno/enu (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 92 tokens to every session and 1,403 once invoked, about $0.0004 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.

LLM Planning TDD Testing ai-agents automation coding-agent developer-tools

tdd

Test-driven development — write a failing test that names the behavior, watch it fail, implement the minimum to make it pass, then refactor with tests green. Works for new features, bug fixes, and behavior changes. Use when the user says "tdd", "test-first", "write tests first", or wants a change built test-first.

genai-io/san · 73 tokens

enu: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Sesión de implementación (BDD → TDD → juicio → DoD)

Pasos

What this file has done since we first saw it

Other skills, from other repositories

tdd

tdd

systematic-debugging

test-driven-development

bad-case-to-dpo

resolve-author-fix