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/to-spec-template.md
View on GitHub# Spec Template
```
## Problem Statement
The problem that the user is facing, from the user's perspective.
## Solution
The solution to the problem, from the user's perspective.
## User Stories
A LONG, numbered list of user stories. Each user story should be in the
format of:
1. As an <actor>, I want a <feature>, so that <benefit>
Example:
1. As a mobile bank customer, I want to see balance on my accounts, so
that I can make better informed decisions about my spending
This list of user stories should be extremely extensive and cover all
aspects of the feature.
## Implementation Decisions
A list of implementation decisions that were made. This can include:
- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
Do NOT include specific file paths or code snippets. They may end up being
outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more
precisely than prose can (state machine, reducer, schema, type shape),
inline it within the relevant decision and note briefly that it came from
a prototype.
## Testing Decisions
A list of testing decisions that were made. Include:
- A description of what makes a good test (only test external behavior,
not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)
## Out of Scope
A description of the things that are out of scope for this spec.
## Further Notes
Any further notes about the feature.
```
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 |