refine

To update project documentation after a development session, distill session learnings and decisions into concise, actionable edits for files in docs/. The skill reviews recent changes and maps them to existing documentation.

The best way to distill session learnings into technical docs is to review change lists, identify exact files to update, and draft small surgical edits. New files or structural changes are proposed conservatively before creation.

Yes, this documentation editing tool requires approval before creating new files or applying structural changes. It proposes targeted edits conservatively and reports updated file paths with short summaries after changes are approved.

Yes, you can use this skill to propose structural changes to your docs directory. It identifies necessary updates, drafts focused edits, and requests approval before creating new files or altering the existing documentation structure.

Session-to-docs distillation handles recent code changes by reading recent session notes or change lists to identify affected files in docs/. It then drafts focused, surgical edits to ensure documentation accurately reflects the discovered patterns and outcomes.

You should use a project docs refinement tool versus manual editing when a development, planning, or review session concludes and you need to surgically map session outcomes, decisions, and discovered patterns into existing technical documentation.