Matt Wynne shares talking-to-humans, a Skill that rewrites dense, jargon-heavy robot prose into plain concrete language people can follow.
mattwynne/skills
SkillsMP has collected 9 skills from mattwynne/skills. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 9
- GitHub stars
- 4
- GitHub forks
- 0
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/mattwynne/skills.Posts
See all →Skills in this repository
Showing 9 of 9 collected skills.
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.
Use when creating or editing Architecture Decision Records - guides thinking through decisions with stakeholders before documenting the outcome
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,…
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
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