From loom
Maintain durable project identity and constraints. Use when principles, decisions, roadmap direction, or long-lived project policy must change.
npx claudepluginhub z3z1ma/agent-loom --plugin loomThis skill uses the workspace's default tool permissions.
Constitution is Loom's highest project-facing owner layer.
Authors enforceable project constitutions for greenfield projects with testable principles, enforcement mechanisms, rationale, and amendment processes.
Creates or updates project constitution template by filling placeholders from inputs or repo context, semantic versioning, and propagating changes to dependent artifacts.
Creates or updates .specify/memory/constitution.md by collecting governance principles, filling placeholders, semver versioning, and propagating changes to templates and agent configs. For initial governance setup, amendments, or syncing.
Share bugs, ideas, or general feedback.
Constitution is Loom's highest project-facing owner layer.
Use it when the project needs to remember what it is and how it should judge future work.
constitution:mainDecision records and roadmap records are first-class constitutional artifacts, not subtypes tucked under the main constitution file. Decision records are Loom's ADR layer: they capture durable architectural and policy choices and their rejected alternatives, so future agents inherit precedent instead of re-deriving it. Roadmap records live in the same subsystem because a roadmap is strategic direction made durable — sequencing at the policy layer, not sequencing at the execution layer.
Roadmaps express durable strategic direction and policy-level milestones.
They do not replace initiative success metrics, plan sequencing milestones, or ticket execution state. If a roadmap starts tracking day-to-day progress, route that detail down into initiatives, plans, or tickets.
Good constitutional writing is:
A constitutional record should help a future agent decide, not merely admire the prose.
Before making a non-trivial architectural or policy choice, grep the constitution subsystem first. Decision records are precedent; the roadmap is strategic sequencing; constitution:main is current framing. A choice that re-derives a prior decision without citing it wastes work and risks contradicting accepted policy.
Useful starting queries:
rg -n '^id:' .loom/constitution — list every constitutional recordfind .loom/constitution/decisions -name '*.md' | sort — scan precedent by filenamerg -n '<topic>' .loom/constitution — check whether this topic already has policyconstitution:main, a decision record, or a roadmap recordconstitution:main, which usually stays link-lightRead immediately for constitutional changes:
references/record-families.md when deciding whether the change belongs in
constitution:main, a decision record, or a roadmap.references/writing-standard.md before accepting durable policy language or
when the prose risks becoming vague philosophy.Then read conditionally:
templates/constitution.md only when creating or reshaping
constitution:main.templates/decision.md only when recording a citable architectural or
policy choice with rejected alternatives.templates/roadmap.md only when durable strategic sequencing belongs above
plans.