Repository navigation
refactor(mmwstack): follow pstack and cut how to one file, rename how explorer to reader - #1526
Merged
Merged
Conversation
`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>
This was referenced Nov 15, 2026
refactor(mmwstack): follow pstack and cut why to one file, recall starts its own investigators
#1527
Merged
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
pstack's latest upstream update (cursor/plugins#1236) cut
howto one file and stopped the mode from running it. mmwstack still had the oldhow, with explorers, an explainer and two prompt files. This PR delivers #1522, part of #1519, and keeps mmwstack's own delegation rules.What changed
howis oneSKILL.md. It starts one read-only subagent that explores and explains in one pass, then presents the result. The two prompt files are gone.howby itself. Feature, Bug fix, Hillclimb, Perf issue, Refactoring, Investigation,architect,no-comments, Comment Sicko and the Benny automation now trace the code themselves.architectkeeps mmwstack's rule to trace only what the invoker's evidence leaves unexplained.how explorerrole is nowreader, still read-only, still the default for a delegate that reads and reports. Thehow explainerrole is gone. The rename note insetup-mmwstackcarries an old line's model over toreader.needs: why on <symbol>when the claim rests on history.Scope
whyand its two roles, which are mmwstack 的 why 跟上 pstack 精简为一个短文件,recall 自起调查员,版本号到 0.15.42 #1523.~/.agents. Its droids andmmwstack-models.mdchange when the owner reruns/setup-mmwstack.Tradeoffs
how explorerand usingswarm workersfor readers would break Droid, becauseswarm workershas no droid.how explorerwould leave a role named for a step that no longer exists.howsubagent onjudgment and prosewould 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.mdhas noreaderline, so the mode's default reader,recall,automate-meandmaintain-verification-skillreport an unfilled role. The oldmmwstack-how-explorerdroid still exists and is read-only.Verification
howas 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 oldmmwstack-how-explorerdroid, the same role under its earlier name, because setup has not been rerun.how explorer,how explainer,explainer-prompt,explorer-promptorExploration angleis left, apart from the rename note. Nodisable-model-invocationanywhere undermmwstack/.scripts/checkpasses.howmention, are listed in the ticket.