Team profiles
Conclave separates structural invariants (you cannot do Scrum without them) from ceremonies (process gates the team chooses to commit to). The split is controlled by the team_profile field in conclave/config.md.
Always required (structural — never skippable)
These checks are enforced by every team profile. They are the minimum Scrum needs to function:
- Sprint Planning — without a goal and a locked story list, there is no sprint. Enforced by
/conclave-planningand the existence ofconclave/sprints/SPRINT-NNN/spec.md. - Acceptance criteria on every story — every story file must reference a non-empty
acceptance/AC-US-NNN.mdwith Gherkin scenarios. Stories without them fail the DoR. - A
disciplineassigned to every story (frontend | backend | qa | design | devops | multi) — assigned by the Tech Lead during/conclave-planning, checked by the same DoR gate. No default; a story with no discipline cannot enter a sprint. - QA verification of acceptance criteria — every
donestory carries a verification report appended to its acceptance file. Enforced by/conclave-qa. - Definition of Done compliance — the team-customized DoD checklist must be met for every story.
Skippable per profile
The team picks a profile in conclave/config.md. Conclave’s ceremony commands read it and silently skip the gates the profile turns off.
| Ceremony | Command | lean default | full-scrum default | Notes |
|---|---|---|---|---|
| Daily Standup | /conclave-standup | off | on | Logs to sprints/SPRINT-NNN/daily/. Planned, not yet shipped. |
| Backlog Grooming | /conclave-groom | off | on | When off, grooming happens inside /conclave-planning. |
| Peer / TL PR Review | /conclave-pr-review | off | on | Solo devs and small teams often skip this. |
| Sprint Review | /conclave-review | off | on | Required when there are stakeholders to demo to. Planned, not yet shipped. |
| Sprint Retrospective | /conclave-retro | off | on | First to get dropped under pressure; opt back in when stable. Planned, not yet shipped. |
Profile semantics
lean— only the structural invariants are enforced. For solo devs, very small teams (2–3), and internal tooling work.full-scrum— every ceremony is required. For cross-functional teams that ship to external stakeholders.custom— the team sets eachceremonies.*.requiredflag individually. Recorded ascustomso nobody assumes a preset.
Two gates cannot be turned off
sprint_planning and qa_verification cannot be flagged off — attempting to set required: false for either is rejected with a clear error. These are structural.
The PR-approval gate
When peer_pr_review.required: true, the Tech Lead (or designated approver) is the one who runs gh pr review --approve via /conclave-pr-review US-NNN. QA’s job ends at the verification report and a PR comment — never an approval. See the state machine for how the story transitions.
When the flag is false, QA’s pass is the merge signal. Story moves straight from review to done.
team_mode is separate from team_profile
team_mode (solo | team, set once by /conclave-init) controls the roster shape — a single person covering every discipline, or a real multi-person roster. team_profile controls which ceremonies are enforced. Solo projects are always lean (there’s no one to run a peer-review or standup with); a team can pick any of the three profiles independently of how many disciplines are actually staffed.
Changing your profile
Edit team_profile in conclave/config.md. To override a single ceremony without changing the whole profile, set team_profile: custom and edit individual ceremonies.*.required flags.
Profile changes take effect on the next slash-command run. The current sprint is unaffected — flags are read at command invocation time.