Commands

edikt commands are organized by namespace. Each namespace groups related commands.

Governance

Compile and maintain the rules the model follows.

Command	What it does
/edikt:gov:compile	Compile ADRs, invariants, and guidelines into the four rendered governance surfaces
/edikt:gov:review	Review governance doc language for enforceability and clarity
/edikt:gov:reextract	Re-run the sidecar-extractor over the corpus, with per-artifact accept/reject review — manual, opt-in only
/edikt:gov:advisory-review	Read-only judgment of whether compiled sidecars look stale — suggests, never writes
/edikt:gov:grade-compile	Score the current compile output for quality across coherence, conciseness, and four other dimensions
/edikt:gov:verify-diff	Judge whether a diff actually implements what a directive's verify: field claims
/edikt:gov:rules-update	Check for outdated rule packs and update them
/edikt:gov:sync	Translate linter configs into rule packs
/edikt:gov:score	Aggregate governance quality scoring
/edikt:gov:benchmark	Adversarial directive testing — opt-in install via ./bin/edikt install benchmark

SDLC Chain

The full cycle from requirements through verification.

Command	What it does
/edikt:sdlc:discovery	Structured uncertainty doc — Known, Unknown, Kill Criteria, Discovery Plan
/edikt:sdlc:prd	Write, continue, or transition a PRD (split markdown + YAML sidecar)
/edikt:sdlc:prd-review	Re-score a PRD against the rubric, report drift and broken refs
/edikt:sdlc:spec	Technical spec from a PRD, brainstorm, or free-text prompt
/edikt:sdlc:spec-review	Re-score a SPEC, verify FR coverage and AC pass-through
/edikt:sdlc:artifacts	Data model, contracts, migrations from an accepted spec
/edikt:sdlc:plan	Phased execution plan with pre-flight specialist review
/edikt:sdlc:code-review	Post-implementation specialist review — routes to domain agents
/edikt:sdlc:drift	Verify implementation matches spec, PRD, and ADRs
/edikt:sdlc:audit	Security audit — OWASP scan, secret detection, auth coverage
/edikt:sdlc:post-flight	Post-phase review pipeline — composes criteria verify, governance verifier, and specialist routing into one deduplicated report

Decisions

Capture and maintain architecture decisions and constraints.

Command	What it does
/edikt:adr:new	Capture an architecture decision record
/edikt:adr:compile	Compile ADRs into governance directives
/edikt:adr:enrich	Add a manual directive to an ADR or invariant sidecar without editing the immutable prose
/edikt:adr:review	Review ADR language quality
/edikt:invariant:new	Define a hard constraint that must never be violated
/edikt:invariant:compile	Compile invariants into governance directives
/edikt:invariant:review	Review invariant language quality
/edikt:guideline:new	Capture a team coding standard or convention
/edikt:guideline:compile	Compile guidelines into governance directives
/edikt:guideline:review	Review guideline language quality

Docs

Keep documentation current.

Command	What it does
/edikt:docs:review	Review documentation gaps for new routes, env vars, and services
/edikt:docs:intake	Scan scattered docs and organize into edikt structure

Daily Use

Everything you'll run session to session.

Command	What it does
/edikt:capture	Capture the current conversation into the right governance artifact
/edikt:context	Load project context, plans, ADRs, and product docs into current session
/edikt:status	Dashboard — plan progress, rules, what's next
/edikt:brainstorm	Brainstorm features, explore design space, converge toward PRD or spec
/edikt:session	End-of-session sweep — surface missed captures before context is lost
/edikt:doctor	Validate governance setup and report actionable warnings
/edikt:init	Detect project, infer architecture, install rules, agents, and context
/edikt:upgrade	Upgrade hooks, agents, and rules to the latest edikt version
/edikt:agents	List, install, and manage specialist agent templates
/edikt:mcp	Connect to Linear, GitHub, or Jira via MCP
/edikt:config	View and modify project configuration
/edikt:team (deprecated)	Merged into /edikt:init and /edikt:config

CLI reference

Surfaces that run as bin/edikt subcommands. Slash commands invoke most of these for you.

Command	What it does
edikt verify	Runner for the verify: shell commands declared in plan, gov, PRD, and SPEC sidecars
edikt migrate sidecars	One-shot migration of in-body directive blocks into co-located .edikt.yaml sidecars
edikt migrate to-v2	Rewrite v1 single-anchor sidecars into the v2 source_excerpts[] shape
/edikt:sidecar:approve	Review a pending behavioral verify proposal and promote, reject, or defer it

You don't need to remember them

After /edikt:init, the model responds to how you naturally talk. You don't need to think about which command to run — just say what you need.

"what's our status?" → /edikt:status "let's plan this" → /edikt:sdlc:plan "capture this decision" → /edikt:adr:new "any doc gaps?" → /edikt:docs:review "compile our governance" → /edikt:gov:compile

See the full list on the Cheatsheet.

The one command you run once

/edikt:init is the setup command. Everything else is day-to-day. After init, most interactions happen through natural language — the slash commands are there when you want explicit control.