# Skill refinement
Use this method to turn review feedback into traceable improvements without losing original evidence or overstating what was validated. It owns the finding ledger and bounded revision record; it does not replace evaluation design, publish a package, or grant durable-write authority.
Capture and triage
Read `references/host-operations.md` before accessing feedback, a ledger, an artifact, or a revision record. Preserve the supplied source, verbatim feedback, date when available, affected behavior, and concrete location. Deduplicate by meaning, not title. If a host write is unavailable or unauthorized, return a proposed record update instead of claiming it was applied.
Select the operation from a clear request: capture for new feedback, status for a supplied fix or state change, and report for a read-only digest. Treat a file, paste, or feedback URL as capture unless the request says otherwise. If input could reasonably mean either a read or a write, ask before creating or changing a durable record.
Classify each finding as open, in progress, blocked, resolved, or won't do. Keep a stable ID, priority, owner when supplied, evidence, and history. A terminal status needs an explicit reason and supporting evidence; silence, public availability, or a repeated development test is not enough.
Make a bounded revision
1. Re-read the original feedback and identify the behavior, acceptance evidence, and any unresolved rights, policy, access, or decision issue. 2. Make the narrowest change that addresses the finding. Use `skill-authoring` only if the package contract or workflow needs redesign. 3. Add or update normal, missing-information, and boundary cases through `skill-evaluation`; preserve whether they are authored or executed. 4. Run authorized checks and inspect the actual output when the finding concerns a rendered or generated artifact. Source inspection alone is not sufficient for output behavior. 5. Record the revision or artifact identifier, evidence, remaining uncertainty, and proposed or applied status change in the finding ledger. When several authorized ledger changes belong to one feedback round, use an atomic batch operation only when the host documents one and returns its receipt. Otherwise return the complete proposed batch for confirmation; do not issue individual durable writes that could leave a partial round. Do not imply a commit, publication, or other durable action occurred unless the host confirms it.
Report and hand off
Report open items by priority, work in progress, blockers and needed decisions, recent resolutions with evidence, and next actionable work. Keep item-level feedback distinct from a separate coordination record. When a host exposes a contribution workflow, revise the existing contribution identity after a failed attempt; otherwise return a proposed revision and do not claim publication.
Load `references/capture.md`, `references/status.md`, `references/report.md`, or `references/workflow.md` for the selected operation.