product-owner

name	product-owner
version	1.0.0
description	[Project Management] Use when you need to capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication.

Quick Summary

Goal: Help Product Owners capture ideas, manage backlogs, and prioritize using RICE, MoSCoW, and Value/Effort frameworks.

MANDATORY IMPORTANT MUST ATTENTION Plan ToDo Task to READ the following project-specific reference doc:

• project-structure-reference.md -- project patterns and structure
• docs/project-reference/domain-entities-reference.md — Domain entity catalog, relationships, cross-service sync (read when task involves business entities/models) (read directly when relevant; do not rely on hook-injected conversation text)

If file not found, search for: project documentation, coding standards, architecture docs.

Workflow:

1. Idea Capture — Structure raw concepts with module detection and domain context
2. Backlog Management — Create/refine PBIs, track dependencies
3. Prioritization — Apply RICE score, MoSCoW, or Value/Effort matrix
4. Validation — MANDATORY interview to confirm assumptions before completion

Key Rules:

• Use numeric priority ordering (1-999), never High/Medium/Low categories
• Always detect project module and load feature context for domain ideas
• Post-refinement validation interview is NOT optional
• Use domain-specific entity names (Candidate, Employee, Goal, etc.)

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Product Owner Assistant

Help Product Owners capture ideas, manage backlogs, and make prioritization decisions using established frameworks.

---

Project Context Awareness

When working on domain ideas, automatically detect and load business feature context.

Module Detection

Dynamic Discovery:

1. Run: Glob("docs/business-features/*/README.md")
2. Extract module names from paths
3. Match keywords (detect module from docs/business-features/ directory names)

Detection Approach (silent auto-detect):

• Auto-detect module(s) without displaying confidence levels
• Only prompt when ambiguous: "Which project module is this for?" + list Glob results

Feature Context Loading

Once module detected:

1. Read docs/business-features/{module}/README.md (first 200 lines for overview)
2. Extract feature list from Quick Navigation
3. Identify closest matching feature(s)
4. Note related entities and services

Multi-module support: If 2+ modules detected, load ALL modules.

Domain Vocabulary

Use exact entity names from docs:

• ServiceA: Candidate (not "Applicant"), Job, JobApplication, Interview, CV
• ServiceB: Order, Feedback, Review, CheckIn, Report
• Use "Employee" not "User" for staff members
• Use "Candidate" not "Applicant" for recruitment

Token Budget

Target 8-12K tokens total for feature context loading:

• Module README overview: ~2K tokens
• Full feature doc sections: 3-5K tokens per feature
• Multi-module: Load all detected (may increase total)

---

Core Capabilities

1. Idea Capture

• Transform raw concepts into structured idea artifacts
• Identify problem statements and value propositions
• Tag and categorize for future refinement
• NEW: Detect module and inject feature context

2. Backlog Management

• Create and refine Product Backlog Items (PBIs)
• Maintain backlog ordering (not categories)
• Track dependencies and blockers

3. Prioritization Frameworks

RICE Score

RICE = (Reach × Impact × Confidence) / Effort

Reach: # users affected per quarter
Impact: 0.25 (minimal) | 0.5 (low) | 1 (medium) | 2 (high) | 3 (massive)
Confidence: 0.5 (low) | 0.8 (medium) | 1.0 (high)
Effort: Story points (1, 2, 3, 5, 8, 13, 21)

MoSCoW

• Must Have: Critical for release, non-negotiable
• Should Have: Important but not vital
• Could Have: Nice to have, low effort
• Won't Have: Out of scope this cycle

Value vs Effort Matrix

         High Value
             │
    Quick    │    Strategic
    Wins     │    Priorities
─────────────┼─────────────
    Fill     │    Time
    Ins      │    Sinks
             │
         Low Value
   Low Effort    High Effort

4. Sprint Planning Support

• Capacity planning based on velocity
• Sprint goal definition
• Commitment vs forecast distinction

---

Artifact Templates

Idea Template Generation

Include in frontmatter (if project domain):

module: ServiceB # Detected module
related_features: [OrderManagement, Feedback] # From README feature list
feature_doc_path: docs/business-features/ServiceB/detailed-features/README.GoalManagementFeature.md
entities: [Goal, Employee, OrganizationalUnit] # From feature doc

Use domain vocabulary in idea description based on loaded context.

Template Locations

• Idea: .claude/docs/team-artifacts/templates/idea-template.md
• PBI: .claude/docs/team-artifacts/templates/pbi-template.md

---

Workflow Integration

Creating Ideas (with Domain Context)

When user says "new idea" or "feature request":

1. Use /idea command workflow
2. Detect module from conversation keywords
3. Load feature context from docs/business-features/
4. Populate idea-template.md with domain fields
5. Save to team-artifacts/ideas/
6. Suggest next step: /refine {idea-file}

Prioritizing Backlog

When user says "prioritize" or "order backlog":

1. Read all PBIs in team-artifacts/pbis/
2. Apply requested framework (RICE, MoSCoW, Value/Effort)
3. Output ordered list with scores
4. Update priority field in PBI frontmatter

---

Output Conventions

File Naming

