@ionivetech/mugiwara 0.5.5 → 0.6.0

package/docs/concepts/skills.md

@@ -1,55 +0,0 @@
-# The Techniques — 26 Skills
-
-Each skill is a portable markdown playbook — the "how to" the crew follows when
-it embodies a role.
-
-## Core pipeline
-
-| Skill | Teaches |
-|-------|---------|
-| `mugiwara-workflow` | Harness entry: inline execution, gateway triage, wave pipeline, workspace, blocker protocol, cleanup |
-| `mugiwara-orchestration` | Captain: 5-way classifier, check-ins, work splitting, decision log, closure |
-| `mugiwara-brainstorm` | Critical sparring: interrogate, research facts, cut over-engineering, recommend |
-| `mugiwara-planning` | Interview-first, full-context scan, wave plans with parallel/sequential markers |
-| `mugiwara-execution` | Todo list, sequential inline + parallel worker batches, 6-field delegation, one commit per task |
-| `mugiwara-checkpoint` | Verify-everything audit — deduped re-runs scoped to wave diff; failure rows to blocker ledger |
-| `mugiwara-quality` | Discover project tooling; formatter, linter, unit tests under consent matrix |
-| `mugiwara-gates` | Coverage ≥90% new / ≥80% modified, build, Definition of Done |
-| `mugiwara-review` | Doubt-driven review: breaking-change map, five-axis, severity-tagged findings |
-| `mugiwara-security` | STRIDE-first security review, OWASP Top 10, authn/authz, secrets, untrusted-data |
-| `mugiwara-healing` | Reads the ledger, Stop-the-Line + Prove-It root-cause fixes, rollback prep |
-
-## Mission control
-
-| Skill | Teaches |
-|-------|---------|
-| `mugiwara-git` | Atomic commits, save-points, multi-commit splitting, bisect/blame debugging |
-| `mugiwara-testcases` | User-test intake: immutable-gold rule, declarative-AC routing, consent, failure adjudication |
-| `mugiwara-pr` | Terminal: push + verdict file with ready PR summary; never creates a PR |
-| `mugiwara-ship` | GO/NO-GO ship gate: pre-launch checklist, feature flags, rollback plan |
-| `mugiwara-sunset` | Sunset & migration: keep-or-retire gate, cutover playbooks, safe schema changes |
-| `mugiwara-resume` | Session resume: rebuild state from `.mugiwara/state.json`; never restart |
-| `mugiwara-lessons` | Cross-mission memory: actionable lessons ledger, read at triage, written at closure |
-
-## Engineering practice
-
-| Skill | Teaches |
-|-------|---------|
-| `using-mugiwara` | Front-door router — explains the crew, classifies missions, routes to specialist |
-| `mugiwara-root-cause` | 4-phase: reproduce → localize → reduce → fix + guard; stop-the-line |
-| `mugiwara-contract-first` | Contract-first design, error semantics, boundary validation, backward compatibility |
-| `mugiwara-claim-audit` | Adversarial verification: CLAIM → EXTRACT → DOUBT → RECONCILE → STOP |
-| `mugiwara-context-budget` | Token/context management: feed selectively, trust-sort sources, the window is a budget |
-
-## Domain
-
-| Skill | Teaches |
-|-------|---------|
-| `mugiwara-frontend` | Anti-slop frontend: audit-first redesigns, design-system extraction, WCAG 2.1 AA |
-| `mugiwara-backend` | Backend/server code: repo standards first, source-backed code, data integrity |
-| `mugiwara-agent-security` | Agent layer: prompt injection, memory poisoning, excessive agency, MCP trust, sandboxing |
-
-## Anatomy
-
-Every skill is a `SKILL.md` with frontmatter + playbook body. See
-[skill-anatomy.md](../reference/skill-anatomy.md).

package/docs/concepts/workflow.md

