Skip to content

matthewyjiang/rho-pstack

v0.3.0MIT

Matt's design-first engineering workflow: an attributed Rho port of pstack and thermos.

GitHub

rho-pstack

Matt's engineering workflow as a Rho Agent Plugin: design first, prove the result, and run one combined thermos review per PR. It ships skills plus the two thermos review agents. There is no installer and no model pin.

A port of Lauren Tan's pstack v0.15.25 and Cursor's thermos v1.0.0.

Install

rho plugins install https://github.com/matthewyjiang/rho-pstack.git

Start a new Rho session so it picks up the skills and agents. To update, use rho plugins update rho-pstack

Use

$pstack implement this feature
$architect sketch the ownership model; stop before implementing
$why why is this retry limit here?
$thermos review this PR
$interrogate challenge this design with a different model

/skill:<name> also works, and the model can load skills on its own.

GroupSkills
Entrypstack (routes to the others)
Designhow, why, architect, sharpen
Proofblast-radius, prove-it-works, show-me-your-work, correct
Reviewthermos, thermo-nuclear-review, thermo-nuclear-code-quality-review, interrogate
Principles15 principle-* skills
  • thermos runs its two lens agents in parallel, one for correctness/security and one for code quality, then merges the results into one verdict. Both use the parent's model. If a lens agent isn't loaded or fails, that lens falls back to Rho's built-in reviewer.
  • interrogate challenges a design across at least two model families, chosen per call through the agent tool's model field or through a host that delegates to other models, such as T3 Code's delegate_task. Without two families it says cross-model review is unavailable.

Agents

Agent Plugins 1.0 standardizes only skills and MCP, so the agents live in Rho's extension directory, io.github.matthewyjiang.rho/agents/ (spec §8.2). Other clients ignore it.

AgentLensLoads rubric
thermo-nuclear-review-subagentcorrectness/securitythermo-nuclear-review
thermo-nuclear-code-quality-review-subagentcode qualitythermo-nuclear-code-quality-review

These mirror upstream Thermos' two subagents. Each loads its rubric skill itself, so the thermos prompt carries only the scope and evidence. Both inherit the parent's model, and a per-call model can move a lens to another one. Because they are runtime: rho, they also run under T3 Code host delegation. Neither has edit tools; their shell is limited to read-only Git/gh by instruction, not by sandbox.

  • Rho version. Loading these needs a Rho build with plugin-agent support. Older builds load only the skills, and thermos falls back to reviewer.
  • Overrides. An agent file with the same id in ~/.agents/agents, ~/.rho/agents or <project>/.agents/agents (project files need RHO_TRUST_PROJECT_AGENTS=1) overrides the plugin's. It replaces the whole definition, so start from a copy of the shipped file and keep tools; omitting tools grants every tool, including edits.
  • Plugin scope. A project-scope plugin overrides a user-scope one. A disabled plugin contributes no agents, and project plugins load only with RHO_TRUST_PROJECT_PLUGINS=1.
  • Files. Agent files must resolve inside the plugin root; symlinks pointing outside it are rejected.

Repository AGENTS.md, user instructions, and permissions always win. See workflow-contract.md and review-routing.md for the rules the skills follow.

License

MIT. Derived from cursor/plugins at commit 09d06eb: pstack/ (© 2026 Lauren Tan) and thermos/ (© 2026 Cursor). The original notices are in licenses/. This is an unofficial port.