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…
Draw every code change in the reply as a diff, an annotated file tree, or a class diagram, and keep ideas in prose. TRIGGER on every reply that explains code, Architecture, a change, a name, or a finding, and whenever the Architect says "show me". DO NOT TRIGGER to score a set of options; that is /rank.
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.
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…
Runs before the agent uses a tool for Bash tool calls, executing block-git-revert.sh and block-unsafe-delete.sh (2 commands). From heyJordanParker/dotfiles.
★not rated 22
changed 19d agoA
tokens not measured
Use to write ads and video sales letters — the paid pieces that have to earn attention cold. Owns the ad's hook and body and the VSL's script. Returns the piece from the brief and evidence. Does not research.
Use for ONE small page-work task the researcher hands off — extract the quotes and facts from ONE cached page against a named subject, or run ONE discovery search — then return. Does exactly the one task named and nothing more: never plans a thread, never judges a source, never writes copy, never files records into…
Use to react to a piece as the project's buyer — is it believable, is it valuable, would they pay. Judges strictly as the owner-approved buyer definition. Returns the buyer's reaction. Writes only findings files (including the strategy-gate stub), never copy.
The copy chief — default agent for the copywriter profile, launched as --agent copy-chief. Runs the copy line end to end: sets up products and projects, dispatches research, commissions the judged root files, dispatches the strategy stage and the review rounds, resolves findings, and makes the final "will this sell"…
Use to run the strategy stage under a job — re-derive the project's own judged buyers, problems, and statistics from the original research records, build the high-level strategies the owner picks among, fan the options inside the picked strategy, then write the three plan files (Reader.md, Brief.md, Proof.md). Returns…
Use to write pages, stories, and social posts — headlines, hooks, and leads through to the full sales, opt-in, or catalog page, plus narrative components and posts. Returns the draft from the brief and evidence. Does not research.
Use to audit whether a piece converts — the action path: CTA presence, position, and size, competing actions, form friction, and ad-to-page continuity. Returns findings against the conversion checks. Writes only findings files, never copy.
Use to review a draft for how it reads and whether it sounds human — sentence quality, structure between sections, and the distinctiveness pass. The sole de-slop owner. Returns findings and suggested edits; never mutates the draft. Does not write new copy from a brief.
Use to write email — onboarding, trial-ending, win-back, expansion, broadcast, cold, and launch sequences. Owns the subject, preview, and first line through to the one ask and the P.S. Returns the email from the brief and evidence. Does not research.
Use to check a piece's claims — every claim must resolve to a research record or an owner/product fact, or it is listed for the chief. Returns the unsourced claims, never kills them. Independent of the writers and the chief. Writes only findings files, never copy.
Use to review a completed research phase against the research SOP before the records are judged — reads the assembled threads and returns a per-thread verdict of pass or return-for-re-execution with the named gap. Fresh context, runs when the chief closes the research phase. Reviews the artifacts, never rewrites a…
Use to attack whether a research or strategy artifact describes anything real — does the claimed market, buyer, problem, and language actually EXIST. Not an improver: a destroyer of fabricated reality. Rates each item's existence from 1 to 100 with reasoning, default low. Writes only findings, never copy.
Use to turn a completed research phase into the judged root files — reads the research records and writes Buyers.md, Competitors.md, Problems.md, and Statistics.md, each entry a 1-to-100 rating with its arithmetic, reasoning, and record citations. Fresh context, runs after research, before strategy. Writes only the…
Use after a research thread completes to review the quality of the sources it read. Runs a fresh context, sweeps the URLs the registry holds unjudged, reads each page, and writes one trustworthiness and one usefulness score (each 1-100) per URL into the sources registry. Writes nothing but registry judgments — never a…
Use to write video scripts that are content, not sales — YouTube and explainer scripts that teach or tell rather than pitch. Returns the script from the brief and evidence. Does not research. DO NOT TRIGGER for video sales letters; use ads-writer.
★not rated 22
changed 14d agoA58 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: