You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: templates/commands/constitution.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,11 @@ description: Create or update the project constitution from interactive or provi
3
3
# (No scripts section: constitution edits are manual authoring assisted by the agent)
4
4
---
5
5
6
-
You are updating the project constitution at `.specify/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
6
+
You are updating the project constitution at `/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
7
7
8
8
Follow this execution flow:
9
9
10
-
1. Load the existing constitution template at `.specify/memory/constitution.md`.
10
+
1. Load the existing constitution template at `/memory/constitution.md`.
11
11
- Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
12
12
- List them in a table with columns: Placeholder | Description In Comments (if present) | Current Value (if any) | Required?
4. Consistency propagation checklist (convert prior checklist into active validations):
31
-
- Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
32
-
- Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
33
-
- Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
34
-
- Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
31
+
- Read `/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
32
+
- Read `/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
33
+
- Read `/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
34
+
- Read each command file in `/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
35
35
- Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
36
36
37
37
5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
@@ -48,7 +48,7 @@ Follow this execution flow:
48
48
- Dates ISO format YYYY-MM-DD.
49
49
- Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
50
50
51
-
7. Write the completed constitution back to `.specify/memory/constitution.md` (overwrite).
51
+
7. Write the completed constitution back to `/memory/constitution.md` (overwrite).
52
52
53
53
8. Output a final summary to the user with:
54
54
- New version and bump rationale.
@@ -65,4 +65,4 @@ If the user supplies partial updates (e.g., only one principle revision), still
65
65
66
66
If critical info missing (e.g., ratification date truly unknown), insert `TODO(<FIELD_NAME>): explanation` and include in the Sync Impact Report under deferred items.
67
67
68
-
Do not create a new template; always operate on the existing `.specify/memory/constitution.md` file.
68
+
Do not create a new template; always operate on the existing `/memory/constitution.md` file.
0 commit comments