Ever wish your AI coding partner could read your mind and avoid costly rework? Matt Pocock’s skillset shows how to make that happen.
The Simple Version
Think of each skill as a tiny recipe you give the agent. When you follow the recipe, the agent knows exactly what to do and why.
How It Actually Works
Low‑fidelity planning starts with a rough outline. It lets the agent see the big picture before diving into details, preventing expensive re‑writes later.
Agent Alignment
Before you start coding, "Grill Me" asks key questions about scope, goals, and constraints. This surfaces hidden assumptions the agent can’t guess.
Skill Workflow
After alignment, you move through a sequence: spec, ticket, implementation, and review. Each step hands off a clear, bounded piece of work.
Shared Vocabulary
Consistent terminology reduces confusion, so the agent interprets instructions the same way every time.
Technical Deep Dive
Matt’s "Grill Me" skill is just 22 lines of code that injects a set of questions into the agent’s prompt. The skill can be version‑controlled and reused across projects.
"Sandcastle" orchestrates multiple agents by looping through tickets, clearing context after each task, and re‑injecting the relevant skill set. This keeps context windows clean and prevents knowledge bleed‑over.
Skill pruning removes no‑ops — instructions that don’t change behavior. The pruning workflow can be triggered automatically when a new skill is added or modified.
A stateful Teach skill learns how you learn, storing your preferred phrasing and level of detail. It then builds custom lessons that match your mental model.
Why This Matters
These techniques turn a chaotic AI‑assisted development process into a repeatable, scalable workflow. Teams can ship larger features faster while keeping quality high.
By catching design flaws early and pruning unnecessary instructions, developers save hours of debugging and reduce compute costs.
Key Takeaways
- Align with the agent first — use Grill Me to surface hidden requirements.
- Start with low‑fidelity plans to avoid costly rework.
- Break work into specs and tickets for multi‑agent, multi‑context projects.
- Automate workflows with tools like Sandcastle and skill‑pruning scripts.
- Maintain a shared vocabulary for consistent agent understanding.
- Leverage a stateful Teach skill to tailor instructions to your learning style.
- Continuously prune no‑ops to keep prompts lean and effective.