benjaminshoemaker
47 verified skills1,927 total stars
feature-audit
Multi-source audit of a shipped feature against its original plans, product vision, UI/UX best practices, and live browser inspection. Produces consolidated findings with prioritized recommendations.
testing41
phase-prep
Check prerequisites before starting a phase. Use before /phase-start to verify dependencies are met and context is loaded.
testing41
product-spec
Generate PRODUCT_SPEC.md through guided Q&A. Use as the first step when starting a new greenfield project.
documentation41
spec-verification
Verify generated specification documents for context preservation and quality issues. Automatically triggered after document generation. Checks that upstream requirements are preserved and identifies common specification problems.
testing41
update-docs
Update documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.
development41
verify-task
Run code-verification on a specific task. Use to verify a single task's acceptance criteria after implementation.
development41
configure-verification
Auto-detect test, lint, typecheck, and build commands from package.json, Makefile, and other project config. Use during project setup or when build tooling changes. Runs silently — no prompts.
tools41
security-scan
Run dependency audits, secrets detection, and static analysis to find CVEs, leaked credentials, and insecure code patterns. Use at phase checkpoints or before releases.
development41
codex-implement
Delegate code implementation to Codex CLI. Claude decomposes, scopes context, and verifies; Codex implements. Accepts a spec file, text description, or gathers requirements interactively.
tools41
auto-verify
Attempt automated verification of criteria before falling back to manual. Parses criterion text for automation hints and executes appropriate tool (curl, browser, file check). Invoked by verify-task and phase-checkpoint for MANUAL and MANUAL:DEFER criteria.
tools41
feature-technical-spec
Define technical approach (architecture, integration points, data model) for a feature through guided Q&A and write FEATURE_TECHNICAL_SPEC.md. Use after /feature-spec.
documentation41
capture-session
Extract decisions, action items, new context, and insights from the current session into LEARNINGS.md and auto-memory. Run before ending any substantive conversation.
testing41
code-verification
Multi-agent code verification workflow using a main agent and sub-agent loop. Use when verifying code against requirements, acceptance criteria, or quality standards. Triggers on requests to verify, validate, or check code against specifications, checklists, or instructions.
development41
create-pr
Create a GitHub PR with verification and Codex review. Runs verify.sh and code/doc review before PR creation.
development41
codex-review
Have OpenAI Codex review the current branch with documentation research. Use for second-opinion code reviews or when you want cross-AI verification.
development41
data-flow-audit
Detect split data source anti-patterns and scattered business rule duplication where the same logic is reimplemented across multiple files and languages. Catches semantic duplication that syntactic tools like jscpd miss. Use at phase checkpoints or when investigating data consistency issues.
tools41
feature-plan
Generate EXECUTION_PLAN.md and scoped AGENTS.md files for a feature. Use after /feature-technical-spec to create the task breakdown.
data-ai41
go
Resume execution from wherever you left off. Detects current state and runs the appropriate next command, or reports what's blocking progress. Use at the start of any session to pick up where you left off.
development41
generate-plan
Generate the greenfield execution plan plus root and scoped AGENTS.md files. Use after /technical-spec to create the phased task breakdown.
data-ai41
merge-prs
Merge multiple PRs with conflict resolution and CI failure auto-patching. Analyzes optimal merge order, resolves conflicts, pulls CI logs on failure, and fixes issues. Use when multiple feature branches need merging into the base branch.
testing41
oauth-login
Complete OAuth login flow and store tokens for verification. Use when browser verification requires authenticated sessions.
tools41
phase-checkpoint
Run checkpoint criteria after completing a phase. Use after /phase-start completes all tasks to verify quality gates before proceeding.
testing41
populate-state
Generate `.claude/phase-state.json` from the main execution plan and git history. Use to recover phase state after context loss or when joining an existing project.
data-ai41
review-deferred
Review deferred verification items. Use when you want to check or clear the deferred review queue without waiting for project completion.
testing41
tech-debt-check
Identify code duplication, cyclomatic complexity, large files, and maintainability anti-patterns. Use at phase checkpoints or on-demand to quantify technical debt.
development41
setup
Initialize a new project with the AI Coding Toolkit. Use when setting up toolkit skills in a new or existing project.
tools41
vision-audit
Audit project alignment with VISION.md, identify SDLC gaps, and generate feature proposals. Use when reviewing strategic direction or planning new features.
testing41
vercel-preview
Resolve Vercel preview deployment URL for the current git branch. Invoked by browser-verification when deployment.enabled is true, or directly to check deployment status. Use to check deployment status or when browser verification needs a URL.
testing41
update-target-projects
Discover and sync all toolkit-using projects with the latest skills. Use when skills are modified, after the post-commit hook reminds you, or to batch-sync multiple projects.
tools41
ui-ux
Comprehensive UI/UX analysis and design intelligence. Point at any product to get: code analysis, product/user context assessment, industry pattern research, and prioritized improvement recommendations. Combines craft principles, data-driven design intelligence, and creative excellence. Also guides design system setup for consistent AI-assisted UI work.
development41
technical-spec
Generate TECHNICAL_SPEC.md through guided Q&A. Use after /product-spec to define the technical architecture.
documentation41
run-todos
Implement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.
tools41
progress
Report completion status of the main and feature execution plans. Use to check how many tasks remain and which phases are done.
testing41
phase-start
Execute all tasks in a phase autonomously. Use after /phase-prep confirms prerequisites are met.
tools41
list-todos
Analyze and prioritize TODO items from TODOS.md. Use when planning work or deciding what to implement next.
testing41
innovate
Identify high-impact innovative additions to the current app or plan. Use when planning next features, during strategic reviews, or when the user asks for creative ideas.
tools41
fresh-start
Orient to project structure and load context. Use at the start of each new session or after context reset to understand the project state.
tools41
feature-spec
Define feature requirements (problem, users, scope, acceptance criteria) through guided Q&A and write FEATURE_SPEC.md. Use when starting a new feature.
documentation41
discover
Exploratory conversation before /product-spec. Asks one question at a time, runs background research for open-source/off-the-shelf alternatives, and writes DISCOVERY_NOTES.md. Use when the user has an idea but hasn't scoped it yet.
documentation41
criteria-audit
Validate EXECUTION_PLAN.md for verification metadata, manual reasons, and testability. Use when preparing Phase 1 or after editing EXECUTION_PLAN.md.
testing41
codex-consult
Get a second opinion from OpenAI Codex on documents, specs, or plans. Use for cross-AI consultation on any content, not just code diffs.
development41
capture-learning
Capture a project learning or pattern to LEARNINGS.md. Use when you discover a useful pattern or convention during development.
development41
browser-verification
Verify browser-based acceptance criteria using ExecuteAutomation Playwright MCP with multi-tool fallback chain. Invoked by verify-task and phase-checkpoint for BROWSER:* criteria.
tools41
audit-skills
Audits skills, commands, and prompt templates for best practice violations including length, checklists, verification steps, and progressive disclosure. Use after creating or modifying skills, during reviews, or to improve existing prompt files. Produces prioritized improvement suggestions.
testing41
analyze-sessions
Extract automation patterns from session logs and rank by impact. Use periodically after multiple sessions to identify repetitive workflows that could become skills or hooks.
tools41
add-todo
Add a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.
development41
audit-agentsmd
Audit AGENTS.md (or CLAUDE.md) for length, attention-zone misplacement, and extraction opportunities. Produces a prioritized report with reordering and extraction recommendations. Use when AGENTS.md exceeds 400 lines, after major additions, or when agent instruction compliance is poor.
testing41