skills/create-issue-rpi/SKILL.md
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.
npx skillsauth add jjjona/agentic-work create-issue-rpiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
00-docs/issues/ exists in the current project, write the issue there.00-docs/ does not exist, ask the user where to write the issue.git config --get user.name in the current repo.YYYY-MM-DD.YYYY-MM-DD-issue-slug.md in the target directory.date and last_updated, the git user for owner, and the confirmed issue title.---
date: YYYY-MM-DD
owner: "<name>"
repository: portal
topic: "<Issue Title> — Issue Brief"
status: draft
last_updated: YYYY-MM-DD
---
# <Issue Title> — Issue Brief
## Problem
- Current behavior:
- Pain:
- Desired outcome:
## Scope
- In scope:
- Out of scope:
## UX / i18n
- Routes/screens:
- Key states (loading/empty/error):
- i18n: all strings via `dictionaries/*`
## Data / sources
- System of record:
- Read/write paths:
- Source mappings (if any):
## Rules / validation
- R1:
- R2:
## Testing
- Unit tests:
- Manual QA steps:
## Open questions
- Q1:
- Q2:
development
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").
testing
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.
documentation
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".
documentation
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 ...".