product-on-purpose/iterate-refinement-notes
skills/iterate-refinement-notes/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add product-on-purpose/pm-skills iterate-refinement-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 4:07 AM146.9s3 files scanned
SKILL.md
- 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.
- license:
- Apache-2.0
- phase:
- iterate
- version:
- 2.0.0
- updated:
- 2026-01-26
- category:
- coordination
- frameworks:
- [triple-diamond, lean-startup, design-thinking]
- author:
- product-on-purpose
<!-- 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
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.
Related Skills
product-on-purpose/utility-pm-workflow-orchestrator
tools
VerifiedTrustedCommunity
Run an ordered sequence of pm-skills against one input via the pm-workflow-orchestrator sub-agent, pausing for go/no-go and stopping on a failed or empty step. Dispatches natively on Claude Code with the pm-skills plugin (invokes @agent-pm-skills:pm-workflow-orchestrator, which delegates each step through the Skill tool); on non-Claude clients (Codex CLI, Cursor, Windsurf, Copilot, Gemini CLI) reads agents/pm-workflow-orchestrator.md and walks the loop inline after a tool-capability pre-flight. Explicit invocation only; never fires proactively. EXPERIMENTAL on all non-Claude clients and on the native path until smoke-tested; run --dry-run first.
264SKILL.mdUpdated Jun 4, 2026
product-on-purpose/foundation-prioritized-action-plan
development
VerifiedTrustedCommunity
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of Constraints), prioritized questions and open decisions, a ranked action plan with the critical effort plus follow-ons, risks and pre-mortem, copy/paste prompts for downstream pm-skills, and an evidence map. Builds a source ledger and cites exact input quotes; refuses High-confidence plans for Complex or Chaotic situations. Use when you want the critical next effort and how to execute it.
264SKILL.mdUpdated Jun 4, 2026
product-on-purpose/deliver-y
testing
VerifiedTrustedCommunity
--- name: deliver-y phase: deliver --- # Deliver Y Fixture skill for phase-map and phase-router tests.
264SKILL.mdUpdated Jun 4, 2026
product-on-purpose/define-x
testing
VerifiedTrustedCommunity
--- name: define-x phase: define --- # Define X Fixture skill for phase-map and phase-router tests.
264SKILL.mdUpdated Jun 4, 2026