Skip to Content
Commands/conclave-init

/conclave-init

One-time project setup wizard. Run it once per repository, before /conclave-planning.

/conclave-init

This command creates the conclave/ workspace and writes the config.md that every other Conclave command reads. There are no AI agents — it is a wizard that reads your project and writes configuration. Story and sprint generation happens in /conclave-planning.

What it does

Step 0 — Guard idempotency

If conclave/config.md already exists, the command stops immediately:

conclave/ is already initialized. Edit conclave/config.md directly to change settings. Run /conclave-planning to generate stories and plan a sprint.”

If the current directory is not a git repo, it asks whether to run git init.

Step 1 — Detect the stack

Before asking anything, the command scans up to 3 directory levels deep for signal files:

Signal fileLikely stack
package.json + next.config.*Next.js
package.json (no framework config)Node.js
pubspec.yamlFlutter / Dart
go.modGo
Cargo.tomlRust
requirements.txt / pyproject.tomlPython
build.gradle / pom.xmlAndroid / Java / Kotlin
GemfileRuby on Rails
mix.exsElixir
composer.jsonPHP

This gives you something concrete to confirm rather than a blank field.

Step 2 — Collect project info

One AskUserQuestion call collects:

  1. Project name — used as the title in all generated artifacts.
  2. Story ID prefix — default US. Stories will be named <PREFIX>-001, <PREFIX>-002, etc. Examples: US, TASK, FEAT, or a project abbreviation.
  3. Project language — ISO 639-1 code. All Conclave-generated markdown (stories, acceptance criteria, reports) will be written in this language. Default: es.
  4. Launch date — ISO date (YYYY-MM-DD), or TBD.
  5. Team modeteam (multi-person) or solo (forces lean profile).
  6. Team profile (team mode only) — lean (only Sprint Planning + QA Verification enforced), full-scrum (all ceremonies required), or custom (configure each flag manually in config.md).

Step 3 — Confirm or override the detected stack

A second AskUserQuestion presents the detected stack. You can confirm the values or correct them — language, framework, datastore, infrastructure.

Step 4 — Find the product planning document

The product planning document is the source of truth for /conclave-planning to generate stories and sprints.

  1. The command searches the repo for files containing keywords like sprint, backlog, user stor, mvp, milestone.
  2. It also checks common paths: docs/mvp.md, docs/project.md, mvp.md, project.md, docs/product.md, PRODUCT.md.
  3. If candidates are found, you pick one (or say “None of these”).
  4. If nothing is found, you choose: paste the content now, provide a path, or create it later.

If you defer ("I'll create it later"), the workspace is created but /conclave-planning will refuse to run until you set product_doc_path in config.md.

Suggested format if you’re creating the document:

# My Project — Product Plan ## Vision One-paragraph description of the product. ## MVP Scope What the MVP includes and excludes. ## Sprint 1 ### Goal One sentence. ### Features - Feature 1: description - Feature 2: description

What it creates

conclave/ ├── README.md ├── config.md # story_prefix, product_doc_path, stack, team config ├── team/ │ ├── roster.md │ ├── ceremonies.md │ └── testing-environments.md ├── product/ │ ├── definition-of-ready.md │ └── definition-of-done.md ├── context/ │ ├── claude-md.snapshot.md │ ├── skills.inventory.md │ └── rules.inventory.md ├── sprints/ ├── runs/ └── report/ .github/ ├── ISSUE_TEMPLATE/bug_report.md # only if it doesn't already exist └── PULL_REQUEST_TEMPLATE.md # only if it doesn't already exist

product/backlog.md and product/architecture.md are created by /conclave-planning (Phase A), not here.

What it does NOT do

  • Does not commit — review the seed files before committing.
  • Does not touch files outside conclave/ or .github/ (and only if those files don’t already exist).
  • Does not run any AI agent.

After it runs

Review and customize:

  • conclave/team/roster.md — add real names/handles.
  • conclave/team/ceremonies.md — adjust cadence to your team.
  • conclave/product/definition-of-ready.md / definition-of-done.md — customize checklists.

Then commit:

git add conclave/ .github/ git commit -m "conclave: bootstrap Scrum workspace"

And run /conclave-planning to generate stories and plan the first sprint.

Idempotency

Re-running /conclave-init on a workspace that already has conclave/config.md is refused. To change settings, edit conclave/config.md directly.

Last updated on