mattwynne

Design trustworthy, maintainable acceptance-test automation across domain, service, and UI boundaries in any technology stack.

Plan a behaviour-changing iteration through adversarial example mapping, Gherkin, collaborative domain modelling, Matt-approved ADRs, plan assembly, and publication.

Choose domain-only BDD implementation or full iteration delivery for a published ready or validated plan, then ask for explicit launch approval and run the guarded Fabro command.

Start planning a product or engineering iteration, classify it as behaviour-changing or technical/refactoring, and route into the appropriate specialist planning skill.

Plan a technical or refactoring iteration that preserves observable behaviour, with explicit capability, constraints, architecture decisions, proof, and publication.

Investigate delivery-workflow friction or a docs/kaizen note, creating the observation first when no matching note exists; establish evidence-backed causes and options without implementing a fix.

Implement and validate a countermeasure for an investigated docs/kaizen note, then document its resolution. Use when asked to fix or resolve a kaizen note, not for investigation-only requests.

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…

Use when creating or editing Architecture Decision Records - guides thinking through decisions with stakeholders before documenting the outcome

Communicate with people in plain, concrete language. Use when explaining work, reporting progress, describing risks, asking questions, or handing work back to a human, especially after a long technical task.

Improve, rewrite, critique, or draft prose with a concise, vigorous, reader-centered style inspired by classic usage guidance including Strunk's public-domain The Elements of Style. Use for essays, emails, docs, blog posts, memos, announcements, and any…

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…

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…

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,…

Inspect, preview and apply bounded literal cells or explicit in-workbook financial formulas in existing Google Sheets, with mandatory review and read-only recovery.

Create Google Docs, insert public PNG logos or apply bounded revision-guarded text/formatting changes, and recover uncertain operations without replaying writes.

Upload one explicitly requested local BB-server file to Google Drive, or intentionally import conservative XLSX/DOCX/PPTX as native Sheets/Docs/Slides, with exact owner review and read-only recovery.

Create an explicitly located Google Drive folder or file an existing Google Drive file without copying or changing its URL, with inspected inherited access and single-use recovery.

Create native Google spreadsheets, read bounded ranges, route existing-cell edits through inspection and owner review, or recover an operation without replaying writes.

Copy a requested Drive file into an explicit destination with a single-use operation key and read-only recovery.

Grant, change or revoke a direct Google Drive file or folder permission, including anyone-with-link access, with mandatory owner approval and read-only recovery.

Deliver verified PA for BB changes and get feedback from the running BB installation. Use after implementing plugin, marketplace, or documentation changes that are ready for delivery.

For contributors maintaining Yaks — Use before writing Gherkin when exploring a story's behaviour, rules, examples, questions, scope, or readiness with stakeholders

For contributors maintaining Yaks — Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule

For contributors maintaining Yaks — Use when designing event-driven architectures, evaluating aggregate boundaries, deciding between event sourcing and current-state storage, building read models, or when a codebase has overlapping domain objects emitting…

For contributors maintaining Yaks — 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

Prepare a yak for contributors maintaining Yaks itself through scope discussion, example mapping, BDD formulation, and implementation-ready context.

For contributors maintaining Yaks — Use when mutation testing reveals survived mutants — guides deep analysis of whether each mutant signals a missing test, a design improvement opportunity, or an equivalent mutation

For contributors maintaining Yaks — Use when evaluating the ubiquitous language in a codebase - produces a glossary of domain terms with references and commentary on inconsistencies, awkward names, or overlapping concepts

Implement a prepared yak for contributors maintaining Yaks itself using isolated worktrees, one-test-at-a-time TDD, verification, and dev merge.

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…

Explain how to use BB Hands-Free's iPhone tap-to-talk view and its safety limits.

Find prior AI coding-agent/Pi sessions, recover context, locate artifacts created in earlier sessions, or reopen old sessions using the holocron CLI. Use when Matt mentions holocron, prior sessions, previous agent work, missing Google Docs/files/URLs, or asks…