@@ -1,89 +0,0 @@
-# The Wave Pipeline
-
-A mission runs as ten waves (plus one optional adversarial pass). Each wave is
-owned by one crew member and runs **inline** in the main conversation.
-
-| Wave | Owner | Skill | Output |
-|------|-------|-------|--------|
-| 0 Triage | Luffy | `mugiwara-orchestration` | 5-way route decision + reason |
-| 1 Brainstorm | Usopp | `mugiwara-brainstorm` | refined direction, options, recommendation |
-| 2 Planning | Nami | `mugiwara-planning` | plan doc: waves, tasks, acceptance criteria |
-| 3 Execution | Zoro | `mugiwara-execution` | implemented tasks with evidence |
-| 4 Checkpoint | Chopper | `mugiwara-checkpoint` | audit report + failure ledger |
-| 4.5 Adversarial | Skeptic | `mugiwara-dynamic-workflow` | findings report (optional) |
-| 5 Quality | Sanji | `mugiwara-quality` | formatter/linter/test results |
-| 6 Gates | Franky | `mugiwara-gates` | coverage + build verdict |
-| 7 Review | Robin ∥ Jinbe | `mugiwara-review` + `mugiwara-security` | severity-tagged findings |
-| 8 Healing | Brook | `mugiwara-healing` | fixes; loops back to Wave 4, max 3 cycles |
-| 9 Closure | Luffy | `mugiwara-orchestration` | closure report + push + PR verdict handed to you |
-
-## Wave 0 — Triage
-
-Every mission starts at the Luffy gateway, which classifies the request 5 ways
-and sizes it to a **lane**:
-
-| Class | Signal | Route |
-|-------|--------|-------|
-| Trivial | one obvious small change, no ambiguity | Lane 0/1 — Wave 2 directly |
-| Explicit | clear requirements, written spec exists | Wave 2 directly |
-| Exploratory | needs direction, options, research | Wave 1 first |
-| Open-ended | broad goal, undefined scope | Wave 1 first |
-| Ambiguous | requirements, APIs, scope unclear | Wave 1 first |
-
-A clear-work route straight to Wave 2 still writes a short **spec bridge** to
-`.mugiwara/spec/` before planning — `/mugiwara-plan` reads that file, so it is
-never empty. The decision + reason is logged in `.mugiwara/logs/`. Risk
-(money/security/data/public API) always triggers the full pipeline and the
-lane escalates automatically when the work outgrows the estimate — it never
-auto-drops. See [lanes.md](lanes.md).
-
-## Wave 4 — Checkpoint (Chopper)
-
-The verify-everything gate. After execution, Chopper re-runs every acceptance
-criterion — but efficiently:
-
-- **Deduped**: each unique check command runs once per wave, scoped to the
-  files this wave changed. No running `npm test` once per task.
-- **Scoped by diff**: `git diff --name-only <wave-base>..HEAD` decides what
-  actually needs re-verification.
-- **Commit hygiene**: one `git log --stat` pass, not per-commit.
-- Failures land in the blocker ledger `.mugiwara/issues/` with honest
-  code-vs-env classification.
-
-## Wave 7 — Review
-
-Robin (doubt-driven review) and Jinbe (security) run in parallel. Robin maps
-breaking changes to callers before reading the diff; Jinbe runs STRIDE + OWASP.
-Findings are severity-tagged with path:line.
-
-## Wave 8 — Healing
-
-Brook reads the blocker ledger and fixes root causes, proving each fix by
-re-running the failed check. The loop returns to Wave 4 — max 3 cycles, then
-escalation to you.
-
-## Wave 9 — Closure
-
-Luffy runs the ship gate, writes the closure report, deletes superseded
-intermediate files, then the terminal step in every mode: **save-point commit →
-push the mission branch → write the PR verdict file → hand branch + verdict to
-you**, who opens the PR. The crew never creates a PR, merges, or deploys.
-
-## The two rules that hold it together
-
-1. **Evidence over claims.** No wave passes on assertion — the owning agent
-   runs the checks and shows output. "Subagents lie. No evidence = not
-   complete." A skipped wave is recorded in the decision log, never silent.
-2. **The plan is the source of truth.** From Wave 2 on, the plan doc in
-   `.mugiwara/plans/` holds the clean execution plan; the decision log holds the
-   who-and-why trace.
-
-**Every skill has a skip gate.** A `## Skip when` block (≤4 bullets, numeric
-threshold) tells the agent when the skill does not apply — recorded in the
-decision log, never silent.
-
-## Blocker protocol
-
-Any agent that hits a blocker appends a row
-(`wave | task | symptom | attempted | help-needed`) to the ledger and escalates.
-Never a silent workaround. Brook heals what the ledger lists.

package/docs/getting-started.md

