Mark a folder as a collection: adds brindley: 1 and the given details to its README.md front-matter, creating the folder and README if needed. Works on a folder that already holds numbered initiative files. The first collection in a repo also returns the agent-instructions snippet for AGENTS.md / CLAUDE.md.

Edit a collection README's details, including its status (active | done | abandoned).

Every collection with its details, counts by initiative status, and number ready.

List initiatives (whole root unless collection is given), optionally filtered.

Full detail of one initiative, including its dependency report (each dependency classified satisfied / blocking / external / missing), dependants, open questions and acceptance criteria.

Initiatives that are designed with nothing blocking — what an agent can pick up now — in suggested order (prerequisites first).

Dependency graph as an adjacency list plus Mermaid: a collection's active work, one initiative's neighbourhood, or a tag (theme) across collections.

Unresolved open questions, grouped by initiative.

The next unresolved blocking question in one initiative (after after, if given), with the count remaining. Drives the design-review conversation.

Every tag (theme) in use plus declared-but-unused ones, with descriptions and counts by status.

Check initiatives and collection structure: missing or unknown statuses, status vs folder vs body-prose disagreements, files not in their collection's status folder, duplicate numbers, dangling references, cycles, broken links (with where a moved file now lives), stale READMEs. Returns errors and warnings with file and line.

Lint project docs for history phrasing, design debate and links into initiatives (docs must describe only what the code is). Defaults to docs changed vs HEAD.

Create a new initiative. The number is coined automatically by scanning the working tree, other worktrees, branches and history. A folder path that isn't a collection yet is marked as one.

Edit an initiative's front-matter fields or H1, or replace a named body section. Cannot change its number or filename.

Change status, enforcing the lifecycle: designed needs no blocking open questions; in-progress needs ready; done goes through complete.

Add an open question. A blocking question moves a designed initiative back to draft. Use implementation=true for questions deliberately left to the implementer.

Resolve an open question. Default mode "remove": delete it and record the decision in record_in (default "Decisions", e.g. "Agreed direction"). Mode "tick": keep it as "- [x] … — answer".

Add or remove depends_on (blocking) and related (non-blocking) entries. Refuses unknown initiatives and cycles.

Mark an initiative done. docs_impact is required: the project doc paths updated in this change, or "none: ". Reports which initiatives became ready.

Rebuild the generated README blocks (tables + Mermaid). check=true only reports what is stale (for CI).