القائمة
Create or amend the constitution — the project's supreme, enforceable law. Everything built afterward must comply.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.
| name | Constitute |
| description | Create or amend the constitution — the project's supreme, enforceable law. Everything built afterward must comply. |
| argument-hint | [--review] |
Create the constitution: the project's mission, technology/tools, architecture and organizational principles, standards, testing and quality philosophy, quality gates, security, performance, documentation, and version-control strategy. Everything built afterward must comply. The constitution is supreme — no spec, skill, or instruction may contradict it.
Runs immediately after discovery. Hard gate: refuses if .genesis/discovery/context.md is missing ("Run /genesis-discover first").
.genesis/discovery/context.md (required).genesis/project-state.md.genesis/templates/constitution-template.md--review) all .genesis/features/*/spec.md and .genesis/design/decisions/* (ADRs)--review mode: read the existing constitution + all approved specs + ADRs and produce a drift report — sections that conflict with specs, shifted tech choices, abandoned patterns, suggested amendments. Then stop.build / test / lint commands the project uses (e.g. npm test, cargo test, pytest). /genesis-accept runs these and records the results.project-state.md Key Decisions table. Optionally offer to generate git hooks (commit-msg, pre-commit) and a CI workflow derived from the gates..genesis/constitution/index.md — the supreme law. Every technology/tool choice traces to discovery; principles are specific enough to enforce; the Amendment Process is always included.project-state.md (phase = "Constitution established"; key decisions logged)..genesis/hooks/commit-msg, .genesis/hooks/pre-commit, a CI workflow.Run /genesis-design overview, then begin your first feature with /genesis-brainstorm.
- "constitute"
- "write the constitution"
- "define the rules"
- "set project law"