Matt Pocock walks through the core workflow in his skills repository, using an existing command-line project as his example. The sequence starts with an interview and ends with implementation and review. Specs and tickets are useful when the work needs more than one agent session.
Install and configure
Pocock demonstrates npx skills@latest add mattpocock/skills, selecting the public-facing skills and his agent. He chooses a global installation and symlinks for his solo setup. For teams, he recommends project-level installation so the configuration can be shared.
The setup skill asks about an issue tracker, triage labels and domain documentation. He selects local Markdown for this demonstration and says the setup can be adapted to other trackers. He also shows an Ask Matt skill as an interactive guide to the workflow.
Interview, then choose a path
/grill-with-docs explores the repository and interviews the developer, recording domain knowledge and architecture decisions. Pocock asks to remove internal commands from his CLI. After six questions the agent outlines the removals and shared-module changes.
For work that fits in the remaining session, he would go straight to /implement. If questions need a runnable answer, he suggests a prototype. For larger work, /to-spec records the destination and /to-tickets breaks the route into pieces sized for individual sessions. In the demo he deliberately takes the longer path to show it, then reduces the proposed three tickets to one.
Pocock describes a context “smart zone” and his own approximate 140,000-token threshold as a working heuristic, not a universal model limit. He clears context between implementation tickets when needed.
Implement and review
In the demonstration, implementation runs checks and invokes a review against the spec and repository standards. Pocock favors separate review agents so they approach the changes with fresh context. The agent reports that its checks passed and commits the result. This is one walkthrough, not an independent evaluation of the workflow’s reliability.