capture-milestone-principle-updateslisted

# capture-milestone-principle-updates This is the finish-time harvester of the answer-principle-learning loop. Over a milestone, each `/answer-open-question` records a decision and commits it with the decision's **rationale in the commit body** (subject `Manual-answer: <Short Title>`). This skill reads that finite, known-up-front set of commits **once the milestone is finished** and distills from them the generalizable answering principles that the recommendation advisor can apply. It is the **sole writer** of `milestones/answer_decision_principles.md` (a single project-wide file at the `milestones/` root, **above** any one milestone, so principles accumulate across milestones). ## Usage ``` /capture-milestone-principle-updates ``` Takes no arguments. It is an **optional** follow-up run *after* `/finish-current-milestone` has already recorded the milestone and cleared the current-milestone pointer to `none`. > This skill writes **only** the principle store at the fixed path > `milestones/answer_decision_principles.md`. It does **not** touch any milestone's `requirements.md`. > When a pass distills a new or revised principle it **commits** that principle-store edit itself > (step 5); a pass that distills none changes no file and commits nothing. ## Workflow ### 1. Resolve the just-finished milestone — NOT via `get-current-milestone` By the time this skill runs, `/finish-current-milestone` has already cleared the current-milestone pointer to `none`, so the usual `share