# Factory Lookback

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle...

- Repository: https://github.com/BuilderIO/skills (4626 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add BuilderIO/skills --skill factory-lookback -g -a claude-code -y`
Codex: `npx skills add BuilderIO/skills --skill factory-lookback -g -a codex -y`
Cursor: `npx skills add BuilderIO/skills --skill factory-lookback -g -a cursor -y`
Gemini CLI: `npx skills add BuilderIO/skills --skill factory-lookback -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add BuilderIO/skills`

## Description

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Factory Lookback

Read `.agent-factory/config.yaml` and apply the optional
`skill_prompts.factory-lookback` entry as additional project guidance. Use this
workflow when asked to look back across a bounded period or when an enabled
`workflows.lookback` automation runs. Its purpose is to find patterns that
normal item-by-item flows keep missing or fixing only temporarily.

## Build a bounded evidence set

1. Confirm the configured sources, scope, time window, comparison period, and
   output policy before querying. Use only connected sources the host can read.
2. Enumerate the full configured range, follow every page or cursor, and record
   source filters, dates, counts, and unavailable or truncated sources. Do not
   report a complete lookback when coverage is partial.
3. Include relevant feedback, analytics or telemetry, runtime errors,
   recurring CI or review failures, repeated recovery attempts, replies to
   earlier information requests, and prior fixes marked shipped or verified
   when those records are available.
4. Cluster records by underlying symptom and affected boundary, not wording
   alone. Keep event counts, affected users or sessions, time range, versions,
   and distinct source links separate; do not infer identity or impact from
   unstable identifiers.

## Find the systemic cause

For each recurring cluster, trace representative reports to their original
source and inspect prior dispositions, commits, tests, and release evidence.
Check whether the symptom recurred after a claimed fix, appeared through a
sibling caller, or escaped because the normal workflow lacked a signal, owner,
verification step, or recovery path.

The rest: https://github.com/BuilderIO/skills/blob/HEAD/skills/factory-lookback/SKILL.md