Skip to main content
What it contains
Small, editable, composable engineering skills for requirements, specs/tickets, TDD, debugging, architecture, research, review, and implementation.
Typical uses
Apply individual engineering disciplines without letting one plugin own the whole development process.
Why people choose it
Inference: chosen for control/composability instead of a monolithic methodology.
Last meaningful updateUnknown
Production readinessproduction
Classification
Subject domains
software engineeringagent skills
Task categories
software engineeringagent skills
Project phases
planningimplementationtestingreview
Secondary types
plugin
Select when
- Need a focused engineering discipline
- Want composable skills
Do not select when
- Need a centralized autonomous engineering factory
Implementation complexitymedium
Routing heuristic 88.0%
Security boundary clarity
3/5 First-party routing documentation
5/5 Strengths
None documented.
Poor-fit scenarios
- Need a centralized autonomous engineering factory
Limitations
None documented.
skills/engineering/ask-matt/SKILL.md
Route to a suitable skill.
routing
skills/engineering/grill-with-docs/SKILL.md
Elicit requirements/domain language.
requirements
skills/engineering/tdd/SKILL.md
Red-green-refactor.
TDD
skills/engineering/diagnosing-bugs/SKILL.md
Feedback-driven bug diagnosis.
debugging
skills/engineering/code-review/SKILL.md
Standards/spec review.
review
skills/engineering/
Convert intent to executable work.
specticketsimplementation
skills/engineering/improve-codebase-architecture/SKILL.md
Survey architecture opportunities.
architecture
FrameworksNone documented
Operating systemsNone documented
Installation methodsClaude plugin, npx skills add
Required credentialsNone documented
External servicesNone documented
Major dependenciesNone documented
Compatibility notes
None documented.
One-sentence semantic summary
Small, editable, composable engineering skills for requirements, specs/tickets, TDD, debugging, architecture, research, review, and implementation.
Capability keywords
requirementsTDDdebuggingdomain modelingarchitecturereviewresearchticketing
User intent phrases
- Need a focused engineering discipline
- Want composable skills
Negative match phrases
- Need a centralized autonomous engineering factory
Differentiators
None documented.
Security considerations
None documented.
Privacy considerations
None documented.
Uncertainty
Unresolved items
- License not conclusively verified in the inspected first-party material.
Inference notes
None documented.
Repository usage guidance
installation summaryClaude plugin; npx skills add
basic usage summaryApply individual engineering disciplines without letting one plugin own the whole development process.
documented entry pointsNone documented
key configuration filesNone documented
important directoriesskills/engineering/, skills/productivity/
documentation pathsREADME.md
example pathsNone documented
Relationships
alternative
high
Compound owns a larger loop; Matt Pocock skills are smaller/selective.
Recommended combinations
Agent-team orchestration high
Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.
Order of operations
- Connect least-privilege agent runtimes
- Add RTK on runtime machines
- Install only role-relevant engineering skills
- Keep human review gates
Routing rules
rule_021: Need a focused engineering discipline P979
Rationale
Small, editable, composable engineering skills for requirements, specs/tickets, TDD, debugging, architecture, research, review, and implementation.
Required conditions
None documented.
Preferred
mattpocock/skills
Fallback
None