max/pm-template
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
df667e0db8272d1d768738db989bb8962b4158ce
pm-template/skills/epics-standards/references/epic-fields-checklist.md
Max Mayfield df667e0db8 v2: Forge Console + Open WebUI artifacts + Docker 
- web/: Local chat UI (Express + WS → Codex bridge)
- openwebui/: Preset, pipelines, knowledge manifest
- Dockerfile + docker-compose.yml
- Updated README with 3 frontend options
- CLI-agnostic: works with Codex, Claude Code, Kiro, Gemini
2026-02-27 06:56:34 +00:00

1.2 KiB
Raw Blame History

RP Epic Field Checklist

Standard page: https://reltio.jira.com/wiki/spaces/PM/pages/2688385025/PM+Standards+Epics

Use this checklist during epic create/update.

Core fields

  • Summary (short Jira shorthand)
  • Description (business outcome + impact)
  • Type of Effort
  • Fix Version (or N/A when not yet planned)
  • Status

Product narrative fields

  • Problem Statement / Why
  • Solution / What
  • Persona / Who
  • Value Statement

Planning and delivery fields

  • Confidence Level
  • Path to Green (required when Confidence is Medium/Low for must-have epics)
  • Availability in Release
  • Planned Release
  • T-Shirt Size
  • Tier
  • Initiative

Ownership and dependencies

  • Product Lead
  • Engineering Lead
  • UX Lead
  • Execution Team
  • Execution Team Dependency

Go-to-market and governance

  • For documentation tickets: set Affected Documentation to a documentation target (for example Help Portal) and never No
  • Doc Required
  • Pricing Required
  • Security Review Required
  • Does this change PCC?
  • Tags (including Must Have when applicable)
  • Demo Link (when available)

Integration check

  • Aha! Reference is present and linked through the RP integration path.
Reference in New Issue View Git Blame Copy Permalink