iterate-refinement-notes SKILL.md skillA
iterate-refinement-notes from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/iterate-refinement-notes@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/iterate-refinement-notes/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed Jun 11, 2026
- First version recorded
- Jan 27, 2026
- Size
- 3,418 bytes
- Repository stars
- 790
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- 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** …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/iterate-refinement-notes@sha256:45254b71dceb925dThe line at the top of this page pins the label v2.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ot4hdvkrryqfq32n)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jan 27, 2026 and Jun 11, 2026, about one every 34 days. Its first recorded version is graded C and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-06-11 | 9b5dbf9 | 3,418 B | A | view · diff |
| v2.0.0 | 2026-05-20 | be1352b | 2,810 B | A | view · diff |
| v2.0.0 | 2026-04-23 | 8ab0f81 | 2,804 B | A | view · diff |
| v2.0.0 | 2026-03-25 | 0ab0a60 | 2,808 B | A | view · diff |
| git:20260127.ac99454 | 2026-01-27 | ac99454 | 2,808 B | C | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3418 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ot4hdvkrryqfq32n GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/iterate-refinement-notes GET https://markdownregistry.com/api/v1/blob/45254b71dceb925dce0246413d568dd4861d88dff909645b3a4f7a925a87c4db
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.