Iterate Refinement Notes
Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.
MCP get_skill({ skillId: "refinement-notes-cc303a3a" })Use this skill with your agent
Create a free account and connect via MCP
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Refinement Notes Refinement notes capture the outcomes of backlog refinement (grooming) sessions.what was discussed, what was estimated, and what decisions were made. They serve as a quick reference for team members who missed the session and a historical record of how stories evolved from idea to ready-for-sprint. ## When to Use - During refinement sessions to capture decisions in real-time - After refinement to share outcomes with absent team members - When onboarding new team members to explain backlog context - Before sprint planning to review what's been refined - When stories need re-refinement due to time elapsed ## When NOT to Use - You need the stories themselves written -> use `deliver-user-stories` - You need a general meeting summary, not a backlog-refinement record -> use `foundation-meeting-recap` - You are running the retrospective ceremony -> use `iterate-retrospective` - Refined stories need their failure scenarios enumerated -> use `deliver-edge-cases` ## Instructions When asked to document refinement notes, follow these steps: 1. **Record Session Metadata** Note the date, attendees, and duration. This helps track who was part of decisions and when discussions happened. 2. **List Stories Discussed** For each story, capture the outcome: estimated points, refined status, key discussion points, and any modifications made to the original scope. 3. **Document Questions Raised** Questions that couldn't be answered in the session need owners and due dates. Don't let them disappear.they often block sprint planning. 4. **Capture Decisions Made** Record any scope decisions, technical approaches agreed upon, or priority changes. These decisions are valuable context that gets lost without documentation. 5. **Note Action Items** Any follow-up work needed before stories are sprint-ready: mockups to create, technical spikes to run, stakeholders to consult. 6. **Flag Blocked Stories** Clearly identify stories that can't proceed until blockers are resolved. Include what the blocker is and who owns resolution. 7. **Plan Next Session** Note what should be refined next and any preparation needed. ## Output Format Use the template in `references/TEMPLATE.md` to structure the output. Complete notes fill every template section: Session Info; Summary; Stories Refined; Stories Summary Table; Questions Raised; Decisions Made; Action Items; Blocked Stories; Parking Lot; and Next Session. ## Quality Checklist Before finalizing, verify: - [ ] All discussed stories have outcomes recorded - [ ] Open questions have owners assigned - [ ] Decisions are captured with enough context - [ ] Blocked stories are clearly flagged - [ ] A reader who missed the session can tell each story's outcome and what happens next without asking ## Examples See `references/EXAMPLE.md` for a completed example.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Deliver User Stories
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.
Utility Update Pm Skills
Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.
Develop Adr
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.