@@ -1,158 +0,0 @@
-# Getting Started
-
-Install the crew, run your first mission, and understand what you're looking at
-in the chat.
-
-## 1. Install
-
-Pick your harness — every major one is supported. The two easiest:
-
-**opencode** — add the plugin to `opencode.json`:
-
-```json
-{ "plugin": ["@ionivetech/mugiwara"] }
-```
-
-**Claude Code** — via the marketplace:
-
-```bash
-/plugin marketplace add ionivetech/mugiwara
-/plugin install mugiwara
-```
-
-| Harness | Install command |
-|---------|----------------|
-| Claude Code | `/plugin marketplace add ionivetech/mugiwara` then `/plugin install mugiwara` |
-| opencode | `{ "plugin": ["@ionivetech/mugiwara"] }` in `opencode.json` |
-| GitHub Copilot | `copilot plugin marketplace add ionivetech/mugiwara` then `copilot plugin install mugiwara` |
-| Gemini CLI | `gemini extensions install https://github.com/ionivetech/mugiwara` |
-| Codex | `codex plugin marketplace add ionivetech/mugiwara` then `codex plugin add mugiwara@mugiwara` |
-| Cursor | `/add-plugin mugiwara` |
-| Kimi Code | `/plugins install https://github.com/ionivetech/mugiwara` |
-| pi | `pi install git:github.com/ionivetech/mugiwara` |
-| Windsurf, Cline, Kilo, Antigravity | `npx @ionivetech/mugiwara@latest --project . --target <id> --yes` |
-
-Or the CLI for any target:
-
-```bash
-npx @ionivetech/mugiwara@latest --project ./my-app --target all --yes
-```
-
-Requires **Node.js >= 20.11**. Bun is optional (build-from-source only).
-
-## 2. Start a mission
-
-The workflow **auto-activates** at session start. The crew announces itself,
-then give any non-trivial request.
-
-### Small: lane 0–1
-
-```
-> fix the date formatting bug in src/utils/format.ts
-```
-
-Luffy routes it to **Lane 1** (Lean). Zoro reproduces and fixes, Sanji runs
-format + lint + tests. Two waves, visible as compact checkpoint reports. No
-nine-wave ceremony for a one-file bug.
-
-That's lane sizing: the process scales to the work. A typo (Lane 0) runs zero
-waves — the fix happens directly.
-
-### Medium: lane 2
-
-```
-> add a search bar to the products page
-```
-
-Touches frontend + API. Luffy routes to **Lane 2** (Standard). Nami plans 1
-wave with 3-5 tasks, Zoro executes test-first, Chopper audits every criterion,
-Sanji and Franky gate, Robin and Jinbe review.
-
-### Large: lane 3
-
-```
-> add role-based access control to the API
-```
-
-Touches auth — Luffy routes to **Lane 3** (Full). All 9 waves run. Nami plans
-the migration, Zoro executes, Chopper audits, Sanji tests, Franky gates, Robin
-reviews the diff with a breaking-change map, Jinbe runs STRIDE + OWASP, Brook
-heals any failures (max 3 cycles), Luffy closes with a mission report + push +
-ready PR summary.
-
-```
-  Wave 0  Luffy   triage → route: full pipe (auth/ touched)
-  Wave 2  Nami    plan   → .mugiwara/plans/2026-08-10-rbac.md (2 waves, 5 tasks)
-  Wave 3  Zoro    execute→ 5 tasks, evidence per task
-  Wave 4  Chopper audit  → PASS: all criteria met, commit hygiene clean
-  Wave 5  Sanji   quality → PASS: lint 0, 312 tests green
-  Wave 6  Franky  gates  → PASS: new 94%, modified 87%, build green
-  Wave 7  Robin   review → 2 minor findings (batched)
-  Wave 7  Jinbe   security→ PASS: STRIDE clean, 0 high
-  Wave 9  Luffy   closure→ mission report + push + ready PR summary
-```
-
-The crew runs **inline** in your main conversation — every wave reports as a
-compact checkpoint. Subagents only for parallel task batches.
-
-Prefer to drive stages yourself? Every stage has a slash command:
-`/mugiwara-plan`, `/mugiwara-execute`, `/mugiwara-review`,
-`/mugiwara-security`, `/mugiwara-heal`, `/mugiwara-ship`. Jump into any stage.
-
-## 3. What you do during a mission
-
-Almost nothing in `guided` mode:
-
-- Answer Nami's clarifying questions (one batched round before planning).
-- Give the plan an explicit GO when presented.
-- Review Brook's rollback note if a risky fix is proposed.
-- In every mode, **open the PR at the end** — the crew pushes the branch and
-  hands you a verdict file with a ready PR summary. The crew never creates a
-  PR, merges, or deploys.
-
-Switch to `semi` or `auto` if you want the crew to self-manage branch, commits,
-and ambiguities. See [modes](concepts/modes.md).
-
-## 4. The `.mugiwara/` workspace
-
-Every mission writes to `.mugiwara/` at the repo root:
-
-```
-.mugiwara/
-├── config          # mode, branch, commit, base, coverage thresholds
-├── state.json      # computed at every wave boundary by scripts/savepoint.sh
-├── spec/           # brainstorm output
-├── plans/          # clean execution plan (source of truth from Wave 2)
-├── results/        # audit, quality, gate, closure reports + evidence logs
-├── reports/        # human-readable mission reports
-├── review/         # review + security findings
-├── issues/         # blocker ledger
-├── refs/           # full skill/agent bodies for glob-loading harnesses
-└── logs/           # decision log + cross-mission lessons
-```
-
-**Savepoint** runs at every wave boundary — `state.json` carries lane, wave,
-files, blockers, heal cycle, and token budget. Resume reads one file instead of
-six. See [audit-trail.md](concepts/audit-trail.md) for the full artifact map.
-
-## 5. Configuration
-
-`.mugiwara/config` (project) overrides `~/.mugiwara/config` (global):
-
-| Key | Default | What it controls |
-|-----|---------|-----------------|
-| `mode` | guided | Autonomy: guided/semi/auto |
-| `branch` | `feature/{type}-{issue}-{slug}` | Branch naming pattern |
-| `commit` | conventional | Commit style: conventional/gitmoji/plain |
-| `base` | main | PR target branch |
-| `coverage_new` | 90 | Coverage % for new files |
-| `coverage_modified` | 80 | Coverage % for modified files |
-
-## 6. Next steps
-
-- Meet the [crew](concepts/agents.md) — 14 agents with permission boundaries.
-- Browse the [skills](concepts/skills.md) — 26 skills with the 3-layer disclosure model.
-- Understand the [lanes](concepts/lanes.md) — how work is sized before it runs.
-- Set your [mode](concepts/modes.md) — guided/semi/auto.
-- Read the [audit trail](concepts/audit-trail.md) — every artifact and how to review it.
-- See the [compliance matrix](reference/compliance-matrix.md) — rule compliance per model.

