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.
SkillScore91Maintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill91%
Checks it passed that the model alone missed
The output contains a dedicated Parking Lot section.
The response includes a separate Parking Lot section.
MOB-404 is explicitly designated under a Blocked Stories section with the missing credentials blocker details.
3 fixed17 passed either way0 still failing2 broke
Pass-rate lift
+5 pp
Tokens
+75%
Agent turns
0%
Response time
+25%
Model gemini-3.6-flashMeasured 8/18/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
We just finished refining epic user management stories for Sprint 14. Attached are our transcript notes listing the stories groomed, story points agreed upon, technical spikes needed, and key architectural choices made. Please compile a complete backlog refinement record outlining session details, story outcomes, open questions with owners, key decisions, immediate action items, blocked stories, and agenda ideas for the next grooming session.
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes an explicit Summary section.
Passed
Passed
The response includes a separate Parking Lot section.
Missed
Passed
case-02 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md62 lines3 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
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.