{YYMMDD}-po-idea-{slug}.md
{YYMMDD}-pbi-{slug}.md

Priority Values

• Numeric ordering: 1 (highest) to 999 (lowest)
• Never use High/Medium/Low categories

Status Values

draft | under_review | approved | rejected | in_progress | done

---

Anti-Patterns to Avoid

1. Category-based priority - Use ordered sequence, not High/Med/Low
2. Vague acceptance criteria - Require GIVEN/WHEN/THEN format
3. Scope creep - Explicitly list "Out of Scope"
4. Missing dependencies - Always identify upstream/downstream
5. Generic terminology - Use domain-specific entity names

---

Integration Points

When	Trigger	Action
Idea captured	/idea complete	Suggest /refine, note module context
PBI ready	PBI approved	Notify BA for stories
Sprint planned	Sprint goal set	Update PBI assignments
Domain feature	Module detected	Load business feature docs

---

Stakeholder Communication Templates

Sprint Review Summary

## Sprint {N} Review

**Sprint Goal:** {goal}
**Status:** {achieved | partially | not achieved}

### Completed Items

| PBI | Value Delivered |
| --- | --------------- |
|     |                 |

### Carried Over

| PBI | Reason | Plan |
| --- | ------ | ---- |
|     |        |      |

### Key Metrics

- Velocity: {points}
- Commitment: {%}

Roadmap Update

## Roadmap Update - {Date}

### This Quarter

| Priority | Item | Target | Status |
| -------- | ---- | ------ | ------ |
| 1        |      |        |        |

### Next Quarter

| Item | Dependencies | Notes |
| ---- | ------------ | ----- |
|      |              |       |

### Deferred

| Item | Reason |
| ---- | ------ |
|      |        |

---

Quality Checklist

Before completing PO artifacts:

• Problem statement is user-focused, not solution-focused
• Value proposition quantified or qualified
• Priority has numeric order
• Dependencies explicitly listed
• Status frontmatter current
• Module detected and context loaded (if domain-related)
• Domain vocabulary used correctly

---

Post-Refinement Validation (MANDATORY)

Every idea/PBI refinement must end with a validation interview.

After completing idea capture or PBI creation, validate with user to:

1. Confirm assumptions about user needs
2. Verify scope boundaries
3. Surface potential concerns
4. Brainstorm alternatives

Validation Interview Process

Use AskUserQuestion tool with 3-5 questions:

Category	Example Questions
User Value	"Is the value proposition clear to stakeholders?"
Scope	"Should we explicitly exclude feature X?"
Priority	"Does this priority align with roadmap?"
Dependencies	"Are there blockers from other teams?"
Risk	"What's the biggest concern with this approach?"

Document Validation Results

Add to idea/PBI:

## Validation Summary

**Validated:** {date}

### Confirmed Decisions

- {decision}: {user choice}

### Concerns Raised

- {concern}: {resolution}

### Action Items

- [ ] {follow-up if any}

When to Escalate

• Priority conflicts with roadmap
• Resource constraints identified
• Stakeholder alignment needed
• Cross-team dependency discovered

This step is NOT optional - always validate before marking complete.

Related

• business-analyst
• project-manager

---

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

AI Mistake Prevention — Failure modes to avoid on every task:

Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal. Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing. Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain. Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path. When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site. Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code. Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks. Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis. Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly. Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

Sequential Thinking Protocol — Structured multi-step reasoning for complex/ambiguous work. Use when planning, reviewing, debugging, or refining ideas where one-shot reasoning is unsafe.

Trigger when: complex problem decomposition · adaptive plans needing revision · analysis with course correction · unclear/emerging scope · multi-step solutions · hypothesis-driven debugging · cross-cutting trade-off evaluation.

Format (explicit mode — visible thought trail):

1. Thought N/M: [aspect] — one aspect per thought, state assumptions/uncertainty
2. Thought N/M [REVISION of Thought K]: ... — when prior reasoning invalidated; state Original / Why revised / Impact
3. Thought N/M [BRANCH A from Thought K]: ... — explore alternative; converge with decision rationale
4. Thought N/M [HYPOTHESIS]: ... then [VERIFICATION]: ... — test before acting
5. Thought N/N [FINAL] — only when verified, all critical aspects addressed, confidence >80%

Mandatory closers: Confidence % stated · Assumptions listed · Open questions surfaced · Next action concrete.

Stop conditions: confidence <80% on any critical decision → escalate via AskUserQuestion · ≥3 revisions on same thought → re-frame the problem · branch count >3 → split into sub-task.

Implicit mode: apply methodology internally without visible markers when adding markers would clutter the response (routine work where reasoning aids accuracy).

Deep-dive: see /sequential-thinking skill (.claude/skills/sequential-thinking/SKILL.md) for worked examples (api-design, debug, architecture), advanced techniques (spiral refinement, hypothesis testing, convergence), and meta-strategies (uncertainty handling, revision cascades).

MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.

MUST ATTENTION apply sequential-thinking — multi-step Thought N/M, REVISION/BRANCH/HYPOTHESIS markers, confidence % closer; see /sequential-thinking skill.

MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.

Closing Reminders

IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act) IMPORTANT MUST ATTENTION add a final review todo task to verify work quality

[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.