Iterate Refinement Notes

This captures what happened in your backlog refinement sessions so the decisions don't evaporate by sprint planning. It walks through documenting which stories got estimated, what questions need answers, who owns the blockers, and what technical decisions were made. The format is straightforward: session metadata, story outcomes, open questions with owners, and action items. Honestly, the value is less about the template and more about forcing the discipline to write things down while they're fresh. If your team constantly re-litigates decisions or forgets why stories were scoped a certain way, this gives you a paper trail. Works during the session or as a recap afterward.

skills.sh installs: 753
GitHub stars: 794
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add product-on-purpose/pm-skills --skill iterate-refinement-notes --agent claude-code

Installs into .claude/skills of the current project.

Files

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