apply-key-decisions

name	apply-key-decisions
description	Propagate a call's fork stage-change decisions into EIP data files. Use when a call's key_decisions.json records EIPs proposed/considered/scheduled/etc. for a fork (e.g. "PFI for Hegota") and the EIP JSONs need their forkRelationships updated to match.

Apply key decisions to EIP fork relationships

A call's key_decisions.json records stage_change decisions — e.g. ACDE #240 proposed five EIPs for inclusion (PFI) in Hegota. This skill reads those decisions and, for each affected EIP, updates src/data/eips/{id}.json so its forkRelationships reflect the new fork status, and attempts to add the presenter as a champion.

Schema

• Types: src/types/eip.ts (ForkRelationship, Champion, KeyDecision).
• Example EIP with populated relationships: src/data/eips/7805.json.
• stage_change.to values map 1:1 onto statusHistory[].status (Proposed, Considered, Scheduled, Included, Declined, Withdrawn). "PFI" = Proposed, "CFI" = Considered, "SFI" = Scheduled.

Step 1: Gather input

Ask the user for the call ref as {type}/{number} (e.g. acde/240). From it:

1. Resolve the artifact dir by glob: public/artifacts/{type}/*_{number}/ (folder is {date}_{numberPadded}, e.g. 2026-07-02_240).
2. Read key_decisions.json from that dir. It's the source of truth for what changed.