petestewart
@petestewart
Public Skills
ralph-script
by petestewart
Add a Ralph Wiggum autonomous loop to the current project. Creates ralph-loop.sh and prompt.md files that enable Claude to autonomously work through a PLAN.md task list. Use when the user says "/ralph-script", "add ralph loop", "set up ralph script", "add autonomous loop", or wants to bootstrap the Ralph Wiggum loop files into a project. Supports a --force flag to skip interactive checks.
explain-project
by petestewart
Generate a detailed, engaging FOR[name].md document that explains an entire project in plain language. Covers technical architecture, codebase structure, technology choices, and lessons learned (bugs, pitfalls, best practices). Written in a conversational, memorable style with analogies and anecdotes. Use when the user invokes "/explain-project" or asks to "explain this project", "write a project explainer", "write a FOR[name].md", "document this project for me", or "help me understand this codebase". Accepts an optional name argument (e.g., "/explain-project Pete").
test-review
by petestewart
Review unit tests for quality, coverage, consistency, and adherence to existing codebase patterns. Use when the user says "/test-review", "review my tests", "check my test coverage", "are my tests good", or needs feedback on test quality and patterns.
plan
by petestewart
Create implementation plan from PRD.md and specs/. Use when the user has specifications and wants an actionable task list. Also use when the user says "/plan", "create a plan", "implementation plan", "task breakdown", or "plan the work".
prd
by petestewart
Expand a problem statement into a Product Requirements Document (PRD). Use when the user has a PROBLEM.md and wants to create a fuller PRD.md with technical approach, dependencies, affected systems, and open questions. Also use when the user says "/prd", "create a PRD", "expand to PRD", or "product requirements document".
problem-statement
by petestewart
Create a structured problem statement document for a feature, bugfix, or project. Use when starting a project, adding a feature, or fixing a bug and you need to clearly define the problem, context, desired outcome, and success criteria. Accepts input from Jira tickets (via MCP), document links, or text descriptions.
specs
by petestewart
Create technical specifications from PRD.md and PROBLEM.md. Use when the user has a PRD and wants detailed technical specs for implementation. Also use when the user says "/specs", "create specs", "technical specifications", or "spec it out".
review-as
by petestewart
Review a PR or branch using a specific reviewer's technical preferences. Use when the user says "/review-as <name> <pr-number-or-branch>", "review this as matt", "what would matt say about this PR", or needs code reviewed against a particular person's standards.
article-queue
by petestewart
View the article topic queue and optionally select a topic to generate an article. Use when the user invokes "/article-queue" or asks "show my article queue", "what articles are queued", or "list article topics".
article
by petestewart
This skill should be used when the user asks to "write an article", "create an article", "explain this topic", or invokes "/article <subject>". Generates self-contained HTML articles with inline SVG diagrams, proper structure, and polished styling. Handles plain text subjects, file paths (.md, .txt), and URLs as input.
article-add
by petestewart
Add a topic to the article queue for later generation. Use when the user invokes "/article-add <topic>" or says "add to article queue", "queue up an article about", or "save this topic for an article later".
QA
by petestewart
This skill should be used when the user asks to "run QA", "test the changes", "create a test plan", "verify the implementation", "QA the work", "check if it works", or needs to validate that completed work functions as expected. Generates TEST_PLAN.md and orchestrates test execution with bug fixing.
orchestrator
by petestewart
Drive a project from PLAN.md to completion by coordinating work, spawning focused subagents, and maintaining plan accuracy. You coordinate, prioritize, verify, and keep the plan accurate—not implementing large tasks yourself.
typora-markdown
by petestewart
Open markdown content in Typora for enhanced viewing. Use when creating plans, PR reviews, analysis reports, or substantial markdown content. Triggers on: plan files, /review-pr output, codebase analysis, documentation generation, or explicit user request to view in Typora.
project-planner
by petestewart
Generate a comprehensive PLAN.md file for a new project. Creates structured plans with tickets that an Orchestrator can execute.
subagent
by petestewart
Execute a single ticket from PLAN.md with precision. You are a focused implementation agent—receive a ticket, implement it, validate it, report results, then stop. Works with the orchestrator skill. (user)