SPEC-NNN: [título]
SPEC-NNN: [título]
Section titled “SPEC-NNN: [título]”Goal: [1 línea — qué cambia para el usuario] Repos: [lista de repos afectados] Priority: P0|P1|P2
Problem
Section titled “Problem”[Qué dolor resolvemos, para quién — solo tier GRANDE/MEDIANO]
Requirements (RFC 2119)
Section titled “Requirements (RFC 2119)”- [SHALL] [requisito no negociable]
- [SHOULD] [requisito deseable]
- [MAY] [nice-to-have]
Scenarios (GIVEN/WHEN/THEN)
Section titled “Scenarios (GIVEN/WHEN/THEN)”- GIVEN [contexto] WHEN [acción] THEN [resultado esperado]
Constraints
Section titled “Constraints”- [AOT, no reflection, etc.]
- [Cross-repo dependencies]
Acceptance Criteria
Section titled “Acceptance Criteria”- [criterio verificable con test o comando]
Architectural Risk
Section titled “Architectural Risk”Level: LOW | MEDIUM | HIGH Affected: [áreas/repos que pueden romperse] Mitigation: [cómo reducimos el riesgo]
Out of Scope
Section titled “Out of Scope”- [Lo que explícitamente NO se incluye]
Nota: OpenSpec genera la base (Requirements + Scenarios) vía
/opsx:propose. El frontmatter de producto,## Problem, y## Architectural Riskson extensiones Verbara que se inyectan víarules:enopenspec/config.yaml.