| name | setting-up-constitution |
| description | Creates or updates the project constitution that defines migration principles, constraints, and conventions.
Triggers: "set up constitution", "define migration principles", "create project rules", "establish conventions", "establish migration constitution".
NOT for: implementation, implementation planning, task generation.
|
User Input
You MUST consider the user input before proceeding (if not empty).
Mandatory Principles
Outline
You are creating or updating the project constitution to your task's artifact path (the Artifact path: from task metadata). Write constitution.md there. Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
Follow this execution flow:
-
Load the existing constitution template at skills/setting-up-constitution/templates/constitution-template.md. Identify every placeholder token of the form [ALL_CAPS_IDENTIFIER].
IMPORTANT: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
-
Collect/derive values for placeholders:
- If user input (conversation) supplies a value, use it.
- If knowledge graph or constitution history contains relevant info, infer from there.
- Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
- [If exists] Read
context.md or similar for any runtime guidance that may inform principle definitions.
- DO NOT read source code files (.java, .ts, .py, .cs, etc.). Constitution is a high-level governance document. You only need: project structure (directory tree), build files (pom.xml, package.json, build.gradle), config files (application.yml, web.xml), and documentation (README, docs/). If you need to understand the tech stack or architecture patterns, read the top-level build file and directory structure — never individual source files.
