atelier

Add a new project-specific agent mid-project, with Chief AI Officer drafting the definition and justification, and the user approving. Use when project scope expands (new domain emerges, a parallel track is needed, or critical expertise is missing) during Phase 2.

Add a new MCP server to the project mid-project. Wraps the capability-management procedure — external MCP search, ADR draft, .mcp.json update, user install instructions, and capability-log entry. User approval is mandatory regardless of involvement level. Use when an authorized agent identifies a missing external integration.

Add a new project-specific skill mid-project. Wraps the capability-extension procedure — reuse audit, skill-creator invocation, capability-log entry, user approval, and reload reminder. Use when an authorized agent identifies a missing helper-skill capability during Phase 1 STEP 2/3 or anywhere in Phase 2.

Re-activate a Phase 1 agent from STANDBY because a requirement, design, roadmap, team-composition, or documentation drift has been detected. The user invokes this with the target agent name and a brief reason. Use when Phase 2 cannot proceed without a Phase 1 decision.

Produce a production hotfix — branch from main, fix, change-review back into main, then merge the fix back into develop. Use when a bug in the released version (main) must be patched without waiting for the normal develop→main cycle.

Initialize a new project with a structured, multi-agent workflow — discovery interview, operating preferences, technical design, agent team formation, roadmap construction, documentation consolidation, and a final user approval gate. Use when the user starts a fresh project and wants a rigorous setup before any code is written.

Render the active milestone's tasks as a kanban board grouped by lane (backlog / todo / in-progress / in-review / done). Forge-aware — GitHub mode shows the Projects v2 URL alongside ASCII fallback; other forges render ASCII only. WIP overflow is flagged but not blocked. Use whenever the user asks "what's where" or wants a quick board view.

Run a milestone completion checkpoint — summarize what was delivered against the milestone's success criteria, surface risks and debt, and either obtain user approval to proceed to the next milestone or route back for remediation. Required when user involvement level is "Milestone Checkpoints" or stricter.

Decompose an active milestone into PR-sized tasks via multi-agent discussion (PM proposes, Tech Lead challenges, CAIO conditional). Use at the start of every milestone in Phase 2 — it's the bridge between the high-level roadmap and per-PR execution. Produces task files with lane/epic/depends_on/acceptance frontmatter and (in GitHub mode) mirrored Issues.

Cut a release — promote develop to main, generate changelog, tag a semver version, and publish release notes. Use when Project Manager marks a milestone complete and the user approves.

Show a dashboard of the current project state — active milestone, in-progress tasks, open PRs with review status, recent risks, and escalation signals. Use whenever the user asks "where are we?", "what's open?", or "what's blocked?". Pass `--json` for machine-readable output (schema at docs/process/status-schema.md).