Decision Summary

A discussion that ran long, with options raised, rejected and revived, leaves its owner holding the pieces rather than the picture. This skill hands them the picture: everything decided so far, in words they would use themselves, seen from what they will get and from how it will work.

It is not a step in the workflow. It gates nothing, moves no plan, and ends nothing. If the user keeps discussing afterwards, the discussion simply continues, and they can ask for it again later.

Where it comes from

• The discussion as it stands now. Where the user changed their mind, the latest ruling is the decision. Earlier versions appear only under Changed along the way, and only when the user might still remember the old one.
• The decision document, if one exists (docs/discussions/), and its What the User Sees section in particular. Where it and the discussion disagree, say so under Needs you; do not pick one quietly.
• Nothing else. Add no idea that was not discussed. If a gap has to be filled for the summary to make sense, fill it and mark it (my assumption, not discussed).