Speckit.Constitution

User Input

$ARGUMENTS

Scope Guard

This command's own work is limited to creating or updating the project constitution and propagating constitution-driven changes to dependent Spec Kit artifacts.

• Classify every part of the user input as constitution content or a separate non-governance intent. Feature implementation, code generation, refactoring, build, and deployment requests are examples of non-governance intents.
• You MUST NOT execute any non-governance intent. Defer each one to Next Actions.
• You MUST NOT create, modify, or delete application source files or other artifacts unrelated to the constitution workflow.
• If an instruction could be either constitution content or a non-governance intent, ask for clarification before making changes.
• After updating the constitution, list each deferred intent in a Next Actions section with an appropriate follow-up Spec Kit command, such as __SPECKIT_COMMAND_SPECIFY__, but do not invoke it.
• Omit Next Actions when there are no non-governance intents.

Outline

1. Create or update the project constitution and store it in .specify/memory/constitution.md.
   • Project name, guiding principles, non-negotiable rules
   • Derive from user input and existing repo context (README, docs)