
Ask matt
SkillRecommends which skill or flow in Matt Pocock's engineering set fits your situation
- Open source
- 326K GitHub stars
- Developer tools

Recommends which skill or flow in Matt Pocock's engineering set fits your situation

Interviews you relentlessly about a plan while keeping a glossary and ADRs up to date

Runs a retrospective on a coding session and suggests changes to the agent's environment

Configures a repo's issue tracker, triage labels and domain docs for these skills

Adds two or three pointed follow-up questions after substantive advice or drafts

Guides doc writing in three stages: gather context, build sections, test on a reader

Writes status reports, 3P updates, newsletters and FAQ answers from template files

Edits AI-sounding prose to sound like its writer, using 26 numbered patterns

Sets up recurring marketing jobs an agent runs on a schedule, with checks and stop rules

Turns a screen recording of a manual task into tiered, tested automation scripts

Reads findings, verdicts and drafts that other agent desks left in a shared bench folder

Checks docs and prose against Vercel's writing guidelines and reports file:line findings

Draft three alternative team OKR sets, each with an objective and three key results

Write a one-to-two page PRD with a six-part value proposition for each market segment

Write job stories in the when, I want, so I can format with 6 to 8 acceptance criteria

Plan, word and run meeting polls and dot votes, with optional AskOne MCP control

Run audience Q&A for all-hands or webinars and turn every question into a FAQ with owners

Rewrite a feature-based roadmap as outcome statements with success metrics

Run a pre-mortem on a launch plan, sorting risks into tigers, paper tigers and elephants

Compare RICE, ICE, Opportunity Score, Kano and five other prioritisation methods

Turn tickets, PRDs or git logs into user-facing release notes grouped by change type

Facilitate a sprint retro with Start/Stop/Continue, 4Ls or Sailboat and owned action items

Plan a sprint from backlog and velocity: capacity, story selection, dependencies and risks

Map stakeholders on a power and interest grid and build a communication plan

Red-team a plan: steelman key assumptions, rank failure modes and name cheap tests

Turn a meeting transcript into notes with decisions, action items and open questions

Write user stories using the 3 C's and INVEST criteria with testable acceptance criteria

Write backlog items in the Why-What-Acceptance format with strategic context

Pick a first launch segment by scoring pain, budget, winnable share and referral reach

Map a customer journey from awareness to advocacy with emotions, pain points and fixes