workplan
/as:workplan
Before acting, read the host contract, this component's declaration (skill:workplan), and applicable workspace semantics. Load only the required modes from the shared catalog.
Use the host adapter and available native tools or ordinary task-specific code. Apply the receive-owned semantic document rules directly; no installed library, nested skill invocation, runner or executable reconstruction is required. Resolve context before durable work. Existing exact authorization persists; ask only for material missing information or missing permission.
Plan work, not a building/site/floor design. Route regulated/domain analysis to its proper owner. Inspect only enough evidence to make the plan reliable; distinguish facts from assumptions. Use applicable originals for external claims.
Quick straightforward tasks proceed within existing authorization. Meaningful multistep work that benefits from advance review receives a concise inline plan: intended result, concrete steps/outputs, relevant dependencies and checks. A durable plan is needed only when requested or useful for project continuity; do not create a file as an invocation tax. No rigid time threshold or compulsory Norma hop applies.
When parallel work benefits the task, state team size, roles, bounded assignments, concurrent work/dependencies, exclusive file ownership and integrator. Obtain only missing approval of that concrete work/team. Plan-only requests end at the plan. Prior exact approval survives resume. The main harness creates approved agents through actual exposed tools, verifies their identities and integrates results; workers return questions to the main loop. Unavailable/failed delegation is disclosed; only a material unapproved fallback needs further approval.
Durable plan
Resolve one project and read relevant PROJECT.md facts, registered decisions/source documents and the Agreement section when present. Compare scope advisory findings without creating commercial gates. Choose enough detail for the task; the plan template is a useful structure, not a required heading/word quota.
Each work unit names its result, owner, affected surface, inputs/dependencies and meaningful acceptance evidence. Include known risks/unknowns that change execution. Never inflate a small task with a committee, duplicate registry, blanket benchmark or mandatory deterministic validator.