A personal, opinionated collection of AI workflows covering the full engineering lifecycle — from product discovery to implementation and deployment.
Workflows are extracted from real project work, not designed in the abstract. They are AI-provider-agnostic by design.
product/ # Product workflows (discovery, PRD review)
design/ # Design workflows (prototype, design review)
engineering/ # Engineering workflows (tech spec)
git/ # Git workflows (commit)
team/ # Team member definitions used by review workflows
providers/
claude-code/ # Adapters for Claude Code slash commands
Canonical workflows live at the top level. Provider-specific adapters in providers/ are thin pointers — a command header and a file reference. They contain no workflow logic.
Symlink the commands you want into your global Claude Code commands directory:
ln -sf "$(pwd)/providers/claude-code/"*.md ~/.claude/commands/They will be available as slash commands in any project (e.g. /discovery).
| Workflow | Description |
|---|---|
| discovery | Take a raw idea and produce a signed-off PRD |
| competitor-analysis | Map the solution landscape and surface positioning gaps |
| prd-review | Run a structured multi-perspective review of a PRD using the full team |
| product-design | Take a signed-off PRD and produce an interactive HTML prototype covering all screens and states |
| product-design-review | Run a structured multi-perspective review of a product design document; surface missing states, spec gaps, and developer ambiguities |
| tech-spec | Take a signed-off PRD and design doc and produce a complete technical specification; two-phase: pre-spec engineering review then full-team post-spec review |
| plan | Slice the tech spec into vertical slices and a hierarchical backlog; assign owners and define ACs |
| build | Orchestrate a build cycle: pick up available tasks, implement in parallel, review, merge, repeat |
| implement | Implement a single backlog task TDD, in character as the assigned team member; open a PR |
| review | Review a PR with domain-primary and cross-domain reviewers in parallel; approve or request changes |
| qa | Pre-release QA pass across a milestone; Neville leads; failures become backlog tasks |
| validate | Validate implementation fidelity against spec, design, and ACs at milestone level |
| commit | Generate a commit message consistent with the repo's style |
The review team is defined in team/. Each team member has their own file with their role, focus areas, and voice. They are used by the prd-review workflow and any other workflow that benefits from multi-perspective input.
| Character | Role |
|---|---|
| Dumbledore | Principal Engineer |
| Hermione | Senior Backend Engineer |
| Ron | Senior Web Engineer |
| Sirius | Senior iOS Engineer |
| Luna | Creative PM |
| Percy | Conservative PM |
| McGonagall | Principal Designer |
| Snape | Data Scientist |
| Moody | Security Engineer |
| Neville | QA / Testing |
| Arthur | DevOps / SRE |
| Tonks | UX Researcher |
| Fred | Growth / Marketing |
| Harry | Junior Android Engineer |
| Ginny | Junior Backend Engineer |
| Colin | Junior PM / Product Analyst |
| Dean | Junior Designer |
| Voldemort | Adversarial Reviewer |
| Victor | Senior Android Engineer (product owner) |