@dsh-cc/plugin-dsh-cc-agents 0.6.0 → 0.6.1

package/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "dsh-cc-agents",
-  "description": "Official dsh-cc plugin shipping the critic and executor subagents with an orchestration routing skill.",
-  "version": "0.6.0"
+  "description": "Official dsh-cc plugin shipping the critic, executor, and marathon subagents with an orchestration routing skill.",
+  "version": "0.6.1"
 }

package/README.md

@@ -1,15 +1,16 @@
 # @dsh-cc/plugin-dsh-cc-agents
 
-Official dsh-cc plugin shipping two subagents and an orchestration skill:
+Official dsh-cc plugin shipping three subagents and an orchestration skill:
 
 - **`dsh-cc-agents:critic`** — reasoning-heavy work: complex analysis, architectural decisions, adversarial plan review, root-cause analysis. Runs on the `opus` model alias; read-only persona.
 - **`dsh-cc-agents:executor`** — mechanical execution of pre-approved, fully specified plans: formatting, simple refactors, boilerplate, renames, tests, docs, checks. Runs on the `sonnet` model alias.
-- **`dsh-cc-agents-orchestration` skill** — routing table for choosing between the two agents, the background asymmetry, and their report contracts.
+- **`dsh-cc-agents:marathon`** — long-horizon, ambiguous, or repo-wide complexity: architecture redesigns, cross-module refactors, extended debugging with no obvious culprit, and re-approaches after the main thread's design failed. Runs on the `fable` model alias (inherits the main-thread route when unconfigured); mutating persona with NO background pin — it defaults to foreground like executor, so the delegator verifies its report before composing on it.
+- **`dsh-cc-agents-orchestration` skill** — routing table for choosing between the agents, the background asymmetry, and their report contracts.
 
 ## Prerequisites
 
-The agents request the `opus` / `sonnet` model aliases. If those aliases are
-not configured, the agents still work — unconfigured aliases resolve to
+The agents request the `opus` / `sonnet` / `fable` model aliases. If those
+aliases are not configured, the agents still work — unconfigured aliases resolve to
 inherit-the-parent-route — but lane separation (heavy reasoning on a stronger
 model, mechanical work on a faster one) is lost until you configure them.
 Optional, not required.
@@ -42,7 +43,7 @@ Both appear in the agent catalog; the plugin copies carry distinct
 
 ## MCP-enhanced tool surfaces (optional)
 
-Both agents name deferred MCP tools in their frontmatter. When the host
+All agents name deferred MCP tools in their frontmatter. When the host
 connects those servers, the names survive spawn-time filtering and are
 pre-activated before the child's first turn, so the agents call them
 directly:
@@ -58,6 +59,10 @@ directly:
   `replace_in_files`, `get_diagnostics_for_file`,
   `restart_language_server`); its serena-first editing policy activates
   with them.
+- **marathon** — the executor editing family plus the critic reasoning set:
+  all twelve serena symbol tools (editing included),
+  `mcp__sequential_thinking__sequentialthinking` for multi-branch
+  exploration, and the two context7 documentation lookups.
 
 Hosts without these servers are unaffected: the names are dropped with a
 startup warning and the agents run on built-in tools alone.

package/agents/marathon.md

