identify-fragile-systems

# Identify fragile systems Built to run unattended once a day. It strings together four skills, and each step's details live in that skill's SKILL.md: - `system-history`: collecting history and scoring systems; - `jira-refactor-findings`: duplicate matching, sightings, and filing; - `refactor-plan`: the fragile vs fast-moving judgment, and the plan file; - `fragility-common`: the run directory and the plan format. ```bash H=.agents/skills/system-history/scripts J=.agents/skills/jira-refactor-findings/scripts P=.agents/skills/refactor-plan/scripts S=.agents/skills/identify-fragile-systems/scripts RUN=<YYYY-MM-DD> # defaults to today's UTC date ``` ## Hard rules - Planning only. Never change product code, open a PR, or push. - Never run blob-reading git commands. See `fragility-common`. - Check Jira for an existing ticket before investigating a system. - A plan needs a named repeated mechanism, taken from diffs you read. A high fix count alone is not a finding. - File only `high` or `medium` confidence plans. A `low` finding goes in `decisions.json`, so a later night can confirm it. - Stop on any nonzero exit from a preflight and report it. Exit 2 is never a pass. ## Steps 1. **Preflight**: `$H/doctor.ts` and `$J/doctor.ts`. For a `run-link` warning, set `FRAGILITY_RUN_URL`. 2. **Collect**: `$H/collect.ts --run $RUN` (24 h window, 21-day lookback). 3. **Triage**: `$H/analyze.ts --run $RUN`. It writes `analysis.md` and `targets.json`, with the hot systems, their scores, and triage verdicts. 4. **Dedup early**: `$J/jira-match.ts --run $RUN`. For each hot system matched to an open or declined ticket, run `$J/jira-upsert.ts --run $RUN --key <KEY> --system <system> --apply` and don't re-plan it. The exceptions: - The ticket was resolved as fixed. That's a recurrence: plan it and upsert it, which opens a linked ticket. - The diffs show a different root problem. Plan it under a new slug, and name the related ticket. 5. **Investigate** the unmatched systems in score order. Focus on `likely-fragile`, `mixed`, and high-scoring `settling`. Skip `coupled` unless the coupling is the defect. Skip `likely-fast-moving` and `insufficient-signal` unless their diffs say otherwise. For each system: - read 3 to 6 fix PRs with `$H/pr.ts`; - read the current top files; - decide using `.agents/skills/refactor-plan/references/rubric.md`. Fan out one read-only sub-agent per system when you can. Give it the system's `analysis.md` section and the rubric, and ask for the mechanism, the PR numbers, and a verdict. 6. **Plan**: one plan per root problem, which may span several systems. Scaffold it with `$P/new-plan.ts`, then fill it in as `refactor-plan` describes. 7. **Record decisions**: give every hot system you didn't plan or sight a one-line reason in `<dataDir>/$RUN/decisions.json`. 8. **File**: `$J/jira-upsert.ts --plan <file>` (a dry run), then add `--apply`. If it reports overlapping tickets, read their diffs: pass `--key KEY` when the plan is that ticket's problem, or `--distinct-from KEY,...` when it isn't. 9. **Summarize**: `$S/summarize.ts --run $RUN`. Exit 1 means some hot system is still undecided, so go back to step 7. ## Final report Write 3 to 6 lines covering: - tickets created and sighted, with links; - plans held back by the cap; - any check that could not run. Use 🟢 when nothing is undecided and every applied upsert succeeded. Use 🟡 when something was held back or a check exited 2, and say what.