Skip to content

refactor(mmwstack): follow pstack and cut how to one file, rename how explorer to reader - #1526

Merged
chancheuklap merged 5 commits into
devfrom
refactor/1522-how-follows-pstack
Nov 15, 2026
Merged

chancheuklap merged 5 commits into
devfrom
refactor/1522-how-follows-pstack

Conversation

@chancheuklap

@chancheuklap chancheuklap commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Why

pstack's latest upstream update (cursor/plugins#1236) cut how to one file and stopped the mode from running it. mmwstack still had the old how, with explorers, an explainer and two prompt files. This PR delivers #1522, part of #1519, and keeps mmwstack's own delegation rules.

What changed

  • how is one SKILL.md. It starts one read-only subagent that explores and explains in one pass, then presents the result. The two prompt files are gone.
  • The mode no longer runs how by itself. Feature, Bug fix, Hillclimb, Perf issue, Refactoring, Investigation, architect, no-comments, Comment Sicko and the Benny automation now trace the code themselves. architect keeps mmwstack's rule to trace only what the invoker's evidence leaves unexplained.
  • The how explorer role is now reader, still read-only, still the default for a delegate that reads and reports. The how explainer role is gone. The rename note in setup-mmwstack carries an old line's model over to reader.
  • Comment Sicko traces a symbol itself. It still ends with needs: why on <symbol> when the claim rests on history.

Scope

Tradeoffs

  • Deleting how explorer and using swarm workers for readers would break Droid, because swarm workers has no droid.
  • Keeping the name how explorer would leave a role named for a step that no longer exists.
  • Running the how subagent on judgment and prose would lose the droid-level read-only guarantee.

Blast Radius

Door: two-way. The text reverts cleanly. Until the owner reruns /setup-mmwstack, ~/.agents/mmwstack-models.md has no reader line, so the mode's default reader, recall, automate-me and maintain-verification-skill report an unfilled role. The old mmwstack-how-explorer droid still exists and is read-only.

Verification

  • Ran the new how as the main chat on a question about this repo. It started one read-only subagent, and the subagent returned an accurate explanation in 36 seconds. The run used the old mmwstack-how-explorer droid, the same role under its earlier name, because setup has not been rerun.
  • No stale how explorer, how explainer, explainer-prompt, explorer-prompt or Exploration angle is left, apart from the rename note. No disable-model-invocation anywhere under mmwstack/.
  • The link check shows the same single known false positive before and after. scripts/check passes.
  • Every deleted line that upstream did not delete, and the decision for each remaining how mention, are listed in the ticket.

chancheuklap and others added 5 commits November 15, 2026 23:18
`how explorer` was also the general role for a delegate that reads and
reports (the mode's default delegation, recall, automate-me and
maintain-verification-skill). The `how` skill stops using explorers, so
the role keeps its job under the name `reader`, stays read-only, and
`how explainer` is retired. Setup carries a `how explorer` model over to
`reader` and drops `how explainer`.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
`how` now starts one fresh subagent on the `reader` role that explores
and explains in one pass, and the main chat presents the result. The
complexity check, the explorers, the explainer and both prompt templates
are gone, along with the glossary entries that only described them.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
The mode no longer runs `how` on a nontrivial change. Investigation,
Feature, Bug fix, Perf issue, Hillclimb and Refactoring trace the code
themselves, and the Multi-phase plan appendix no longer names `how`.
Architect traces the systems its invoker's evidence leaves unexplained
and keeps its start from that evidence.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Comment Sicko traces a named symbol or call through the nearby code and
its call sites. It still ends its report with `needs: why on <symbol>`
when a claim rests on history, and no-comments and the build guide say
the same.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
The README skill list, guides 02, 03, 04 and 10, and the three Benny
files no longer say the mode, the Investigation playbook, architect or
a Benny automation runs `how`. Guide 03 now describes `how` as one
read-only subagent instead of two to four explorers. `/how` stays where
it is a command the reader types.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant