mirkobozzetto/dotfiles/arsenal

Arsenal

One entry point, the shortest sufficient workflow. Read and apply selected skills; do not reproduce their procedures here. Work solo by default. Delegation requires explicit approval and the native contract in references/adapters/delegation.md; higher-priority solo rules win.

Start

Load steps/step-00-init.md. Keep the objective, scope, constraints, decisions, artifact paths, permissions and remaining questions in conversation. Reuse existing artifacts; no mandatory orchestration file or roadmap.

With no description, ask what outcome the user wants and whether they want advice, a document, or implementation. Use the runtime's native question form when available and permitted in the active mode; otherwise ask in plain text. Wait for the answer: a preselected option is not submitted consent.

With a description, inspect supplied context and relevant project instructions first. Ask only missing questions that could change the route, scope or safety. Use small adaptive batches, not a fixed questionnaire or complexity score. Existing answers and accepted artifacts are not another interview.

Choose the next useful step

Use the live installed skill inventory, including actual names and paths. These routes express intent, not a required sequence or proof of installation:

For another installed Arsenal skill, match its declared purpose to the missing result. Do not route back to Arsenal. A bug does not imply a GitHub issue; a large change does not imply a brief. A short clarification can resolve uncertainty without creating a document. For advice-only requests, recommend the shortest path and stop before execution.

Apply, then reassess

1. Name the selected skill and the concrete reason in one short update.
2. Resolve it from the live inventory and read its complete SKILL.md before

acting. Load only the linked references/scripts required by that skill. Resolve relative resources from that skill's directory, never Arsenal's. Plugins may be installed separately; do not guess sibling cache paths.

1. Pass the current objective, constraints, decisions, artifacts, authorizations

and unknowns into the step. Follow its actual instructions, not its summary.

1. When it returns a result, update that context and reassess what remains.

Continue only inside the user's original authorized outcome. Child skills do not launch one another; Arsenal owns the transition.

Missing or unreadable skill: state the gap. Do not claim to have used it or silently install it. Offer installation or a clearly labeled native fallback; stop if the missing capability is essential. No whole-config scan by default.

Standalone stop rules end that skill's step, not an already authorized broader Arsenal task. They never waive approval gates: a proposal remains Draft/Review until explicitly accepted; ship requires a ready brief or Accepted proposal when consuming one. Analysis is not permission to implement. Issue creation, closure, commits, pushes, installs and delegation retain their approval rules. If a selected skill explicitly forbids the required transition, stop and ask.

Stop when the outcome is delivered, approval is needed, the user stops, or a step cannot progress. No repeated unchanged route, redoing completed work, automatic reviewers, model retuning or ceremonial launch confirmations.

Prime runtime

Read references/adapters/prime.md before routing. Prime Normal/Plan mode and higher-priority instructions remain authoritative. This skill does not switch modes, models, or enable agents. When the native Prime Arsenal mode extension is enabled, it routes each request here through persistent system guidance; this does not relax Normal/Plan mode or any permission boundary. skill://, Task agents, Agent Hub, and the OMP ship runtime extension are unsupported. Approved delegation uses native RLM, not OMP agent files. Use filesystem-backed live skill discovery. The existing personal websearch skill is the research route.

Optional roadmap and configuration

For a requested roadmap or -r <slug>, read the existing roadmap if present and steps/step-03-plan.md. Preserve its schema and finished phases. Research only unresolved external questions through websearch when available. Render scripts/render.py only for --html or an explicit request. Mark ready when approved; a roadmap request alone does not authorize implementation.

-a permits explicit assumptions, not new permissions. Delegation flags never grant consent; persistent agent installation is not required. Do not install agents or additional workflow runtimes. Commits and publication remain opt-in and require explicit authorization.