JPeetz/agent-skills / skills/development/mattpocock-dev-workflows
mattpocock-dev-workflows
VerifiedUse when you need Matt Pocock's engineering workflow patterns: spec synthesis, deep-module design, domain modeling, two-axis code review, or disciplined bug diagnosis. A meta-skill covering five complementary sub-patterns for real engineering — not vibe coding.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 2.0 KB |
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 20.6 KB |
| evals/evals.json | config | 5.2 KB |
| references/adr-format.md | markdown | 2.7 KB |
| references/code-review-smell-baseline.md | markdown | 2.2 KB |
| references/codebase-design-glossary.md | markdown | 2.7 KB |
| references/context-format.md | markdown | 2.3 KB |
| references/deepening.md | markdown | 2.5 KB |
| references/design-it-twice.md | markdown | 2.6 KB |
| references/diagnosing-bugs-phases.md | markdown | 7.2 KB |
| references/to-spec-template.md | markdown | 1.6 KB |
references/adr-format.md
View on GitHub# ADR Format
ADRs live in `docs/adr/` and use sequential numbering:
`0001-slug.md`, `0002-slug.md`, etc.
Create the `docs/adr/` directory lazily: only when the first ADR is
needed.
## Template
```md
# {Short title of the decision}
{1-3 sentences: what's the context, what did we decide, and why.}
```
That's it. An ADR can be a single paragraph. The value is in recording
*that* a decision was made and *why*, not in filling out sections.
## Optional sections
Only include these when they add genuine value. Most ADRs won't need them.
- **Status** frontmatter (`proposed | accepted | deprecated | superseded
by ADR-NNNN`): useful when decisions are revisited
- **Considered Options**: only when the rejected alternatives are worth
remembering
- **Consequences**: only when non-obvious downstream effects need to be
called out
## Numbering
Scan `docs/adr/` for the highest existing number and increment by one.
## When to offer an ADR
All three of these must be true:
1. **Hard to reverse**: the cost of changing your mind later is meaningful
2. **Surprising without context**: a future reader will look at the code
and wonder "why on earth did they do it this way?"
3. **The result of a real trade-off**: there were genuine alternatives and
you picked one for specific reasons
If a decision is easy to reverse, skip it: you'll just reverse it. If
it's not surprising, nobody will wonder why. If there was no real
alternative, there's nothing to record beyond "we did the obvious thing."
### What qualifies
- **Architectural shape.** "We're using a monorepo." "The write model is
event-sourced, the read model is projected into Postgres."
- **Integration patterns between contexts.** "Ordering and Billing
communicate via domain events, not synchronous HTTP."
- **Technology choices that carry lock-in.** Database, message bus, auth
provider, deployment target. Not every library: just the ones that would
take a quarter to swap out.
- **Boundary and scope decisions.** "Customer data is owned by the
Customer context; other contexts reference it by ID only." The explicit
no-s are as valuable as the yes-s.
- **Deliberate deviations from the obvious path.** "We're using manual SQL
instead of an ORM because X." Anything where a reasonable reader would
assume the opposite. These stop the next engineer from "fixing"
something that was deliberate.
- **Constraints not visible in the code.** "We can't use AWS because of
compliance requirements." "Response times must be under 200ms because of
the partner API contract."
- **Rejected alternatives when the rejection is non-obvious.** If you
considered GraphQL and picked REST for subtle reasons, record it;
otherwise someone will suggest GraphQL again in six months.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |