What is Iterate Refinement Notes?

A structured capture of refinement outcomes, including decisions, estimates, questions, blockers, and actions.

Who should own and update notes?

Typically the facilitator or note-taker; owners of follow-up items should be added.

Where are notes stored and how are they shared?

Saved in the project repository or wiki and distributed to the team; used before sprint planning.

Iterate Refinement Notes

Scanned

npx machina-cli add skill product-on-purpose/pm-skills/iterate-refinement-notes --openclaw

Files (1)

SKILL.md

2.7 KB

name: iterate-refinement-notes description: 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. phase: iterate version: "2.0.0" updated: 2026-01-26 license: Apache-2.0 metadata: category: coordination frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose

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

Instructions

When asked to document refinement notes, follow these steps:

Record Session Metadata Note the date, attendees, and duration. This helps track who was part of decisions and when discussions happened.
List Stories Discussed For each story, capture the outcome: estimated points, refined status, key discussion points, and any modifications made to the original scope.
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.
Capture Decisions Made Record any scope decisions, technical approaches agreed upon, or priority changes. These decisions are valuable context that gets lost without documentation.
Note Action Items Any follow-up work needed before stories are sprint-ready: mockups to create, technical spikes to run, stakeholders to consult.
Flag Blocked Stories Clearly identify stories that can't proceed until blockers are resolved. Include what the blocker is and who owns resolution.
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.

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
Notes are understandable to someone who wasn't there

Examples

See references/EXAMPLE.md for a completed example.

Source

git clone https://github.com/product-on-purpose/pm-skills/blob/main/skills/iterate-refinement-notes/SKILL.mdView on GitHub

Overview

Iterate Refinement Notes records the outcomes of backlog refinement sessions, including stories refined, estimates, questions raised, decisions made, and action items. It serves as a quick reference for absent teammates and preserves the history of how ideas evolve into sprint-ready work.

How This Skill Works

During or after refinement, document session metadata (date, attendees, duration), capture each story's outcome (estimates, refined status, key points), and record questions, decisions, and action items. The notes follow the template at references/TEMPLATE.md and are shared with the team, ensuring blockers are flagged and next-session planning is clear.

When to Use It

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 has been refined
When stories require re-refinement due to time elapsed

Quick Start

Step 1: Begin a notes document during refinement, recording date, attendees, and duration
Step 2: For each story, capture outcome, estimates, status, and key points
Step 3: Flag blockers, assign owners, and share using references/TEMPLATE.md

Best Practices

Record session metadata: date, attendees, duration
List each story discussed with outcome: estimates, status, modifications
Document questions with assigned owners and due dates
Flag blocked stories with blockers and owners for resolution
Review notes for clarity and share promptly with the team

Example Use Cases

Product team logs grooming outcomes for devs and QA
Notes record scope decisions and the chosen technical approach
Blocked stories are flagged with owner and resolution date
New engineers use notes to understand backlog context
Notes inform sprint planning with refined stories and estimates

Frequently Asked Questions

Add this skill to your agents