product-retro

Redirects per-session retrospective entries to the After Action Report template in wrap-up.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill product-retro-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-retro
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/product-retro
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill product-retro-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose lessons learned when sessions end without a written record, and older retro-log conventions no longer match the current reporting format. This Skill preserves the mandatory per-session retrospective rule while pointing agents to the current After Action Report format and location. ## Core Features & Use Cases - Supersession pointer: Explains that since 2 Sep 2026 the per-session retro entry is the After Action Report, loaded via the wrap-up skill. - Field mapping table: Maps the four legacy 1.x retro fields (what happened, learning or decision, friction, carried forward) onto the corresponding After Action Report sections. - Placement rules: Directs the report to a comment on the Linear ticket the session worked, with an optional vault copy under 00 handover, and declares retro-log.md files read-only archives. - Use Case: An agent finishing a product work session invokes /product-retro and is routed to wrap-up's aar-template.md to write the mandatory After Action Report as a Linear comment. ## Quick Start Ask the agent to write the retro entry for the session just completed, and it will load wrap-up and produce an After Action Report comment on the ticket.

Frequently Asked Questions about product-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product retro entry after a work session?▼

Write an After Action Report using the wrap-up skill's aar-template.md and post it as a comment on the Linear ticket the session worked. The standalone retro-log format was superseded on 2 Sep 2026.

What replaced the product-retro retro-log format?▼

The After Action Report in wrap-up 2.0.0 replaced it. The four legacy fields map onto its sections: what happened becomes Actual, learnings become Sustain or The gap, friction becomes Watch-outs, and carried forward becomes Improve actions.

Can I still append to an existing retro-log.md file?▼

No. Every retro-log.md is an archive as of 2 Sep 2026 and must be read for history only, never appended. New entries go to Linear as After Action Report comments.

Is the per-session retrospective still mandatory?▼

Yes. The rule that every session that does product work writes a report before ending survives unchanged; only the shape and location changed to the After Action Report on the ticket.

Where is the vault copy of the After Action Report stored?▼

When the vault is mounted, the copy lives at 00 handover/aar-YYYY-MM-DD-[thread].md. Linear remains the system of record for the report.