Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives

2026-07-05238

commit

govctl-org/govctl

Commit changes with govctl integration — check work item status, preserve durable notes only when needed, and run govctl check

2026-07-05238

detach

govctl-org/govctl

Remove govctl governance from a project. Archives artifacts, removes skills/agents, strips code references. Use when: (1) User wants to stop using govctl, (2) User mentions detach, opt-out, remove governance, or uninstall

2026-07-05238

guard-writer

govctl-org/govctl

Write well-structured Verification Guards. Use when: (1) Creating a new guard, (2) Editing guard check commands or patterns, (3) User mentions guard, verification, or check

2026-07-05238

migrate

govctl-org/govctl

Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield

2026-07-05238

rfc-writer

govctl-org/govctl

Write well-structured RFCs with normative clauses. Use when: (1) Creating a new RFC, (2) Adding or editing RFC clauses, (3) User mentions RFC, specification, or normative requirements

2026-07-05238

name	init
description	Set up govctl in the current project. Installs the binary if missing, initializes governance structure.
allowed-tools	Read, Write, Edit, Bash, Glob, Grep, TodoWrite
argument-hint	[optional setup scope]

/init - Set Up Govctl

Set up govctl in the current project.

Outputs: Initialized governance structure, verified local setup, and a recommended next workflow.

Critical Rules

This is a setup workflow, not an implementation workflow. Do not create work items or change product code here.
Ask permission before installing govctl with cargo install govctl.
Prefer local govctl if it is already available. When working in the govctl repo itself, prefer cargo run --quiet -- before installing a global binary.
Never edit governed files directly. Use govctl init.
If setup succeeds and the user wants it recorded, hand off to /commit rather than embedding raw VCS commands here.

Steps

1. Check for govctl binary

govctl --version

If you are working in the govctl repository itself, prefer:

cargo run --quiet -- --version

If that works, use cargo run --quiet -- <subcommand> for the rest of this workflow instead of installing a global binary.

If no usable local invocation exists, ask permission, then install it:

cargo install govctl

If cargo is also missing, tell the user to install Rust first: https://rustup.rs

2. Initialize the project

If gov/config.toml does not exist:

govctl init

If it already exists, skip — the project is already initialized.

3. Optional: Install project-local agent assets

If the user wants the bundled skills and reviewer agents copied into the project or agent config directory, run:

govctl init-skills

Use govctl init-skills --format codex for Codex agent role output, and --dir <path> when the assets should be written outside the project directory.

4. Verify

govctl status

Show the user what was created and confirm everything is working.

Next Steps

Use /discuss for design work
Use /spec for governance-only artifact maintenance
Use /gov for implementation-bearing work
Use /quick for trivial non-behavioral cleanup