Transform Shaping output into a concrete Modeling artifact — database schema, User experience, and Architecture. TRIGGER between Shaping and Slicing, or when the Architect asks to model an existing system before Execution.
MANDATORY for naming any code identifier — variable, function, file, folder, class, database column, route, CSS class. Always returns a 5-10 candidate slate; the caller picks. TRIGGER when proposing or choosing a name, on /naming, on "rename", "ideas", "options", "what should I call", or any new…
The orchestrate mode's contract. You own the Architecture and spend your whole capacity on it — Subagents make every change, and you validate what they return with read-only checks. TRIGGER when the session enters orchestrate mode, on the /orchestrate command, and when orchestrate mode is re-injected after compaction.…
Add pros, cons, and confidence to options in a Prompt. TRIGGER when the Architect asks for "/pcc", pros/cons/confidence, alternatives, options, approaches, or a ranked choice. DO NOT TRIGGER for a single implementation call, a convention Decision with repo Precedent, or a proposing-state turn where /propose is…
Dispatch 5 parallel Subagents, each using a named Frame from the roster, for competing takes on an Architect Prompt. TRIGGER on "/personas", "run personas", "diverse takes", "give me competing perspectives", or when the Architect explicitly asks for named thinkers. DO NOT TRIGGER when the task needs redundant…
Keep engineering boring and complete. TRIGGER when the Architect says KISS, pragmatic, don't overengineer, ship it, keep it simple, or asks for a pragmatic read on a Proposal, Plan, code review, or Architectural Decision. DO NOT TRIGGER when the Architect asks for maximum rigor over shipping pressure.
Shape the reply for the Architect - a sentence for a fact, a one-screen packet for a status or finding, a Decision Hierarchy for an Architectural discussion, impact stated before mechanism. TRIGGER on every reply that carries a Decision, a finding, or an Architectural discussion, and on /present. DO NOT TRIGGER for…
Broad-to-narrow research Orchestration - start with a wide census, harden the scope from returned Evidence, and specialize Subagents only once the exact situation is proven. TRIGGER when the Architect says "progressive research", "start broad", or when dispatching research or debugging Subagents into a situation whose…
Mandatory contract for every proposing-state turn. The classifier names it when the Architect types /propose. Builds the Proposal as a Decision Hierarchy: dominant call on top, gated children nested beneath it, genuine peers side by side, the work breakdown tagged onto Decisions rather than used as the skeleton. Opens…
Produce the Evidence that proves work is done before any completion claim. TRIGGER before reporting a Task complete, writing report.md, or claiming fixed, passing, or pre-existing. DO NOT TRIGGER while still implementing.
Check a diff for capability regressions — loss of User-facing capability ("the User can no longer X") or loss of system capability ("our system can no longer Y"). Maps changed code to affected Critical Path and system capabilities, traces each through the code, and reports any that no longer work. TRIGGER on…
Source-grounded external research for current library, API, framework, service, and vendor behavior. TRIGGER when the Task asks for current facts, docs, releases, compatibility, adoption, or external technical Decisions. DO NOT TRIGGER for in-codebase Architecture tracing; use /trace or the explorer agent.
Reviews Shaping, Modeling, Slicing, and Plan Prompts under docs/shaping/[feature]. Dispatches five parallel specialized Subagents. TRIGGER when the Architect asks to review a Shaping, Modeling, Slicing, or Plan artifact.
Read the changeset yourself, review it with one Claude reviewer and one codex reviewer on the same target at once, triage their findings with /triage, and iterate until a round returns no breaking finding. TRIGGER on "review the changes", "code review", on the Review before a changeset is presented to the Architect…
Collaborative Shaping with the Architect: capture requirements, boundaries, shapes, fit checks, research unknown mechanics, and transition to Modeling then Slicing. TRIGGER when the Architect asks to shape, scope, compare approaches, or turn a rough idea into a modeled change.
Build and publish the page the Architect reviews an Architecture Proposal on — one self-contained page toggling between the start state and the final state across architecture diagrams, annotated file trees, and database changes. TRIGGER when the Architect fires this Command by name. DO NOT TRIGGER to show…
Show the work in the reply — annotated file trees, relationship diagrams, state transitions, call and gate chains, timelines, because-chains, bars, signatures, column trees, and exact diffs, with the prose around them carrying the WHY. TRIGGER on every reply that explains code, Architecture, a change, a name, or a…
Turns a shaped and modeled change into vertical Slices with acceptance criteria and Verification requirements. Each Slice ends in demo-able functionality. The Plan becomes an immutable contract.
Code intelligence for the local codebase — search, callers, definitions, symbols, complexity, file/method reads with rich Architectural Context. TRIGGER whenever you need to find, understand, or trace relationships in code instead of raw grep or unfiltered file reads.
Turn returned reviewer findings into one graded report grouped by who each problem affects, and act on the gate. TRIGGER after review Subagents return findings — from /review, /regressions, /user-testing, or any audit — and before results reach the Architect. DO NOT TRIGGER while reviewers are still running, or for a…
Deep research of the systems behind a change — name the systems, show the architecture, read the git history for intent, trace the code, attack the understanding, and report in a layered file another Agent can act on coherently. TRIGGER when a change lands in a system the Agent has not mapped, when the Architect says…
Tests code changes by tracing real Critical Paths. Lists Critical Paths affected by uncommitted changes, spawns one Subagent per Critical Path to trace Execution and find gaps, then evaluates Architecturally. TRIGGER when the Architect says "user test", "test the Critical Paths", or "trace Critical Paths".
Verify the whole changeset the way the User meets it: the suite, the Review gate, the Critical Paths, once every Task has landed. TRIGGER when the last Slice is staged, when an autonomous run reaches functional completion, or on "verify the changes". DO NOT TRIGGER with Tasks still open, where the Orchestrator judges…
★not rated 20 13d agoA0 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: