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.
Plan a technical or refactoring iteration that preserves observable behaviour, with explicit capability, constraints, architecture decisions, proof, and publication.
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…
Carry a delivery-workflow problem end to end: capture or amend a kaizen note, investigate its cause, and apply and validate a fix. Use when asked to kaizen a problem or take a workflow/tooling observation through resolution; use the stage-specific skills for…
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.
Use when creating or editing Architecture Decision Records - guides thinking through decisions with stakeholders before documenting the outcome