package/docs/index.md

@@ -1,56 +0,0 @@
-# Mugiwara Docs
-
-The Straw Hat crew of AI agents and skills. These docs cover what the crew is,
-how to adopt it, and how each harness installs it. The crew is markdown plus a
-small Node CLI (`mugiwara`) — no daemons, nothing to host. It ships **15
-agents** and **32 skills**, and the workflow **auto-activates** at session
-start — a non-trivial request runs the pipeline by itself, with
-`/using-mugiwara` as an optional explicit router. Work is **sized to a lane**
-before it runs: small fixes skip the pipeline, sensitive changes run the full
-nine waves, and every wave passes only on **evidence**, never on a spoken
-claim.
-
-## Start here
-
-| Doc | What it covers |
-|-----|----------------|
-| [Getting started](getting-started.md) | Install, first mission, what you see in the chat |
-| [Adoption guide](reference/adoption-guide.md) | Pick the harness, pick the mode, fit the crew to your workflow |
-| [Modes](concepts/modes.md) | guided / semi / auto — the autonomy levels, what each asks you |
-| [Config](concepts/config.md) | Full reference for `.mugiwara/config` keys and commit styles |
-| [Auto-PR](concepts/pr-summary.md) | What the crew hands off at closure: push + a ready-to-paste PR summary (it never creates a PR) |
-| [The crew](concepts/agents.md) | All 14 agents and when to summon each |
-| [The techniques](concepts/skills.md) | All 32 skills and what each enforces |
-| [The wave pipeline](concepts/workflow.md) | How a mission flows Wave 0 → Wave 9 |
-| [Execution model](concepts/execution-model.md) | Inline-by-default: why the crew runs in your main conversation |
-| [Lanes & sizing](concepts/lanes.md) | How Luffy sizes work at triage: Lane 0–4, escalation, budget |
-| [Enforcement](reference/enforcement.md) | Skip gates, evidence over claims, and capability tiers |
-| [Git discipline](concepts/git-strategy.md) | Commits, branches, save-points — and why the executor commits |
-
-## Install by harness
-
-| Harness | Guide |
-|---------|-------|
-| Claude Code | [install/claude.md](install/claude.md) |
-| opencode | [install/opencode.md](install/opencode.md) |
-| GitHub Copilot | [install/copilot.md](install/copilot.md) |
-| Gemini CLI | [install/gemini.md](install/gemini.md) |
-| Codex | [install/codex.md](install/codex.md) |
-| Cursor | [install/cursor.md](install/cursor.md) |
-| Windsurf | [install/cli.md](install/cli.md) |
-| Cline / Kilo / Antigravity | [install/cli.md](install/cli.md) |
-
-## Reference
-
-| Doc | What it covers |
-|-----|----------------|
-| [Skill anatomy](reference/skill-anatomy.md) | How a mugiwara skill file is structured |
-| [Agent anatomy](reference/agent-anatomy.md) | How a mugiwara agent file is structured |
-| [Troubleshooting](troubleshooting.md) | Common problems and how to fix them |
-| [Developer onboarding](reference/developer-onboarding.md) | Repo layout, validation, tests, contributing |
-
-## Resources
-
-- GitHub: <https://github.com/ionivetech/mugiwara>
-- npm: <https://www.npmjs.com/package/@ionivetech/mugiwara>
-- License: MIT