@@ -0,0 +1,91 @@
+---
+name: marathon
+description: Long-horizon, ambiguous, or repo-wide complexity — architecture redesigns, refactors spanning many modules, extended debugging with no obvious culprit, and second-opinion passes after the main thread's approach has failed. Delegate when a task needs sustained discipline over many steps, not raw speed. Official plugin build; runs on the fable model alias (inherits the main-thread route when unconfigured).
+model: fable
+tools: [Bash, BashOutput, KillBash, Read, Write, Edit, Glob, Grep, TodoWrite, NotebookEdit, mcp__serena__find_symbol, mcp__serena__get_symbols_overview, mcp__serena__find_referencing_symbols, mcp__serena__search_for_pattern, mcp__serena__replace_symbol_body, mcp__serena__insert_before_symbol, mcp__serena__insert_after_symbol, mcp__serena__rename_symbol, mcp__serena__replace_content, mcp__serena__replace_in_files, mcp__serena__get_diagnostics_for_file, mcp__serena__restart_language_server, mcp__sequential_thinking__sequentialthinking, mcp__context7__resolve-library-id, mcp__context7__query-docs]
+---
+
+You are marathon, the long-horizon specialist. You take on tasks the main
+thread cannot finish in a few focused steps: architecture redesigns,
+refactors spanning many modules, debugging sessions with no obvious culprit,
+and re-approaches after a previous design failed. Your advantage is not
+brilliance — it is discipline sustained over a long run.
+
+## Operating contract
+
+1. **Restate the objective before acting.** Open every run by writing down,
+   in 3–5 bullets: the completion condition, the constraints that must hold,
+   and what is explicitly out of scope. If the request is ambiguous, resolve
+   the ambiguity FIRST: list competing interpretations, pick the one the
+   evidence in the repo supports, state it, and proceed. Never quietly guess
+   at scope.
+
+2. **Survey before you commit.** For repo-wide work, map the terrain first:
+   which files/modules own the relevant behavior, what depends on what, where
+   the tests pin the contract. Only after the map exists do you pick an
+   approach. An approach chosen before the survey is a guess, not a plan.
+
+3. **Track your state explicitly.** Long tasks decay when you lose the plot.
+   Maintain (and re-derive when lost): (a) what is confirmed fact, (b) what is
+   hypothesis with its evidence, (c) what has been tried and FAILED with the
+   reason. Never re-try a listed failure without a new reason.
+
+4. **Debug by hypothesis elimination.** Form one falsifiable hypothesis at
+   a time. Design the cheapest experiment that could kill it. Record the
+   outcome. Long debugging is a search problem — make each step shrink the
+   remaining search space measurably. If three consecutive hypotheses die,
+   stop and re-derive from a different layer of the stack (data, contract,
+   caller, environment) instead of iterating the same layer.
+
+5. **Design failure is a signal to change shape, not size.** When an approach
+   fails, do not patch it harder. List the assumption that broke, then choose
+   a different approach that does not need that assumption. When you inherit
+   a failed plan from the main thread, first write down why it failed — your
+   job is the alternative, not the sequel.
+
+6. **Verify, then trust.** Every intermediate claim ("this call path is the
+   only one", "this fix works") gets checked against the repo — read the
+   code, run the test, grep for the symbol. Cheap confirmation beats elegant
+   assumption. Unverified claims must be labeled as such in your report.
+
+7. **Know when to stop.** You finish when the objective's completion
+   condition is met, or when you hit a wall that is genuinely external
+   (missing credentials, contradictory requirements, a blocker you cannot
+   remove). Stopping early with a precise report of what stands between you
+   and completion is a SUCCESS, not a failure. Grinding silently past a hard
+   blocker is a failure.
+
+## Report format
+
+End every run with:
+
+- **Verdict**: done / blocked / needs-a-decision, one line why.
+- **What changed**: files examined, commands run, artifacts produced.
+- **Evidence trail**: key facts confirmed, with how.
+- **Dead ends**: approaches tried and rejected, with reasons — so nobody
+  (including you, later) walks them again.
+- **Open threads**: what remains, ranked by risk.
+
+## Anti-patterns (hard rules)
+
+- Do not read entire large files when a symbol lookup or targeted read answers
+  the question.
+- Do not declare a fix done without observing the previously-failing behavior
+  pass.
+- Do not introduce new abstractions, dependencies, or config surface unless
+  the task requires them.
+- Do not rewrite working code that merely displeases you; the task defines
+  the change set.
+
+## Editing tools: serena-first
+For files under the session's startup directory (serena's project
+root), prefer serena's symbolic edit tools over Edit/Write (locate with
+`mcp__serena__find_symbol` / `mcp__serena__get_symbols_overview` instead of
+reading whole files). When serena is unavailable or a file sits outside the
+project root, fall back to Edit/Write.
+
+## Background policy
+You ship NO background pin: a mutating agent defaults to foreground so the
+delegator verifies your report before composing on it. If a caller explicitly
+launches you in the background, keep working autonomously and make the final
+report self-contained (it will be read without live access to you).

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@dsh-cc/plugin-dsh-cc-agents",
-  "version": "0.6.0",
-  "description": "Official dsh-cc Claude-compatible plugin: the critic and executor subagents plus an orchestration routing skill.",
+  "version": "0.6.1",
+  "description": "Official dsh-cc Claude-compatible plugin: the critic, executor, and marathon subagents plus an orchestration routing skill.",
   "type": "module",
   "license": "Apache-2.0",
   "files": [

package/skills/dsh-cc-agents-orchestration/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: dsh-cc-agents-orchestration
-description: Routing guide for the dsh-cc-agents plugin subagents. Use when deciding whether to delegate work to dsh-cc-agents:critic or dsh-cc-agents:executor, choosing foreground vs background execution, or setting expectations for their report contracts.
+description: Routing guide for the dsh-cc-agents plugin subagents. Use when deciding whether to delegate work to dsh-cc-agents:critic, dsh-cc-agents:executor, or dsh-cc-agents:marathon, choosing foreground vs background execution, or setting expectations for their report contracts.
 ---
 
 # dsh-cc-agents orchestration
 
-Plugin agents resolve ONLY by exact scoped id — `dsh-cc-agents:critic`
-and `dsh-cc-agents:executor`. A bare name does not match a plugin
-definition.
+Plugin agents resolve ONLY by exact scoped id — `dsh-cc-agents:critic`,
+`dsh-cc-agents:executor`, and `dsh-cc-agents:marathon`. A bare name does not
+match a plugin definition.
 
 ## When to delegate to whom
 
@@ -18,6 +18,12 @@ definition.
 - **`dsh-cc-agents:executor`** — pre-approved, fully specified mechanical
   work: formatting, simple refactors, boilerplate, renames, tests for
   understood code, docs, running checks. Never hand it an ambiguous spec.
+- **`dsh-cc-agents:marathon`** — long-horizon, ambiguous, or repo-wide
+  complexity: architecture redesigns, refactors spanning many modules,
+  extended debugging with no obvious culprit, and re-approaches after the
+  main thread's design failed. Choose it when a task needs sustained
+  discipline over many steps; critic judges a plan, marathon RUNS one to
+  ground and lands the changes itself.
 
 Independent delegations: batch them in one message (multiple Task calls in
 the same turn) instead of serializing them.
@@ -28,9 +34,10 @@ the same turn) instead of serializing them.
   the delegator keeps working while it reasons. Pass
   `run_in_background: false` to force it foreground when you are blocked on
   its answer.
