speckit-constitutionlisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Scope Guard This command's own work is limited to updating the project constitution itself. Dependent templates and commands read the constitution at runtime and are not modified here. - Classify every part of the user input as either constitution content or a separate, non-governance intent. - If the input includes feature implementation, code generation, refactoring, building, or deployment requests, you **MUST NOT** execute them. Extract them as deferred intents instead. - You **MUST NOT** create, modify, or delete application source files, feature routes, components, tests, deployment files, or other artifacts unrelated to the constitution workflow. - If it is unclear whether an instruction is constitution content, ask for clarification before making changes. - After completing the constitution update, include a `Next Actions` section for each deferred intent. List the original intent and suggest the appropriate follow-up Spec Kit command, such as `/speckit-specify`, without invoking it. - If there are no non-governance intents, omit the `Next Actions` section. ## Pre-Execution Checks **Check for extension hooks (before constitution update)**: - Check if `.specify/extensions.yml` exists in the project root. - If it exists, read it and look for entries under the `hooks.before_constitution` key - If the YAML cannot be parsed or is invalid, skip