friction-retrospectivelisted

# Friction Retrospective ## Purpose / When to Activate Activate to aggregate and analyze friction captured during delivery. This skill reads `## Friction Log` sections from delivery artefacts and detects patterns that warrant promotion to durable memory (conventions, decisions, rule updates). **Recommended triggers (conventions, not rules):** - **Per-Epic:** when an Epic is marked done - **Monthly:** alongside `memory-refresh` - **Incident:** if a single Story generates 3+ friction events **Constraint:** Only the Discovery Agent may invoke this skill. Delivery agents capture friction; Discovery analyzes it. --- ## Process 1. **Scope resolution** — determine which artefacts to scan: - If `epic` filter: scan artefacts matching `{epic_id}S*` - If `date_range` filter: scan artefacts within date range (from frontmatter `created_at`) - If `type` filter: scan all artefacts but only extract entries matching the specified friction type - If no filter: scan all artefacts (full retrospective) 2. **Friction extraction** — for each artefact containing a `## Friction Log`: - Parse the table rows - Tag each entry with: Story ID (from filename), date (from frontmatter), artefact type (impl-report / qa-report / micro-delivery-report) 3. **Pattern detection** — analyze extracted entries: - Group by `type` (ac-ambiguity, missing-context, tool-failure, etc.) - Count frequency per type - Identify thematic clusters within each type (e.g., multiple `missing-conte