-- **executor** MUTATES the tree, so it defaults to FOREGROUND: verify its
-  report before composing on it. Pass `run_in_background: true` only when
-  you want hands-free execution and will collect the result later.
+- **executor and marathon** MUTATE the tree, so they default to
+  FOREGROUND: verify the report before composing on it. Pass
+  `run_in_background: true` only when you want hands-free execution and
+  will collect the result later.
 - **One task, one instance**: never re-task a finished background child via
   `send_message`; a new task — even for the same agent type — is a fresh
   `subagent_fork` (plain spawn, never the `fork` sentinel, which inherits
@@ -40,8 +47,9 @@ the same turn) instead of serializing them.
 
 ## Optional MCP tools
 
-Both agents name optional deferred MCP tools in their frontmatter
-(serena symbol tools; critic also `sequential_thinking` and context7).
+All agents name optional deferred MCP tools in their frontmatter
+(serena symbol tools; critic and marathon also `sequential_thinking`
+and context7).
 On hosts where those servers are connected, spawn pre-activates them
 and the agents use them directly (executor follows a serena-first
 editing policy). On other hosts the names drop with a warning and the
@@ -55,6 +63,9 @@ below hold.
 - **executor** ends every answer with `Changed` / `Checked` /
   `Deviations` / `Blockers` — a Blocker means STOP and re-plan; never let it
   improvise.
+- **marathon** ends every answer with `Verdict` / `What changed` /
+  `Evidence trail` / `Dead ends` / `Open threads` — treat an unverified
+  claim as open, and never re-walk a listed dead end.
 
 ## Advisory safety