Menú
Create or update the project constitution (principles, non-negotiables, out-of-scope).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.
Use when local verification passed and the feature is ready to ship to Azure.
Use when a plan exists and the application source or IaC needs to be created or updated.
Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code.
Use when the user wants to run the full Specify → Plan → Implement → Deploy loop end-to-end in one shot. Accepts a free-form prompt that is passed to specify.
Use when implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying.
| name | constitution |
| description | Create or update the project constitution (principles, non-negotiables, out-of-scope). |
$ARGUMENTS
$ARGUMENTS is the user's input from the triggering message — assume it's available even if the placeholder appears literally above. Don't ask the user to repeat it unless they provided an empty command.
Gather context. Read specs/constitution.md if it exists (this is an update, not a fresh write). Skim repo context — README.md, top-level docs, project metadata (pyproject.toml, package.json, etc.) — to ground the constitution in reality.
Create if missing. specs/constitution.md should be initialized from assets/constitution-template.md during project setup. If it's missing, copy the template first.
Update specs/constitution.md with these sections:
Guidelines: merge user input with existing content, preserving prior rules unless explicitly overridden; keep it terse — every line should be actionable by /speckit:specify, /speckit:plan, /speckit:tasks; mark genuine unknowns as [NEEDS CLARIFICATION: <question>] rather than inventing constraints; no implementation details, file structures, or task lists — those belong in plan.md and tasks.md.
Report the path to specs/constitution.md and a brief summary of what changed (or "created" if new).