Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Scan the codebase, write a PRD, and open a GitHub issue.
/po <prompt> - Create a GitHub issue from the given feature description/po <prompt> --priority <P0|P1|P2|P3> - Create issue with explicit priority/po - Ask user what to build, then create the issue/po amend <issue_number> <summary> - Append a revision to an existing issueIf no --priority is given, ask the user which priority to assign.
Conventional format:
feat(<context>): <short description>
Examples:
feat(blog): add article pinningfeat(export): add rss feed generationfix(import): handle rate limiting from dev.to apiRules:
## Overview
What we're building and why.
## Problem Statement
What user problem does this solve?
## Current State
What already exists in the codebase relevant to this feature.
## Requirements
- [ ] R-1: Description
## Technical Approach
- Affected modules
- Data flow changes
- Database changes if any
## Acceptance Criteria
Given/When/Then scenarios.
## Out of Scope
What we're explicitly NOT doing.
gh issue create \
--title "feat(<context>): <description>" \
--body "$(cat <<'EOF'
<PRD content>
EOF
)" \
--label "prd" \
--label "P2: medium"
Report the issue URL to the user when done.
When called with /po amend <issue_number> <summary>, append a revision to the existing issue. The original PRD is immutable — never edit or overwrite it.
Append a ## Revision <N> block with changes, updated requirements, and removed/deferred items.
/po <prompt> -> GitHub issue -> /dev -> /review -> /commit -> /pr
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.
The English summary is being prepared. Showing the original description.
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
The English summary is being prepared. Showing the original description.
Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review.
The English summary is being prepared. Showing the original description.
Deep code review - Elixir idioms, Phoenix patterns, architecture, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, code smells.
The English summary is being prepared. Showing the original description.