dostulata/initiative
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

Add artifact lifecycle guidance to constitution (v3.2.0)
All checks were successful
CI / check (push) Successful in 2m8s
Details
CI / build-image (push) Has been skipped
Details

Browse Source 
Clarify that spec.md is a living capability document, plan.md/tasks.md
are bounded work packages, and tests are the executable ground truth.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Lukas
2026-03-30 01:06:35 +02:00
parent 09da9a8dfc
commit 43546aaa7b
1 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.specify/memory/constitution.md
View File

@@ -1,9 +1,9 @@
<!-- <!--
Sync Impact Report Sync Impact Report
─────────────────── ───────────────────
Version change: 3.0.0 → 3.1.0 (MINOR — new principle II-A: context-based state flow) Version change: 3.1.0 → 3.2.0 (MINOR — artifact lifecycle guidance)
Modified sections: Modified sections:
- Core Principles: added II-A. Context-Based State Flow (max 8 props, context over prop drilling) - Development Workflow: added artifact lifecycle rules (spec.md living, plan/tasks bounded, tests authoritative)
Templates requiring updates: none Templates requiring updates: none
--> -->
# Encounter Console Constitution # Encounter Console Constitution
@@ -113,6 +113,18 @@ architecture, and quality — not product behavior.
(which creates a feature branch for the full speckit pipeline); (which creates a feature branch for the full speckit pipeline);
changes to existing features update the existing spec via changes to existing features update the existing spec via
`/integrate-issue`. `/integrate-issue`.
- **Artifact lifecycles differ by type**:
- `spec.md` is a **living capability document** — it describes what
the feature does and is updated whenever the feature meaningfully
changes. It survives across multiple rounds of work.
- `plan.md` and `tasks.md` are **bounded work packages** — they
describe what to do for a specific increment of work. After
completion they become historical records. The next round of work
on the same feature gets a new plan, not an update to the old one.
- Tests are the **executable ground truth**. When a spec's
acceptance criteria and the tests disagree, the tests are
authoritative. Spec prose captures intent and context; tests
capture actual behavior.
- The full pipeline (spec → plan → tasks → implement) applies to new - The full pipeline (spec → plan → tasks → implement) applies to new
features and significant additions. Bug fixes, tooling changes, features and significant additions. Bug fixes, tooling changes,
and trivial UI adjustments do not require specs. and trivial UI adjustments do not require specs.
@@ -156,4 +168,4 @@ MUST comply with its principles.
**Compliance review**: Every spec and plan MUST include a **Compliance review**: Every spec and plan MUST include a
Constitution Check section validating adherence to all principles. Constitution Check section validating adherence to all principles.
**Version**: 3.1.0 | **Ratified**: 2026-03-03 | **Last Amended**: 2026-03-19 **Version**: 3.2.0 | **Ratified**: 2026-03-03 | **Last Amended**: 2026-03-30