Dev-Discipline Skills

MUR ships a curated engineering-discipline pack — seventeen built-in skills that carry a professional coding method (design before code, test-first, root-cause debugging, evidence before "done") into every AI tool MUR feeds. They are internalized from the MIT-licensed obra/superpowers and mattpocock/skills, merged into one canon per topic and adapted to MUR's runtime.

mur skill list                    # dev-discipline skills appear as mur-*
mur skill show mur-tdd            # load a skill's full method on demand
mur sync                          # install/refresh built-ins into your AI tools

One hub, sixteen leaves

A single hub routes; sixteen on-demand leaves carry the method:

mur-dev (hub) · mur-grilling · mur-brainstorm · mur-domain-modeling · mur-writing-plans · mur-tickets · mur-executing-plans · mur-delegate-dev · mur-worktree · mur-tdd · mur-debugging · mur-code-review · mur-receiving-review · mur-verification · mur-finishing-branch · mur-merge-conflicts · mur-skill-authoring

The hub is a routing map: "building something new → mur-brainstorm; fixing anything → mur-debugging; about to claim done → mur-verification." When a task matches, the AI loads that leaf with mur skill show <name> and follows it.

Zero cost until used

Only the mur-dev hub appears in the session-start learning index. The sixteen leaves are on_demand — excluded from the index and from abstract injection, reachable via the hub's routing, keyword triggers, search, and mur skill show. Nothing but the one-line hub is paid for until a leaf is actually needed.

Superpowers-aware

If you already run the superpowers plugin, MUR detects it and hides the mur-dev hub from the CLI learning index so the two never double up. Control it in ~/.mur/config.yaml:

skills:
  dev_discipline_index: auto   # auto (default) | always | never

• auto — suppress the hub when a superpowers plugin install is detected.
• always — list the hub even when superpowers is installed.
• never — never list the hub on the CLI surface.

Runtime injection for MUR agents is never affected by this setting — it governs only the AI-tool learning index.

Never-shadow

A dev-discipline built-in never overwrites a skill you authored yourself. If a skill named mur-tdd (or any of the seventeen) already exists on disk from a non-MUR publisher, mur sync skips it and leaves your version untouched. Delivery is free either way: the YAMLs ship with MUR and inject store-wide, so there is nothing to download.

Related

• Capabilities — install a whole tool bundle onto an agent in one command.
• mur skill doctor — health-check and de-pin an agent's skills.
• mur skill scope <name> — set a skill's visibility scope (user / project / fleet).