Retro Shaper — convert retrospective into prioritized Linear tasks

Takes raw retro outputs — exit interviews, comments, complaints, free-form retro notes — and renders them as an impact/effort matrix in a small web UI. Each card has a button that creates a Linear ticket auto-assigned to the most-likely owner.

Replaces the "Miro board → someone re-types into Linear next week → 40% of items lost" loop. Goes from retro session to executable backlog in the same hour.

1. Capture retro inputs as plain text (transcripts, form responses, pasted notes).
2. Skill shaper parses the text and clusters items by theme, tagging each with rough impact (S/M/L) and complexity (S/M/L).
3. Skill renders a static HTML page: graph view + sortable list. Team votes inline via thumbs.
4. Each item has a "Create in Linear" button calling the Linear API with: title, description, owner inferred from text, project, labels.
5. Run live at the end of the retro; click through prioritized items together.
6. Keep the rendered HTML as the retro artifact (replaces a Notion writeup).

• Owner-inference is wrong ~30% of the time on first run. Always show the suggested owner; never assign silently.
• Resist letting the agent score "impact in revenue." It will fabricate numbers. Use S/M/L only unless you give it concrete revenue baselines.