refinement-logger

Generate resolution annotations and optional transcripts from refinement sessions.

Updated Aug 27, 2026

Search Tags:#refinement #logging #artifacts #review #transcripts #product-management #resolutions

Ready to run

npx skills add https://github.com/mattfuster/aisef-setup --skill refinement-logger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refinement-logger
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/refinement-logger
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill refinement-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and preserve the outcomes of review-driven refinement sessions so that the rationale behind changes survives the session. You produce two artifacts: resolution annotations on the review report (always), and a session transcript for precedent-setting decisions (when warranted).

Core Features & Use Cases

Automatic annotation of resolutions on review reports to document what changed and why.
Optional creation of a session transcript to preserve precedent-setting decisions for future sessions.
Works after refinement passes on requirements, blueprints, work orders, or any reviewed document to maintain a traceable history of decisions.

Quick Start

After finishing a refinement pass, say 'log refinement' to generate resolution annotations and an optional transcript.

Frequently Asked Questions about refinement-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I log refinement outcomes for reviewed requirements documents?▼

To log refinement outcomes, trigger the logger after a review pass to generate resolution annotations on the report and an optional transcript. This preserves what changed and why for requirements, blueprints, or work orders.

What is the best way to preserve the rationale behind changes after a review session?▼

Preserving review rationale is done by capturing resolution annotations and optional session transcripts. These artifacts document what changed and why, ensuring traceability and serving as precedent for future sessions.

Can I use refinement logging to maintain a traceable history of decisions for product management?▼

Refinement logging maintains a traceable history of decisions by automatically annotating resolutions on review reports. It applies to any reviewed document in product management, ensuring governance and durable precedent.

When do I need a session transcript for document refinement?▼

You need a session transcript when a refinement pass results in precedent-setting decisions. The logger creates this optional transcript alongside mandatory resolution annotations to preserve the session's governance value.

Does refinement logging work with blueprints and work orders or only requirements?▼

Refinement logging works with any reviewed document, including requirements, blueprints, and work orders. It triggers after any refinement pass to capture changes and generate traceable artifacts.

Why does my team lose the context of decisions made during refinement sessions?▼

Decisions lose context without formal logging. By generating resolution annotations and optional transcripts after refinement passes, the rationale behind changes survives the session for future traceability.