package/docs/install/antigravity.md

@@ -1,45 +0,0 @@
-# Antigravity Install
-
-Mugiwara installs as an Antigravity plugin from this repo.
-
-## Prerequisites
-
-- [Antigravity](https://antigravity.google) installed
-
-## Install
-
-```bash
-agy plugin install https://github.com/ionivetech/mugiwara
-```
-
-## How it works
-
-Antigravity reads `.agents/plugins/marketplace.json` and installs the plugin
-from the repo root. Skills and agents are auto-discovered.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-Reinstall with the same command:
-
-```bash
-agy plugin install https://github.com/ionivetech/mugiwara
-```
-
-## Uninstall
-
-```bash
-agy plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [config.md](../concepts/config.md).

package/docs/install/claude.md

@@ -1,77 +0,0 @@
-# Claude Code Install
-
-Mugiwara is a full Claude Code native plugin with agents, skills, and a
-session-start hook.
-
-## Prerequisites
-
-- [Claude Code](https://claude.ai/code) installed
-- Node.js >= 20.11
-
-## Install
-
-```bash
-/plugin marketplace add ionivetech/mugiwara && /plugin install mugiwara
-```
-
-## How it works
-
-Claude Code clones the repo and reads from:
-
-- `skills/` and `agents/` — symlinks to `content/skills/` and
-  `content/agents/`. Claude Code auto-discovers all 26 skills and 14 agents.
-- `hooks/hooks.json` — defines a SessionStart hook that runs
-  `hooks/session-start.ts`, injecting the crew announce header at every
-  session start.
-
-The hook announces: "Mugiwara crew available. The workflow auto-activates
-for non-trivial requests..."
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-Or start any task — the crew auto-activates at session start.
-
-## Update
-
-```
-/plugin update mugiwara
-```
-
-## Uninstall
-
-```
-/plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [config.md](../concepts/config.md).
-
-Switch autonomy mode with `/mugiwara-mode guided|semi|auto`.
-
-Or set permanently in `.mugiwara/config`: `mode=guided`.
-
-## Troubleshooting
-
-### Plugin not showing up
-
-1. Verify marketplace is registered: `/plugin marketplace list`
-2. If not, re-run the marketplace add command
-3. Check Claude Code is up to date
-
-### Skills not found
-
-1. Check that `skills/` and `agents/` symlinks resolve correctly
-2. Reinstall: `/plugin uninstall mugiwara` then reinstall
-
-### Hook not running
-
-The session-start hook requires Claude Code plugin hook support. Ensure
-you're on a recent Claude Code version.

package/docs/install/cli.md

@@ -1,115 +0,0 @@
-# CLI Install (Windsurf, Cline, Kilo)
-
-These platforms don't have native plugin systems. Use the mugiwara CLI
-installer to copy files into the platform's config directory.
-
-## Prerequisites
-
-- Node.js >= 20.11
-
-## Install
-
-```bash
-npx @ionivetech/mugiwara@latest install --target <id> --yes
-```
-
-Replace `<id>` with one of: `windsurf`, `cline`, `kilo`.
-
-Or install globally first:
-
-```bash
-npm i -g @ionivetech/mugiwara
-mugiwara install --target <id> --yes
-```
-
-### What gets written
-
-| Target | Skills/agents | References | Bootstrap |
-|--------|---------------|------------|-----------|
-| Windsurf | `.devin/rules/*.md` (stubs) | `.mugiwara/refs/*.md` | — |
-| Cline | `.clinerules/*.md` (stubs) | `.mugiwara/refs/*.md` | — |
-| Kilo | `.kilo/rules/*.md` (stubs) | `.mugiwara/refs/*.md` | `kilo.jsonc` |
-
-Tier 3 targets use stubs (pointer + routing) to keep rule files small.
-Full skill bodies live in `.mugiwara/refs/` — the agent loads them on demand.
-
-### Interactive mode
-
-Drop `--yes` for the interactive wizard:
-
-```bash
-npx @ionivetech/mugiwara install
-```
-
-Pick scope (global/project), target(s), and confirm before writing.
-
-### Multiple targets
-
-```bash
-npx @ionivetech/mugiwara install --target windsurf,cline,kilo --yes
-```
-
-Or all available targets:
-
-```bash
-npx @ionivetech/mugiwara install --target all --yes
-```
-
-## Verify
-
-Ask your agent:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-```bash
-npx @ionivetech/mugiwara@latest update --project . --target <id> --yes
-```
-
-Or with global CLI:
-
-```bash
-mugiwara update --project . --target <id> --yes
-```
-
-## Uninstall
-
-```bash
-npx @ionivetech/mugiwara@latest uninstall --project .
-```
-
-Or with global CLI:
-
-```bash
-mugiwara uninstall --project .
-```
-
-## Global install
-
-```bash
-mugiwara install --global --target <id> --yes
-```
-
-Installs to `~/.devin/rules/` (Windsurf), `~/.clinerules/` (Cline), or
-`~/.kilo/rules/` (Kilo).
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [config.md](../concepts/config.md).
-
-## CLI reference
-
-```bash
-mugiwara install                                  # wizard (interactive)
-npx @ionivetech/mugiwara@latest install --yes     # non-interactive (project + all)
-mugiwara update --project . --target <id> --yes   # replace existing files
-mugiwara uninstall --project .                    # remove what manifest recorded
-mugiwara list                                     # show installations
-mugiwara list --check                             # health check (missing files)
-mugiwara reset --keep-logs                        # wipe mission state, keep lessons
-mugiwara reset --force                            # override multi-actor guard
-```

package/docs/install/codex.md

@@ -1,44 +0,0 @@
-# Codex Install
-
-Mugiwara installs as a native Codex plugin.
-
-## Prerequisites
-
-- [Codex](https://github.com/openai/codex) CLI or app installed
-
-## Install
-
-```bash
-codex plugin marketplace add ionivetech/mugiwara && codex plugin add mugiwara@mugiwara
-```
-
-## How it works
-
-Codex reads `.codex-plugin/plugin.json` which references `content/skills/`.
-All 26 skills are auto-discovered. Agents come from `content/agents/` via the
-`agents/` symlink.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-```bash
-codex plugin update mugiwara
-```
-
-## Uninstall
-
-```bash
-codex plugin remove mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [config.md](../concepts/config.md).

package/docs/install/copilot.md

@@ -1,45 +0,0 @@
-# GitHub Copilot Install
-
-Mugiwara installs as a Copilot plugin directly from the GitHub repo.
-
-## Prerequisites
-
-- [GitHub Copilot](https://docs.github.com/en/copilot) extension installed
-
-## Install
-
-```bash
-copilot plugin install https://github.com/ionivetech/mugiwara
-```
-
-## How it works
-
-Copilot clones the repo and auto-discovers skills from `content/skills/`
-and agents from `content/agents/`.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-Reinstall with the same command:
-
-```bash
-copilot plugin install https://github.com/ionivetech/mugiwara
-```
-
-## Uninstall
-
-```bash
-copilot plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [config.md](../concepts/config.md).