mattwynne

Use when writing or reviewing Gherkin features, especially after discovering examples or edge cases that reveal a new business rule

Use when a feature feels under-tested, after implementing new functionality, or before a release to discover edge cases, UX issues, and bugs through hands-on CLI exploration

Use when running yx commands that create, modify, or delete yaks outside of real project work — provides an isolated temp environment

Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main

Prepare a yak for implementation by establishing spec, acceptance criteria, and breaking into sub-yaks

Discover work structure by approaching goals and finding blockers — emergent planning through action, not top-down decomposition

Use when a yak needs requirements, examples, and a plan before implementation - prepares a yak so it's ready for subagent-driven development

Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup

Interview Matt about the next product/dev iteration, turn the discussion into a focused iteration plan, publish planning artifacts, validate the plan, and ask whether this LLM session should launch the Fabro implementation-and-review delivery workflow. Use when planning the next iteration, shaping work before implementation, or preparing a plan for delivery.

Delegate self-contained research, review, planning, debugging, or implementation subtasks to a Pi subagent running the openai-codex/gpt-5.5 model. Use when the user asks for Pi, GPT-5.5, a subagent, independent analysis, parallel investigation, or a second coding-agent opinion.

Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule

Offer to capture and, when accepted, write a docs/kaizen observation when we notice friction, imperfections, waste, opacity, brittleness, or failure in the pipeline/factory/workflows/tooling used to create the product. Use for workflow/tooling problems, not ordinary product bugs.

Read, audit, and safely manipulate Resend email configuration and message data through the Resend API. Use when inspecting domains, API keys, audiences, contacts, broadcasts, emails, webhooks, or making explicit Resend changes with an API key from the environment.

Read, audit, and safely manipulate Postmark configuration and message data through the Postmark API. Use when inspecting servers, streams, senders, domains, templates, messages, webhooks, suppressions, or making explicit Postmark changes with API tokens from the environment.

Read, audit, and safely manipulate DNSimple DNS configuration through the DNSimple API. Use when inspecting domains, zones, DNS records, or making explicit DNS changes with a DNSimple API token from the environment.

Investigate and resolve docs/kaizen problem observation notes. Use when Matt asks to fix a kaizen note, investigate root cause, suggest repair options, or apply an obvious workflow/tooling fix and update the note with the resolution.

Capture delivery-process friction as a kaizen note and immediately run the kaizen-fix workflow on it. Use when Matt asks to JFDI a kaizen issue, wants a kaizen note and fix in one pass, or asks to turn an observed workflow/tooling problem directly into an applied improvement.

Use when distilling practical design heuristics from code reviews, PR discussions, design sessions, architecture debates, incident reviews, or prior team decisions

Run a parallel multi-model review with Gemini, Codex, and Claude, then synthesize the reports into a single decision-oriented review. Use when the user asks for an ensemble review, three-way review, deep review, or independent second opinions on code, design, plans, or documents.

Use when a feature feels under-tested, after implementing new functionality, or before a release to discover edge cases, UX issues, and bugs through hands-on exploration

Investigate and resolve docs/kaizen problem observation notes. Use when the user asks to fix a kaizen note, investigate root cause, suggest repair options, or apply an obvious workflow/tooling fix and update the note with the resolution.

Offer to capture and, when accepted, write a docs/kaizen observation when we notice friction, imperfections, waste, opacity, brittleness, or failure in the pipeline/factory/workflows/tooling used to create the product. Use for workflow/tooling problems, not ordinary product bugs.

Pick the next ready iteration plan from docs/iterations and execute it through the Fabro iteration-implementation workflow. Use when Matt asks to implement, run, execute, or start the next ready iteration.

Interview Matt about the next product/dev iteration, turn the discussion into a focused iteration plan, and submit it to the project's Fabro plan-validation workflow. Use when planning the next iteration, shaping work before implementation, or preparing a plan for Fabro validation.