Skip to content

Commit 692fd34

Browse files
committed
Update constitution.md
1 parent 2f043ef commit 692fd34

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

templates/commands/constitution.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ description: Create or update the project constitution from interactive or provi
33
# (No scripts section: constitution edits are manual authoring assisted by the agent)
44
---
55

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.
77

88
Follow this execution flow:
99

10-
1. Load the existing constitution template at `.specify/memory/constitution.md`.
10+
1. Load the existing constitution template at `/memory/constitution.md`.
1111
- Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
1212
- List them in a table with columns: Placeholder | Description In Comments (if present) | Current Value (if any) | Required?
1313

@@ -28,10 +28,10 @@ Follow this execution flow:
2828
- Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
2929

3030
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.
3535
- Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
3636

3737
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:
4848
- Dates ISO format YYYY-MM-DD.
4949
- Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
5050

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).
5252

5353
8. Output a final summary to the user with:
5454
- New version and bump rationale.
@@ -65,4 +65,4 @@ If the user supplies partial updates (e.g., only one principle revision), still
6565

6666
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.
6767

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

Comments
 (0)