Plan an agentic-os install
plan_installCompose one or more role presets into an ordered file manifest for install scaffolding. Returns the plan without writing any files. Use after listing available presets.
Instructions
Compose one or more agentic-os role presets into an ordered manifest of the files an install should scaffold, each with a uri to read its template from. Use it after list_presets to turn chosen roles into concrete steps. Composition is additive: roles are unioned, the strictest HITL level wins, and every orchestration style in the union is installed. This returns a plan and writes nothing — no file is created, and the target repository is neither read nor touched, so the plan is not validated against what may already be installed (use run_doctor for that). You perform every write yourself, so the user can review each one. Read-only and idempotent.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| roles | Yes | Role preset names to compose, e.g. ["developer","qa"]. At least one is required. Get the valid names from list_presets — an unrecognized name is an error, not a silent skip, and no partial plan is returned. Composition is additive: pass every role the repo needs in one call rather than planning each separately. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | The files to scaffold, ordered by template id. This is the plan's payload: you read each source_uri and perform the writes yourself. Any template with no file in the bundle is reported in follow_ups and omitted here rather than emitted as a broken entry. | |
| roles | Yes | The roles this plan composes, echoed back in the order given (which determines orchestration_default). | |
| follow_ups | Yes | Problems and decisions this plan could not settle — a missing template, an undeterminable HITL level or orchestration default. Surface these rather than installing past them: an empty array means the plan is complete as returned. | |
| sdlc_skills | Yes | agentic-sdlc pipeline skills the composed roles enable. Empty if no chosen role takes part in the SDLC flow. | |
| hitl_default | Yes | The human-in-the-loop level to install: the strictest among the chosen roles ("strict" > "gated-autonomous" > "autonomous"). Empty if no role declared a recognized level, in which case follow_ups says so. | |
| generated_candidates | Yes | Stack-specific agent contracts this role set *could* generate — candidates, not commitments. Generating one requires facts about the target stack that this server does not have, so filter them against the actual repository before writing any. | |
| orchestration_default | Yes | The style to pre-select as active: the first listed role's default, except that a "strict" hitl_default forces "dispatcher". Empty if undeterminable, in which case follow_ups says to set it explicitly. | |
| orchestration_installed | Yes | Every orchestration style to install — the union across roles, not a single choice, because a mixed team needs each one present. |