What is spec-kit-requirements-fr?

A requirements-writing guide for defining what a software product must do in Spanish. It covers scope, user roles, workflows, testable acceptance criteria, and basic traceability.

Use it to maintain functional requirements and connect them to related decisions, open questions, and project tasks.

It helps turn incomplete or ambiguous ideas into requirements that developers and testers can verify, while recording unanswered questions instead of guessing.

How lksnext-ai-lab/spec-kit-template configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to lksnext-ai-lab/spec-kit-template. 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/lksnext-ai-lab/spec-kit-template/main/.github/skills/spec-kit-requirements-fr/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-template

Made for: Claude Code, Codex.

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/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr/github.svg)](https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr)

Your own site

<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr/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/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-requirements-fr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,229 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.00063	$0.01229
Opus 5.5	$0.00025	$0.00492
Sonnet 5.5	$0.00013	$0.00246
Haiku 4.5	$0.00006	$0.00123

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

Security

Grade A, and why

spec-kit-requirements-fr 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.

.github/skills/spec-kit-requirements-fr/SKILL.md · 122 lines

How it starts

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

Skill: Requirements-FR (spec-kit)

Objetivo

Mantener requisitos funcionales claros, verificables y sin ambigüedad, listos para derivar a UI/API/datos sin mezclar capas.

Archivos que se pueden modificar

Primario: docs/spec/10-requisitos-funcionales.md
Si aplica:
- docs/spec/02-trazabilidad.md
- docs/spec/95-open-questions.md
- docs/spec/adr/ADR-*.md
- docs/spec/96-todos.md

Reglas duras (anti-deriva)

No inventar

Si falta información que cambia el comportamiento → OPENQ (no rellenar).

FR ≠ Diseño (anti-solutioning) Un FR NO debe incluir:

endpoints concretos, nombres de rutas, payloads,
estructura de BBDD/tablas,
componentes UI específicos, layouts o librerías,
elecciones tecnológicas (“usar X”). Eso va en UI/backend/datos/arquitectura.

FR ≠ NFR

Rendimiento, disponibilidad, retención, cifrado, logging, auditoría técnica, etc. se referencian como:
- “Debe cumplir NFR-…” (o enlace a docs/spec/11-requisitos-tecnicos-nfr.md)
No introducir umbrales/cifras si no existen en la spec.

Granularidad

Un FR = 1 capacidad principal que un actor puede ejecutar end-to-end.
Si para validar necesitas 2 historias distintas o 2 actores principales → dividir.
Si es una “variante” de un FR existente (mismo objetivo), mantener como variante, no como FR nuevo.

Criterios de aceptación verificables

Deben ser testeables (Given/When/Then o checklist verificable).
Evitar adjetivos sin condición (“intuitivo”, “rápido”, “fácil”).
Si hay permisos/roles: incluir aceptación de “acceso denegado” cuando aplique.

Convenciones

IDs: FR-### correlativo, no reutilizar.
Prioridad: MVP | Should | Could
Estado: Draft | Validated | Deprecated
Deprecación: mantener el FR con razón y referencia al que lo sustituye (si aplica).

Plantilla obligatoria por FR

FR-### — <Verbo + objeto>

Descripción: (1–3 líneas)
Actor principal: (1)
Actores secundarios: (opcional)
Alcance: IN / OUT (si OUT no está claro → OPENQ)

Read the full file on GitHub · 122 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 · 122 lines · 63 tokens per session scan A 721fe47a93c1

Subscribe to this mod's changes

spec-kit-requirements-fr is a skill published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,229 once invoked, about $0.0003 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.

Planning Writing and docs

spec-kit-requirements-fr next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-kit-requirements-frlksnext-ai-lab/spec-kit-template	Skill	5	8mo ago	Apache-2.0	A	63	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

spec-kit-template: Skill for Claude Code