Skill

po-workflows

Product Owner workflows — ticket refinement, sprint planning, requirements analysis, impact assessment for Repo

Install

Run in your terminal

npx claudepluginhub johwer/marketplace --plugin claude-toolkit

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.5k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.5k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

140.3k

Stats

Stars0

Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Ticket Refinement Checklist

Before a ticket is READY:

Clear user story: "As a [role], I want [goal], so that [benefit]"
Acceptance criteria (Given/When/Then format)
Edge cases identified and documented
UI/UX: mockups or wireframes attached (if applicable)
API contract defined (if backend change)
Impact on other services identified
Data migration needs assessed
i18n: translation keys planned (5 languages: sv, en, da, no, fi)
Estimated story points (1-4 scale)

User Story Template

As a [HR administrator / employee / system admin],
I want to [specific action],
So that [business value].

**Acceptance Criteria:**
- Given [context], when [action], then [result]
- Given [context], when [action], then [result]

**Out of scope:**
- [What this ticket does NOT include]

**Dependencies:**
- [Other tickets or services needed]

Sprint Planning

Estimation Scale (Repo convention)

1 point — Simple, well-understood, single file/service change
2 points — Moderate complexity, 2-3 files, one service
3 points — Cross-service, needs design decisions, database changes
4 points — Complex, multiple services, significant risk — consider splitting

Capacity Planning

Total team points per sprint: [configurable]
Buffer for bugs/support: ~20% of capacity
Max 1 four-pointer per sprint per developer

Impact Analysis Workflow

When evaluating a feature request:

Identify affected services

# Search for related code in the monorepo
grep -r "EntityName" services/ --include="*.cs" -l
grep -r "relatedEndpoint" apps/web/src/ --include="*.ts" -l

Check API contracts
- Which endpoints change?
- Are there breaking changes?
- Who consumes these endpoints?
Database impact
- New tables or columns?
- Data migration needed?
- Performance impact on existing queries?
Frontend impact
- New pages or components?
- State management changes?
- RTK Query API generation needed?
Cross-cutting concerns
- Authorization/ServiceC changes?
- Email/notification templates?
- Translation keys (TranslationService)?
- ServiceE/reporting impact?

Jira Quick Reference

# View ticket
acli jira workitem view PROJ-1234

# Update ticket status
acli jira workitem update PROJ-1234 --status "In Progress"

# Add comment
acli jira workitem comment PROJ-1234 "Analysis complete — see AC below"

# Download attachments
bash ~/.claude/scripts/jira-download-attachments.sh PROJ-1234

Recommended External Skills

For enhanced product management:

Spec-Flow — AI-powered specification-driven development with Jira/Confluence integration
PICT Test Designer — Pairwise/combinatorial test case generation from requirements