Constitution
Spec-Driven Agentic OS for Claude Code + OpenAI Codex CLI. Native skills, subagents, hooks, and an adversarial codex review loop. Inspired by github/spec-kit, built on Claude Code primitives. No daemon, no vendor lock-in.
npx -y skills add MakFly/ai-dev-kit --skill constitutionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use PROACTIVELY when the user wants to author, amend, or revise memory/constitution.md (the supreme project contract). Triggers on /constitution and on phrases like "set the project principles", "redéfinis les principes", "what are our invariants". Never use during a feature flow (specify/plan/...) — pause the flow and explain.
SKILL.md
3.0 KB, as published. Nobody here has run it
/constitution
You edit memory/constitution.md — the supreme contract of this repository.
Pipeline position
/constitution [YOU] → /specify → /clarify → /plan → /tasks → /implement → /review
The constitution is rarely edited. Most sessions never touch it. Treat each edit as a deliberate amendment, not a normal feature flow step.
Procedure
- Read current state.
cat memory/constitution.md. - If placeholder: draft the initial constitution from scratch using the structure below. Confirm with user before writing.
- If real content: treat the user's amendment as a proposed diff. Show the diff, explain consequences, ask for explicit GO before writing.
- Write. Commit message:
chore(constitution): <one line>. - Stamp version. Each amendment bumps the constitution version (semver: amendment = patch, structural change = minor, full rewrite = major).
Required structure of memory/constitution.md
# Constitution — ai-dev-kit
**Version:** v<major>.<minor>.<patch>
**Last amended:** <ISO-8601>
## Article I — Principles
1. <principle 1> — <one-line rationale>
2. ...
## Article II — Workflow
- The canonical loop is /constitution → /specify → /clarify → /plan → /tasks → /implement → /review.
- Skipping a step requires an ADR in memory/decisions/.
## Article III — Authoring conventions
- <agent frontmatter rules>
- <skill frontmatter rules>
- <commit conventions>
## Article IV — Out of scope
- <bounded list of what this project will NOT do>
## Article V — Verification
- Required commands and their meaning.
- Codex review is non-optional for spec, plan, tasks.
## Amendments
- <date> v<old> → v<new> — <summary>
Doctrine
- Reuse > rewrite. Amendments are small and surgical. Full rewrites need user signoff.
- Conflict resolution. If a future spec/plan/code conflicts with the constitution, the constitution wins. Always.
- Bounded scope. Articles I-V are the schema. Do not invent Article VI without user direction.
- Pause feature flows. If invoked during an active /specify or /plan, refuse and explain — finish or abort the feature flow first.
After write
Print to chat:
- New constitution version.
- One-paragraph summary of the amendment.
- Any spec/plan/code in the repo that may now be in violation (
grep -lcross-check).