food-chain-monitor

# Food Chain Monitor ## What This Is A **delta battle** — the ongoing health-check companion to `food-chain-ideation`. Run it after pivots, after major feature additions, after market changes. It tests ONLY what changed since the last battle. Everything that already survived stays untouched. ## What This Is NOT - **Not a full food chain battle.** That is `food-chain-ideation`. If you want to stress-test an idea from scratch, go there. - **Not a replacement for the Battle Log.** This skill REQUIRES a prior Battle Log. If the user does not have one, redirect them: *"You need to run food-chain-ideation first to establish a baseline Battle Log. I can't monitor changes to something that hasn't been battle-tested yet."* ## Input Requirements | Input | Required | Description | |-------|----------|-------------| | **Battle Log** | YES | From a prior `food-chain-ideation` session. Contains the original idea, evolved idea, apex predator, patches, and UAS. | | **What Changed** | YES | A plain-language description: "we pivoted from X to Y", "we added feature Z", "competitor launched W", "market shifted because of Q". | | **Action Log** | NO | From `apex-to-action`. If provided, the monitor checks whether executed actions are still valid post-change. | If the user provides no Battle Log, do NOT proceed. Redirect to `food-chain-ideation`. --- ## Step 1 — Delta Analysis Identify exactly what is new. Do not re-litigate settled assumptions. ```markdown ## Delta Analysis | Field | ...