Open-source repos
mattpocock/skills
Turn requirements interviews into specifications, task dependencies and code reviews
This page provides source information and editorial guidance. Recommendations and trust labels do not mean every skill here was tested. Results for individual skills are on the skill data pages. See skill data · Listing policy
Overview
Matt Pocock’s collection breaks development collaboration into composable steps: resolve open decisions, write a specification, divide work into verifiable tasks, then review coding standards and specification compliance separately. SkillFlux has collected all 38 skills at a pinned commit. This analysis explains the engineering workflow from its instructions so readers can choose the steps their project needs.
SkillFlux sample check
On 2026-10-31, SkillFlux pinned this source at commit a496f55, drew a seeded sample of 20 from the 38 entries it contains, and ran static health check 1.0.0 on each. 40% had no failing check, said when to use the skill and carried a license.
- 20/20sampled entries had a SKILL.md we could check
- 0/20fail at least one check
- 12/20do not say when to use the skill
- 0/20have no license we could find
- 2/20bundle scripts the agent may run
- 0/20include scripts that call the network
- 0/20include destructive shell commands
- 0/20exceed the 5,000-token body guideline
See the 20 sampled entries
The sample reads files only; it does not run any skill and does not describe entries outside the sample. Flags describe what a skill contains; they are not verdicts. Raw data · Method
What the skills help you do
Inputs, methods and outputs described in the collected source version.
Interview by decision dependencies
grilling maps an idea into a decision tree. Each round asks only questions whose prerequisites are settled and offers recommendations, avoiding downstream design based on unresolved assumptions.
Read the source instructions ↗Synthesize a specification
to-spec synthesizes the conversation and codebase into a problem statement, user stories, implementation decisions, testing boundaries and exclusions for handoff after clarification.
Read the source instructions ↗Divide a specification into verifiable tasks
to-tickets creates small vertical slices across data, interfaces, UI and tests, with explicit blocking dependencies. Each completed ticket should be independently demonstrable or verifiable.
Read the source instructions ↗Separate standards and specification reviews
code-review starts from a fixed Git comparison point and separately checks repository standards and the originating specification, so clean code does not hide missing requirements.
Read the source instructions ↗A typical workflow
Choose the current step
Start with an unresolved idea, discussed requirements or an existing specification. Check the selected skill’s trigger and host dependencies.
Set requirements and acceptance boundaries
Resolve decision dependencies when an interview is needed, then use to-spec to record user stories, testing boundaries and exclusions.
Work through task dependencies
Use to-tickets to divide work into verifiable vertical slices. During implementation, advance tasks with completed prerequisites and retain validation results.
Review against specifications and standards
Review changes against a fixed Git comparison point, record specification gaps and standards issues separately, then prepare the handoff.
Best for
- Developers who need to clarify hidden assumptions, acceptance criteria and project vocabulary before implementation.
- Teams with specifications or tickets that want to implement in dependency order and distinguish coding standards from requirement coverage.
Use cases
- Coding & development
- Planning & long tasks
- Content & writing
SkillFlux notes
This page analyzes the instructions, references and scripts of the 38 skills at a pinned commit, across engineering, productivity, misc and in-progress; it does not claim execution testing of these workflows. Listed skills each have a health check report; install them by following the original repository.
Installation and use
Open the original repository and read its README, the selected skill instructions and any linked scripts. Check installation paths, host requirements, dependencies and licenses, then follow the project documentation to verify a small task in a workspace you can restore.
Limitations
- Some workflows require a configured issue tracker, domain glossary and architecture decisions. Implementation and review may also depend on other skills, Git and subagents.
- Interviews, specification publication and ticket approval have different interaction boundaries. The 38 skills are not one program that completes development in a single call; in-progress also contains workflows under development upstream.
Alternatives
- Superpowers (obra)
Compare Superpowers for another workflow connecting planning, implementation, debugging and testing, with attention to activation and handoff.
- OthmanAdi/planning-with-files
Compare planning-with-files when the main problem is losing plans and findings during long tasks rather than linking interviews, specifications and tickets.