Repository navigation
v1.4.0 — goal-first wizard, the planner, a Claude Code skill
Published to npm as @armoryworks/md-agent@1.4.0.
New
-
Goal first. The wizard's first question is now What should the orchestrator be reaching for? — the goal used to come after the seats.
-
Journal step in the wizard. Keep the project's configured repo, pick or create another, skip journals for this run only, or No, and don't ask again — ever. Once opted out, the panel footer shows
journals off (type "journals"); that keyword turns them back on during any run. -
The planner fork. Have Claude plan it: a high-tier model (
MD_AGENT_PLANNER_MODEL, defaultclaude-fable-5-1) reads the goal and the repo, with a brief on how md-agent works, and recommends the team — how many seats, each one's mandate, provider and tier, the verify command it found, isolation, escalation, a budget, rationale, and open questions. Launch it, save it asmd-agent.launch.json, or adjust it by hand with the wizard prefilled. -
A Claude Code skill.
md-agent skill installputsskills/md-agent/SKILL.mdinto~/.claude/skills, teaching Claude when a task is a team job, how to write a launch config, the console commands, and how to read a run. Ships in the package. -
Told twice. A notice after
npm install(where the package manager shows install-script output; npm hides and gates it by default), and a one-time offer the first time the home screen opens on a machine with Claude Code but no skill — install user-wide or for this project (skill install --project), not now, or don't ask again — followed by where the skill applies and how it's used.