Phil Bennett
Community@philipobenito
@thephpleague leadership group, wrote league/container and league/route.
Agent Skills by Phil Bennett
Showing 11 vetted skills indexed across 1 GitHub repositories.
philipobenitodesign-recovery
Recovers approved designs from tickets or documents and confirms scope before implementation.
philipobenitodesign-committee
Deliberates design decisions through three lens agents, cross-examination, and evidence-based synthesis.
philipobenitowork-swarm
Implements approved designs as file-disjoint tasks with concurrent review and verification.
philipobenitowork-review-receive
Verifies code review feedback against the codebase and implements accepted fixes in severity order.
philipobenitowork-tdd
Executes the red-green-refactor TDD cycle with verified failing tests before writing production code.
philipobenitodesign-handoff
Persists approved designs as ticket hierarchies or structured Markdown documents for future session recovery.
philipobenitowork-review-request
Dispatches a code reviewer subagent against a diff and drives the fix-and-re-review loop.
philipobenitodesign-dialogue
Guides interactive design dialogue from idea to explicitly approved design summary.
philipobenitodebug-investigation
Investigates bugs through reproduction, ranked hypotheses, and a minimal verified fix.
philipobenitodesign-review
Reviews consolidated design summaries by dispatching a fresh reviewer subagent with a three-dispatch budget.
philipobenitowork-verification
Runs fresh verification commands and cites their output before stating completion claims.
Frequently Asked Questions About Phil Bennett
FAQPage SchemaWhat tasks can I accomplish with philipobenito's skills?▼
You can run interactive or hands-off design deliberation, persist approved designs into GitHub Issues, Jira, GitLab, or Linear tickets, recover work from ticket references, execute test-driven development, perform evidence-driven bug investigation, orchestrate parallel implementation, and enforce code review and verification gates before shipping.
Who are these skills designed for?▼
Software engineers and technical leads who want disciplined engineering process enforcement: mandatory failing tests before production code, root-cause identification before fixes, severity-ranked review feedback handling, and explicit design approval before implementation begins.
How do the design skills work in practice?▼
design-dialogue walks you through one question at a time interactively, while design-committee runs hands-off deliberation among three lens agents (Pragmatist, Architect, Advocate) with a synthesiser resolving decisions. Both end with design-review and explicit user approval before handoff.
What are the prerequisites for using work-swarm or design-handoff?▼
Both require an approved design already in hand. work-swarm decomposes it into file-disjoint tasks for concurrent implementation with per-task review; design-handoff persists it into tickets under a single parent or a structured Markdown document when no ticketing system exists.
How does debug-investigation enforce fix quality?▼
It hard-gates all bug fixes: no code changes without a reproduction and an identified root cause, regardless of how simple the fix appears. It enforces scope discipline, an investigation budget, the minimal fix principle, and takes its own approval for the fix approach.