@mmerterden/multi-agent-pipeline 19.1.4 → 20.0.0

package/pipeline/skills/shared/core/multi-agent-local-autopilot/SKILL.md

@@ -1,55 +0,0 @@
----
-name: multi-agent-local-autopilot
-language: en
-description: "Full pipeline + local + autopilot  -  no worktree, no confirmations, all 6 phases run end-to-end on the current branch. Use when the full pipeline should run on the current branch with no worktree and no prompts."
-user-invocable: true
-argument-hint: '"task"  -  issue URL, Jira ID, free-text, or #id (for resume)'
----
-
-# multi-agent-local-autopilot  -  Full Pipeline, Local Branch, Autonomous
-
-**Input**: $ARGUMENTS
-
-Runs the full 6-phase pipeline **without creating a worktree** + **skipping all confirmations**. The `autopilot + local` combination. Byte-identical behavior to `/multi-agent:local-autopilot` (Claude Code colon-form).
-
-## Matrix (which one should I use?)
-
-| Command | Pipeline | Worktree | Confirmation |
-|---|---|---|---|
-| `multi-agent "task"` | Full 6 phases | ✅ | ✅ (interactive) |
-| `multi-agent-autopilot "task"` | Full 6 phases | ✅ | ❌ |
-| `multi-agent-local "task"` | Full 6 phases | ❌ | ✅ |
-| **`multi-agent-local-autopilot "task"`** | **Full 6 phases** | **❌** | **❌** |
-
-Depth is a separate axis, asked at Phase 0 Step 7.5 rather than encoded in the command name: Full runs every phase above, Short runs Dev → Review → Test → Commit → Report. The two autopilot rows never ask and always run Full.
-
-## What changes
-
-- The Phase 0 Step 6 worktree step is skipped (local contract)
-- The Phase 2 Plan Approval Gate is skipped (autopilot contract)  -  `state.autopilot === true`
-- The Phase 3 test prompt is skipped, Phase 4 commit/PR does not wait for confirmation
-- **v7.0.0+**: The Phase 2 safety classifier (`classify-plan-safety.mjs`) always runs; if the score is ≥ 50 it asks for a single manual confirmation even in autopilot (`prefs.global.autopilotSafetyGate`, default on)
-
-## What is NEVER skipped
-
-- 🔴 Review blocking → Automatic fix + rebuild (max 3 retries)
-- 💥 Build fail → Automatic fix + rebuild (max 3 retries, then pause)
-- 🛡️ Safety classifier pause → manual confirmation when a high-risk plan is detected
-- ⚠️ Kill/Purge → Always asks for confirmation (destructive)
-
-## Examples
-
-```bash
-multi-agent-local-autopilot "PROJ-12345"
-multi-agent-local-autopilot https://github.com/org/repo/issues/316
-multi-agent-local-autopilot "LoginView dark mode fix"
-multi-agent-local-autopilot "#3"
-```
-
-## Delegation
-
-The orchestrator skill (`multi-agent/SKILL.md`) takes the `--local` + `"autopilot": true` state flags together. Contract: `refs/phases/phase-0-init.md` Step 6 (local branch) + `refs/phases/phase-1-plan.md` Step 5 (gate skip) + Step 5c (safety classifier, v7.0.0+).
-
-## Required: outward-facing payload contracts
-
-Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.

package/pipeline/skills/shared/core/multi-agent-resume-local/SKILL.md

@@ -1,51 +0,0 @@
----
-name: multi-agent-resume-local
-language: en
-description: "Continue already-done LOCAL work through the pipeline tail: Review (with its build gate) → Commit/PR → Report (technical analysis + Jira test-scenario comment). No dev phase. Use when local work is already done and only review, build, commit and reporting remain."
-user-invocable: true
----
-
-# multi-agent resume-local  -  Take Existing Branch Work Through the Pipeline Tail
-
-You already wrote (and maybe hand-tested) the change on the current branch, or committed it outside the pipeline entirely. `ship` picks up from there and runs the **pipeline tail** over that existing work in one command, without re-developing. (As of v14.0.0 a Short run reviews its own output, so this is for work with no pipeline run behind it.)
-
-## Pipeline
-
-```
-Phase 0: Init          → project/branch detect, resolve base + diff (work already done), Jira id, state (NO worktree)
-Phase 3: Review        → the Verify gate first (stack-aware build + existing tests; SUCCESS required), then
-                         parallel review (Fable + Opus + Sonnet) + Fable triage
-Phase 4: Commit        → commit remaining changes + push + open PR if none exists
-Phase 5: Report        → technical analysis + Jira comment with test scenarios (channels: Jira / PR / Confluence / Wiki)
-```
-
-Phases 1-2 (Plan / Dev) are skipped by design  -  the branch's local diff IS the Phase 2 output. The build that Dev's exit gate would have run happens inside Review instead, because there is no Dev run to inherit a log from.
-
-## When to use it
-
-- After a `:local` run answered Short (which skips Review + Test) to run the full quality tail on the same branch.
-- After hand-coding / hand-testing a change, to get review + build/test + PR + Jira write-up without re-running dev.
-
-## When NOT to use it
-
-- Change not written yet → `multi-agent` / `multi-agent:local`.
-- Only the review → `multi-agent:review`; only report/channels → `multi-agent:channels`; only device UI test → `multi-agent:test` / `multi-agent:manual-test`.
-
-## Input
-
-```bash
-multi-agent resume-local                   # current branch vs base; Jira id from branch name
-multi-agent resume-local PROJ-12345      # explicit Jira id for the Phase 5 comment
-multi-agent resume-local --base develop     # override base branch for the diff
-multi-agent resume-local autopilot          # no gate prompts: auto-fix, auto-PR, auto-comment
-```
-
-## Notes
-
-- Build+Test is the automated success gate (not the interactive device user-test  -  that is `multi-agent:manual-test`). If the repo has no tests, it reports "no tests present"  -  never fabricates results.
-- Commit/PR follows house rules: conventional message, `Ref: #N` (never Closes/Fixes), NO AI/bot attribution. PR opened only if one does not already exist.
-- Full phase contract lives in the Claude Code command `commands/multi-agent/ship/SKILL.md`; this skill is the Copilot-CLI counterpart.
-
-## Required: outward-facing payload contracts
-
-Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.