jjjona
8 verified skills12 total stars
implement
Implement an approved plan from 00-docs/03-plans — execute phases in order, pausing for human verification after each phase (don't chain phases unless told to). Use when the user asks to implement, execute, or follow a plan, or says "start phase X", "continue with the plan", "continue with phase X".
documentation2
plan
Create a detailed, testable, phased implementation plan through research and iteration — working interactively, with explicit sign-off on the phase breakdown before writing the full plan (never dump a complete plan in one pass). Use when the user asks to plan, create a plan, or wants a structured plan before coding.
testing2
research
Document and explain an existing codebase without critique or recommendations. Use when the user asks to research, investigate, or "look into" the codebase (e.g. "research how auth works", "look into X").
development2
create-issue
Capture a bug report or feature request as a structured issue file under 00-docs/01-issues. Use when the user reports a problem or asks to "create an issue for ...".
documentation2
create-issue-rpi
Create a new issue markdown file from a template when users report problems or ask to create an issue ("i found these problems", "saw an issue", "these things are wrong", "create an issue for"). Use when an agent should capture an issue in the current project under 00-docs/issues with the required frontmatter and sections.
documentation1
implement-rpi
Implement approved plans from 00-docs/plans, execute phases, and verify success criteria. Use when the user asks to implement a plan, execute a plan, or follow a written plan, or says "start phase X", "start working on the plan", "continue with the plan", "continue with phase X", or similar.
testing1
plan-rpi
Create detailed, testable implementation plans through research and iteration. Use when the user asks to plan, create a plan, propose an implementation plan, or wants a structured plan before coding.
testing1
research-rpi
Document and explain existing codebases without critique or recommendations. Use when the user asks to research, investigate, or "look into" codebases (e.g., "research", "research this", "research the codebase for", "look into").
development1