Plan a feature or initiative through a computed route. The conductor\n(skills/_shared/delta-routing.md) derives the canon delta Δ, the gap profile\nΠ, the zone maturity M, and the risk flags R, then assembles the document\npackage; instruments produce the documents. Vision types are the primary\noutput. Reads cover all three categories: vision supplies intent and\nresumption targets, knowledge supplies constraints, experience supplies\nprecedent.
capability: one spec plus one planumbrella: prd, one spec per capability, one plansources mode)iso mode)research; \"Compare the alternatives for Y\" → research instrument, rnd — a named pending decision or candidate set selects rnd, otherwise researchplan research <topic> → research instrument; the instrument selects research (closed by scope coverage) or rnd (closed by a recommendation) by its closing testNot plan:
\n/archcore:document/archcore:document/archcore:document/archcore:reviewApply in this order:
\n| Signal | \nRoute | \n
|---|---|
| No arguments | \nGround per step 1; WHEN a draft on the branch carries a state block, resume it; otherwise ask one question — what to plan — with a recommendation drawn from the branch changes | \n
The first word is a mode (sdd, sources, iso, research) | \nThe mapped instrument per the mode map in skills/_shared/delta-routing.md, without route computation | \n
| Any other request | \nCompute Δ, Π, M, and R per the Derivation section of skills/_shared/delta-routing.md; its route table decides the package | \n
| A decision surfaces at a gate | \nRecord the adr through the decision instrument (skills/_shared/tracks/decision.md), then return to the open gate | \n
Research boundary: discovery feeding an mrd → brd → urd requirements\nchain belongs to acquisition. A request naming a pending decision or a set of\ncandidates to choose between produces rnd; any other investigation produces\nresearch. The path name research selects the instrument, not the type; the\nsame test applies. Neither rnd nor evidence is an entry on this command: an\nrnd comes only from that test, the spike, or the compatibility fallback, and a\nstandalone material is filed through /archcore:document research. A request proposing a specific\ntarget for team acceptance (\"should we switch to Y\", \"let's adopt Y\") belongs\nto /archcore:document's decision instrument.
Complete this step before asking the user any question. The research\nvocabulary probe (skills/_shared/research-compatibility.md) runs only under\nits own condition 1 — a request or type naming research or evidence, a\nroute engaging the research instrument, or a grounding result of either type.\nAdd research and evidence to the planning-moment filter below only when\nthe probe returns yes; a topic search without a type filter finds documents\nof both types on every engine. If this skill has no shell tool, use the probe\nresult the host supplied; if none was supplied, report needs-vocabulary-probe\nwith the helper path and stop before the first MCP call that names either type.
The actor-subject probe (skills/_shared/actor-subject-compatibility.md) runs\nunder its own condition 1 — a request naming scenario or journey, a route\nengaging the illustrate instrument, or a grounding result of either type — and\nadds both types to the filter below only when it returns yes. The same\nno-shell rule applies: report needs-vocabulary-probe and stop before the first\nMCP call that names either type.
.archcore/ with mcp__archcore__search_documents and mcp__archcore__list_documents across all three categories. Pass a planning-moment type filter — for example types=[\"idea\", \"prd\", \"plan\", \"spec\", \"rnd\", \"rfc\", \"adr\", \"rule\", \"task-type\", \"cpat\"] — and add \"scenario\", \"journey\" when the actor-subject probe returned yes — instead of relying on the global type ranking. Do not exclude a category from reads.implements, depends_on, or related relations, pull the linked documents one hop via mcp__archcore__list_relations and mcp__archcore__get_document.archcore:track state block, resume it per the resume rules in skills/_shared/gate-contract.md and skills/_shared/delta-routing.md instead of opening a new track..archcore/ exists but contains no documents, THEN proceed on outer-context grounding (git state and the codebase) and report that zero documents were found..archcore/ does not exist, THEN announce initialization in one line and call mcp__archcore__init_project without asking a question.Global sources. If a list_documents / search_documents result has\nglobal: true / read_only: true / source_kind: \"global\", load\nskills/_shared/globals.md. Also load it when a search_documents response's\ncoverage names a source other than \"local\" — even when results is empty:\nthe empty page is exactly where that file's retry ladder applies. Never modify\na global document and never target one with add_relation. Absent any global\nmatch, proceed as usual.
Compute the route per the Derivation section of\nskills/_shared/delta-routing.md and report the route announcement. WHEN the\nfirst word is a mode, execute its mapped instrument without route computation.\nA route name or a document type name as the first word is topic text; the\nconductor computes the route. Never ask the user to choose a route or a size label.
Interview mechanics, question form, and ceilings:\nskills/_shared/elicitation-contract.md. Auto mode draws every question from\nthe shared per-invocation ceiling; a mode entry raises per-gate\nbudgets to the maxima the track file declares.
Invoke each instrument the route names, in conductor order, per the instrument\nregistry and sequencing rules in skills/_shared/delta-routing.md. Run each\ninstrument's gates per skills/_shared/gate-contract.md: evaluate skip_when\nfirst at every gate, keep track state only in the archcore:track block\ninside the draft artifact (with the route: and delta: fields this command\nadds), persist each gate close in one mcp__archcore__update_document call,\nand follow the resume rules on re-entry. Gate bodies, per-gate questions, and\nrelation wiring live in the track files — do not restate them.
Before delegating research or evidence work, pass the current vocabulary probe\nresult and absolute plugin root to the assistant. If the assistant returns\nneeds-vocabulary-probe, run the helper and resume the same task.\nBefore delegating any other document write or relation work, pass the absolute\nplugin root to the assistant. The assistant reads\nskills/_shared/relation-authoring.md under that root.
WHEN the package produced a plan document:
@path/to/file notation, in one mcp__archcore__update_document call.## Declared Delta section per sequencing rule 9 of skills/_shared/delta-routing.md.WHEN the package produced no plan document (the null, decision, and\namendment routes, the acquisition and research paths), skip to Result — the\nexit gate or the announcement names the follow-ups.
Offer exactly two exits and let the user choose:
\n.archcore/; a later /archcore:plan invocation resumes any draft that still carries a state block.Report:
\nmcp__archcore__add_relation targets among existing documents, or a statement that none match.retires entries reported for closeout discharge, when any exist./archcore:plan to continue a package, /archcore:document decision to record a decision or /archcore:document code to document code touched during implementation, /archcore:review closeout to check the implementation against the recorded plan and reconcile the declared Δ.<track>.<stage>.