Closing the intent-to-code chasm - specification-driven development with BDD verification chain
86
92%
Does it follow best practices?
Impact
86%
1.82xAverage score across 14 eval scenarios
Advisory
Suggest reviewing before use
Create or update the project constitution at CONSTITUTION.md — the governing principles for specification-driven development.
MUST contain: governance principles, non-negotiable development rules, quality standards, amendment procedures, compliance expectations.
MUST NOT contain: technology stack, frameworks, databases, implementation details, specific tools or versions. These belong in /iikit-02-plan. See phase-separation-rules.md.
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty).
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.bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-00-constitution/scripts/bash/validate-premise.sh --jsoncat CONSTITUTION.md 2>/dev/null || echo "NO_CONSTITUTION"Load existing constitution — identify placeholder tokens [ALL_CAPS_IDENTIFIER]. Adapt to user's needs (more or fewer principles than template).
Collect values for placeholders:
RATIFICATION_DATE: original adoption dateLAST_AMENDED_DATE: today if changes madeCONSTITUTION_VERSION: semver (MAJOR: principle removal/redefinition, MINOR: new principle, PATCH: clarifications)Draft content: replace all placeholders, preserve heading hierarchy, ensure each principle has name + rules + rationale, governance section covers amendment/versioning/compliance.
Consistency check: validate against plan-template.md, spec-template.md, tasks-template.md.
Sync Impact Report (HTML comment at top): version change, modified principles, added/removed sections, follow-up TODOs.
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.
Phase separation validation: scan for technology-specific content per phase-separation-rules.md. Auto-fix violations, re-validate until clean.
Write TWO files — both are required outputs of this skill:
a) Write CONSTITUTION.md with the finalized constitution content.
b) Write .specify/context.json with the TDD determination extracted from the constitution you just wrote. All downstream skills (testify, bugfix, implement) read TDD policy from this file. Determine the value from the constitution text:
mandatorymandatoryforbiddenoptionaloptionalCreate the file:
mkdir -p .specifyWrite .specify/context.json containing at minimum:
{
"tdd_determination": "<mandatory|optional|forbidden>"
}If .specify/context.json already exists, merge (don't overwrite other fields). You can use jq if available, or write the file directly.
Verify: confirm .specify/context.json exists and contains tdd_determination.
Git init (if needed): git init to ensure project isolation
Report: version, bump rationale, TDD determination, git status
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-00-constitution/scripts/bash/post-phase.sh --phase 00 --commit-files "CONSTITUTION.md,.specify/context.json" --commit-msg "Add project constitution"Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-00-constitution/scripts/powershell/post-phase.ps1 -Phase 00 -CommitFiles "CONSTITUTION.md,.specify/context.json" -CommitMsg "Add project constitution"
Parse next_step from JSON. Present per model-recommendations.md:
Constitution ready!
Next: [/clear → ] <next_step> (model: <tier>)
[- <alt_step> — <reason> (model: <tier>)]
- Dashboard: file://$(pwd)/.specify/dashboard.htmlevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
rules
skills
iikit-00-constitution
scripts
dashboard
iikit-01-specify
iikit-02-plan
iikit-03-checklist
scripts
bash
dashboard
iikit-04-testify
iikit-05-tasks
iikit-06-analyze
iikit-07-implement
iikit-08-taskstoissues
iikit-bugfix
scripts
dashboard
iikit-clarify
iikit-core
references
scripts
bash
dashboard
powershell
templates