wcygan
@wcygan
Public Skills
playwright-cli
by wcygan
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages. Keywords: browser, automation, playwright, web testing, screenshot, form, click, navigate, scrape
customer-review
by wcygan
Customer voice: Preserve authentic customer language in evidence
data-review
by wcygan
Review data pipelines, warehouses, analytics infrastructure for reliability, quality, performance, governance, and cost. Spawns specialized agents (data-engineer, data-scientist, performance-analyst, security-auditor) to audit in parallel, then debate architecture trade-offs. Use when evaluating data platforms, assessing pipeline health, optimizing queries, or auditing data governance and compliance. Keywords: data pipeline, warehouse, analytics, ETL, data quality, query optimization, data governance, compliance, data platform.
debt-audit
by wcygan
Re-audit regularly - debt grows; quarterly audits prevent accumulation
api-workshop
by wcygan
Design new APIs or review existing ones using debate-driven multi-agent workshop. Agents propose designs and challenge each other on consumer UX, domain modeling, security, performance, and standards compliance. Use when the user wants to design a new API, review an existing API, decide between REST/GraphQL, or improve API architecture. Keywords: api design, api review, rest api, graphql, openapi, api architecture, api specification, endpoint design, api standards.
business-review
by wcygan
Launch a multi-function business review team to evaluate product ideas, features, or applications from stakeholder perspectives. Agents represent product management, marketing, engineering, finance, data science, data engineering, sales, and synthesis roles. Use when evaluating a new feature, assessing product viability, planning launches, or need cross-functional input on business decisions. Keywords: business review, product evaluation, feature assessment, stakeholder analysis, cross-functional review, product viability, go-to-market, unit economics, technical feasibility
spec-team
by wcygan
Exploratory prototyping (use /research instead)
launch-ready
by wcygan
Vague recommendations: "Monitor closely" is not a mitigation plan
postmortem-team
by wcygan
Blameless language guide
spike-team
by wcygan
Time-sensitive bug fixes
migration-team
by wcygan
Stakeholders satisfied with outcome
arch-review
by wcygan
RFC-style review of major technical decisions using a 5-agent debate team. Spawns tech-lead, security-auditor, performance-analyst, reliability-engineer, and devils-advocate for independent analysis followed by structured discussion. Produces decision document with pros/cons, dissenting opinions, and recommendation. Use for architecture decisions, technology selection, major refactors, design reviews. Keywords: architecture, RFC, design review, technical decision, architecture review, design decision, major change
competitor-analysis
by wcygan
Comprehensive competitor research using a 7-agent team. Spawns parallel research agents for product, marketing, UX, and technical analysis, then sequential synthesis agents for MVP spec, go-to-market strategy, and competitive landscape. Use when evaluating a competitor, planning a new product, or scoping an MVP. Keywords: competitor, competitive analysis, market research, product research, MVP, go-to-market, GTM, teardown, product teardown
spike
by wcygan
Quick prototype or investigation in an isolated git worktree. Creates a worktree, spawns agents to explore a technical approach, and opens a draft PR with findings. Use for time-boxed technical exploration, feasibility testing, library evaluation, or codebase audits. Keywords: spike, prototype, worktree, explore, feasibility, proof of concept, PoC, try, experiment, can we use, audit, investigate, trace, wired up
new-agent
by wcygan
Create custom Claude Code subagents. Interactive wizard that gathers requirements, generates the agent .md file with proper frontmatter and system prompt. Use when creating a new agent, adding a subagent, or making a custom agent available globally. Keywords: agent, subagent, create agent, new agent, custom agent
commit
by wcygan
Analyze staged changes and create a well-crafted conventional commit. Handles unstaged files, pre-commit hook failures, and multi-file changes. Use when ready to commit, or when you want help writing a good commit message. Keywords: commit, git commit, stage, conventional commit, commit message
diff-explain
by wcygan
Explain a diff in plain English. Works with staged changes, unstaged changes, commits, branches, or PR numbers. Use when you want to understand what changed and why. Keywords: diff, explain diff, what changed, understand changes, diff summary, review changes, read diff
review-changes
by wcygan
Orchestrate multiple review agents for a comprehensive pre-PR code review. Analyzes diff, verifies intent alignment with linked issues, and checks for broader codebase impacts. Use before opening a PR to catch bugs, security issues, silent failures, and performance problems. Keywords: review, code review, pre-PR, diff review, check changes, audit changes
onboard
by wcygan
Explore an unfamiliar codebase and generate an ARCHITECTURE.md with component diagrams, pattern catalog, and dev workflow guide. Use when joining a new project, picking up an OSS repo, or needing to understand how a codebase works. Keywords: onboard, architecture, explore, understand, codebase, new project, map, document, how does this work
changelog
by wcygan
Generate a changelog or release notes from git history between two refs (tags, commits, or branches). Use when preparing a release, summarizing changes, or creating release notes. Keywords: changelog, release notes, release, changes, what changed, version, tag, diff, history, summary
fix-issue
by wcygan
Take a GitHub issue number, investigate it, implement a fix, write tests, and open a PR. End-to-end workflow from assigned issue to merged PR. Use when you want to fix a specific GitHub issue. Keywords: fix issue, github issue, resolve issue, close issue, implement issue, issue to PR, bug fix
agent-team
by wcygan
Launch and coordinate Claude Code agent teams for complex tasks. Use when the user wants to parallelize work across multiple agents, needs a team for review, debugging, design, or feature development, or asks to "create a team" or "spawn agents." Keywords: agent team, team, spawn, teammates, parallel agents, coordinate, collaborate, multi-agent
security-review
by wcygan
Run a targeted security audit on specified files or modules. Uses OWASP-informed checks, dependency vulnerability scanning, and auth/input validation review. Use for security audits, vulnerability checks, or before deploying sensitive code. Keywords: security, audit, vulnerability, OWASP, CVE, secrets, injection, XSS, auth, authentication, authorization
debug-team
by wcygan
Debug complex issues using an agent team with competing hypotheses. Spawns 3-5 investigators that actively challenge each other's theories and converge on the root cause. Use for tough bugs where the root cause is unclear. Keywords: debug team, competing hypotheses, root cause, investigation, multi-agent debug, hard bug, mystery bug