diegosouzapw/awesome-omni-skill / skills/ai-agents/agent-ops-constitution
agent-ops-constitution
VerifiedCreate/update .agent/constitution.md. Use when commands/boundaries/constraints must be confirmed before baseline or code changes. Draft v0 from repo evidence, then interview user.
Constitution workflow (mandatory before baseline)
Goal
Make .agent/constitution.md baseline-ready by confirming:
- allowed/restricted/forbidden work areas
- single-line build/lint/test/format commands
- environment assumptions
- project-specific constraints
- issue-first workflow expectations
Pre-requisite: Context Map
Before starting constitution interview, ensure a context map exists:
- Check if
.agent/map.mdexists - If NO map exists:
β Invokeπ No context map found. Creating one first to inform constitution questions...agent-ops-context-mapto generate.agent/map.md - If map exists but is stale (>30 days old or significant changes detected):
π Context map may be outdated. Refresh? [Y]es / [N]o - Use the map to:
- Pre-populate candidate work areas
- Identify build/test tooling
- Understand project structure for interview questions
Procedure
- Ensure context map exists (see above)
- Run tool detection β invoke
agent-ops-toolsoraoc tools scan --save- Creates
.agent/tools.jsonwith available development tools - Identifies missing recommended tools based on detected project type
- Populates "Available tools" section in constitution
- Creates
- Inspect repo evidence (README, CI workflows, package/build files). Do not guess.
- Draft v0 constitution:
- every inferred item must cite its evidence ("CANDIDATE from ")
- anything without evidence is
TODO+UNCONFIRMED - use detected tools to suggest build/lint/test commands
- Interview the user:
- one question per TODO/UNCONFIRMED item
- ask both "what should it be?" and "why?"
- Update constitution until:
- build + test commands are CONFIRMED
- work boundaries are CONFIRMED
- Use
agent-ops-stateto update.agent/focus.md. - Invoke
agent-ops-tasksfor any setup work discovered.
Issue Discovery During Constitution
After constitution setup, invoke agent-ops-tasks discovery:
-
Collect setup items discovered:
- Missing configuration β
CHOREissue - Broken scripts β
BUGissue - Missing documentation β
DOCSissue - Security concerns noted β
SECissue - Environment issues β
CHOREissue
- Missing configuration β
-
Present to user:
π Constitution setup found {N} items to address: High: - [BUG] Build script references missing file - [CHORE] CI workflow needs updating Medium: - [DOCS] README is outdated Create issues for these? [A]ll / [S]elect / [N]one -
Workflow continues:
- Issues created before baseline capture
- Baseline can now proceed with known issues documented
Template
Start from constitution template.
Low Confidence Completeness Check (MANDATORY)
For LOW confidence work, constitution must be verified as complete before proceeding.
Required Sections Checklist
When confidence is LOW, verify constitution has ALL of these sections CONFIRMED (not TODO/UNCONFIRMED):
| Section | Required | Purpose |
|---|---|---|
| Project scope | β | What this project does |
| Work areas: allowed | β | Where changes are permitted |
| Work areas: restricted | β | Where caution is required |
| Work areas: forbidden | β | Where changes are never allowed |
| Build command | β | Single-line build command |
| Test command | β | Single-line test command |
| Lint command | β | Single-line lint command |
| Format command | βͺ Optional | Single-line format command |
| Coverage command | β for LOW | How to measure coverage |
| Environment assumptions | β | OS, runtime versions, dependencies |
| Tool detection | β | .agent/tools.json exists |
| Constraints | β | Project-specific limitations |
| Default confidence | β | LOW/NORMAL/HIGH |
Completeness Verification
Before LOW confidence work begins:
π― LOW CONFIDENCE CONSTITUTION CHECK
Checking constitution completeness for low confidence work...
| Section | Status |
|---------|--------|
| Project scope | β
CONFIRMED |
| Allowed areas | β
CONFIRMED |
| Restricted areas | β
CONFIRMED |
| Forbidden areas | β οΈ TODO |
| Build command | β
CONFIRMED |
| Test command | β
CONFIRMED |
| Lint command | β
CONFIRMED |
| Coverage command | β MISSING |
| Environment | β
CONFIRMED |
| Tool detection | β
.agent/tools.json exists |
| Constraints | β οΈ UNCONFIRMED |
Result: INCOMPLETE β 3 items need confirmation
β οΈ Cannot proceed with low confidence work until constitution is complete.
Starting interview to fill gaps...
Staleness Check
For LOW confidence, also check constitution age:
| Age | Action |
|---|---|
| < 7 days | Proceed |
| 7-30 days | Prompt: "Constitution is {N} days old. Review before proceeding?" |
| > 30 days | Require: "Constitution is stale. Re-interview before low confidence work." |
Gap-Filling Interview
If constitution is incomplete for LOW confidence:
- List missing/unconfirmed sections
- Invoke
agent-ops-interviewfor each gap - Update constitution with confirmed values
- Re-verify completeness
- Only proceed when all required sections are CONFIRMED
π Constitution gaps for low confidence work:
1. Forbidden work areas (currently: TODO)
2. Coverage command (currently: MISSING)
3. Constraints (currently: UNCONFIRMED)
Starting interview to fill these gaps...
Q1: What areas of the codebase should NEVER be modified?
(These will be marked as forbidden work areas)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |