Intent Integrity Kit Constitution

Create or update the project constitution at CONSTITUTION.md — the governing principles for specification-driven development.

Scope

MUST contain: governance principles, non-negotiable development rules, quality standards, amendment procedures, compliance expectations, quality governance section referencing QA-PLAN.md.

Quality Governance section (MUST be included in every constitution):

### Quality Governance
QA-PLAN.md is the authoritative quality artifact for this project. It aggregates:
- Global Definition of Done and acceptance criteria (derived from this constitution)
- Per-feature qa/ subdirectories (created emergently by /sdd:spec and /sdd:test)
- Quality gate status (updated by /sdd:analyze)
- Feature quality registry (AC coverage, test coverage, checklist completion)
Run /sdd:qa to generate or refresh. Auto-invoked by /sdd:analyze.

MUST NOT contain: technology stack, frameworks, databases, implementation details, specific tools or versions. These belong in /iikit-02-plan. See phase-separation-rules.md.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Prerequisites Check

1. Check PREMISE.md exists: test -f PREMISE.md. If missing: ERROR — "PREMISE.md not found. Run /iikit-core init first to create it." Do NOT proceed without PREMISE.md.
2. Validate PREMISE.md:

   bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/validate-premise.sh --json
   

   If FAIL (missing sections or placeholders): ERROR — show details, suggest re-running init.
3. Check if constitution exists: cat CONSTITUTION.md 2>/dev/null || echo "NO_CONSTITUTION"
4. If missing, copy from constitution-template.md

Execution Flow

1. Load existing constitution — identify placeholder tokens [ALL_CAPS_IDENTIFIER]. Adapt to user's needs (more or fewer principles than template).

2. Collect values for placeholders:

   • From user input, or infer from repo context
   • RATIFICATION_DATE: original adoption date
   • LAST_AMENDED_DATE: today if changes made
   • CONSTITUTION_VERSION: semver (MAJOR: principle removal/redefinition, MINOR: new principle, PATCH: clarifications)

3. Draft content: replace all placeholders, preserve heading hierarchy, ensure each principle has name + rules + rationale, governance section covers amendment/versioning/compliance.

4. Consistency check: validate against plan-template.md, spec-template.md, tasks-template.md.

5. Sync Impact Report (HTML comment at top): version change, modified principles, added/removed sections, follow-up TODOs.

6. Validate: no remaining bracket tokens, version matches report, dates in ISO format, principles are declarative and testable. Constitution MUST have at least 3 principles — if fewer, add more based on the project context.

7. Phase separation validation: scan for technology-specific content per phase-separation-rules.md. Auto-fix violations, re-validate until clean.

8. Write to CONSTITUTION.md

9. Store TDD determination in .specify/context.json so all skills read from here instead of re-parsing the constitution:

   TDD_DET=$(bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/testify-tdd.sh get-tdd-determination "CONSTITUTION.md")
   

   Write to .specify/context.json using jq (merge, don't overwrite):

   jq --arg det "$TDD_DET" '. + {tdd_determination: $det}' .specify/context.json > .specify/context.json.tmp && mv .specify/context.json.tmp .specify/context.json
   

   If .specify/context.json doesn't exist, create it: echo '{}' | jq --arg det "$TDD_DET" '{tdd_determination: $det}' > .specify/context.json

10. Git init (if needed): git init to ensure project isolation

11. Commit: git add CONSTITUTION.md .specify/context.json && git commit -m "Add project constitution"

12. Dashboard Refresh (optional, never blocks):

bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/generate-dashboard-safe.sh

Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/generate-dashboard-safe.ps1

13. Report: version, bump rationale, TDD determination, git status, suggested next steps

Formatting

• Markdown headings per template, lines <100 chars, single blank line between sections, no trailing whitespace.

Next Steps

Run: bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/next-step.sh --phase 00 --json Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/next-step.ps1 -Phase 00 -Json

Parse the JSON and present:

1. If clear_after is true: suggest /clear before proceeding
2. Present next_step as the primary recommendation
3. If alt_steps non-empty: list as alternatives
4. For next_step and each alt_step, include the model_tier from the JSON so the user knows which model is best for each option. Look up tiers in model-recommendations.md for agent-specific switch commands.
5. Append dashboard link

Format:

Constitution ready!
Next: [/clear → ] <next_step> (model: <tier>)
[- <alt_step> — <reason> (model: <tier>)]

- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)

Usage

Example invocations:

• "/iikit-00-constitution" — Run the full iikit 00 constitution workflow
• "iikit 00 constitution on this project" — Apply to current context

Validation Gate

• Output follows the defined structure and format [EXPLICIT]
• All claims are tagged with evidence markers [EXPLICIT]
• No placeholder content (TBD, TODO) [EXPLICIT]
• Actionable recommendations with priority levels [EXPLICIT]
• Assumptions explicitly documented [EXPLICIT]

Assumptions & Limits

• Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
• Requires English-language output unless otherwise specified [EXPLICIT]
• Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate