Middle-down planning: decide and write down what gets built. Thirteen skills and six principles for an interactive session — intake routing, relentless grilling, domain modeling, frontier scouting, triage, specs and tickets. Every session ends in a written artifact carrying which of the four dimensions it closed. Requires ph-lib.
Plugin ph-plan from marketplace photon-plugins in mattlindell/photon-plugins. Commands read from the repo's manifest — 2 days ago.
define-doneClose the verification dimension by deciding one shared way a body of work will be proven done, and attach it to whatever carries the work — a live planning session, a spec, or a ticket set. Use when grilling has settled problem, shape, and approach, when a spec or tickets still have verification op
domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
grillingGrill the user relentlessly about a plan, decision, or idea until the frontier is empty, maintaining the domain model as you go and ending in a spec or tickets. Use when the user wants to stress-test their thinking, sharpen a design, or work out what to build, or uses any 'grill' trigger phrases.
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
intakeEntry point for work that does not exist yet. Use when the user describes something they want to build, floats an idea, brings a rough or half-formed spec, or asks where to start — before any planning or implementation begins.
principle-block-on-the-humanApply when an open question could be answered by the person in front of you. In an interactive planning session the human is the cheapest resolver of ambiguity - ask, and wait.
principle-close-or-block-the-dimensionApply at the end of any planning session. Every dimension ends either settled or as a named decision ticket - never merely discussed.
principle-name-the-destinationApply before decomposing work into tickets, phases, or a map. State what done looks like before you break anything into parts.
principle-one-way-doors-firstApply when sequencing decisions or ordering a plan. Surface and settle irreversible decisions early, while changing your mind is still cheap.
principle-walk-the-treeApply when interviewing, scoping, or decomposing. Ask the whole frontier of currently-answerable questions at once; never guess at an answer that would unblock a question you have not asked.
principle-write-it-downApply whenever a decision is reached, a term is pinned, or a session ends. A decision that was not recorded did not happen.
prototypeBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
scoutChart work too big for one agent session as a shared map of decision tickets on the issue tracker, then resolve them one at a time until the way to the destination is clear. Use when intake finds the frontier unmapped, when the work is a rewrite, migration, or other effort whose open questions canno
setup-ph-planConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
to-questionnaireTurn a decision you can't fully answer into a questionnaire for someone else to fill in.
to-specTurn the current conversation into a spec carrying a settled block and publish it to the project issue tracker — synthesis of what was already discussed, not a new interview. Use when a grilling or planning session has reached shared understanding and should end in a spec, or when the user asks to w
to-ticketsBreak a plan, spec, or the current conversation into tracer-bullet tickets, each declaring its blocking edges, and publish them to the configured tracker. Use when a planning session should end in tickets rather than a spec, when a spec needs splitting into slices an agent can build, or when the use
triageMove issues and external PRs through a state machine of triage roles — categorize, verify, grill if needed, and write agent-ready briefs. Use when intake finds the work already exists as an issue or PR, when the user asks what needs attention or what is ready for an agent, or names an issue or PR to
Unattended implementation: build what was decided, at a cost that tracks what is still unknown. Thirty-five skills, twenty-four principles, nineteen playbooks and three agents, forked from pstack. Reads the rigor signal a spec carries, gates expensive multi-agent work behind one-way doors, and caps every fan-out. Requires ph-lib.
59 skills · 3 agents · hooks
Engineering leadership and people management: 1:1s and skip-levels, difficult conversations, delegation, managing up, cross-functional collaboration, timelines and status, meetings and offsites, decision processes, OKRs, org design and transformation, team culture and rituals, post-mortems, and systems thinking. Twenty-four skills with a router.
24 skills
Comprehensive PHP development covering WordPress, Laravel, Sage/Roots, WooCommerce, and CodeIgniter 3 legacy maintenance. 16 skills for architecture decisions, troubleshooting, and implementation patterns, plus 4 scaffold commands.
16 skills · 4 commands
Claude Code plugins for a variety of projects and tasks
17 skills
Shared library for the photon plugins: four primitives that ph-plan and ph-build reference and require (codebase-design, technical-writing, unslop, writing-for-agents), plus nine operator tools you invoke directly (automate-me, bro, caveman, handoff, recall, reflect, teach, wait-what, what-did-i-get-done). Not a hat — nobody installs this because of the work they are doing.
13 skills
Atlassian and scrum operations: Jira, Confluence, Atlassian administration and templates, sprint analytics, senior-PM portfolio and risk management, meeting-transcript analysis, and internal team communications. Eight skills; bundles the Atlassian Remote MCP server.
8 skills · 1 MCP server
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development
9 skills · 1 command · 8 agents
AI-supervised issue tracker for coding workflows
1 skill · 1 agent · hooks
PRD generation and conversion skills for the Ralph autonomous agent loop
2 skills
MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows
18 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.