apply-decisionslisted

# Apply Decisions Canonical consumer algorithm for the `DECISIONS_CONTEXT` index passed by orchestrators. The index lists each ADR/PF entry with ID, truncated title, status, and area — not the full body. Use this skill to surface the right decisions and pitfalls for your task without loading the entire corpus. ## Iron Law > **VERBATIM IDs ONLY — NEVER FABRICATE** > > Cite only IDs that appear verbatim in DECISIONS_CONTEXT. If an ADR/PF ID is not > in the index, do not cite it. If an entry looks relevant but you haven't Read its > full body, do not cite it. Fabricated citations are worse than no citations. --- ## 5-Step Algorithm ### Step 1: Scan the index Read through all entries in `DECISIONS_CONTEXT`. The index format is: ``` Decisions (N): ADR-001 Title truncated to 60 chars [Active] ADR-002 Another decision [Active] Pitfalls (M): PF-004 Background hook god scripts [Active] — src/assets/scripts/hooks/foo.cjs PF-011 DECISIONS_CONTEXT fan-out [Active] — src/assets/commands/... ADR-NNN entries live in {worktree}/.devflow/learning/decisions.md PF-NNN entries live in {worktree}/.devflow/learning/pitfalls.md Read the relevant file and locate the matching `## ADR-NNN:` or `## PF-NNN:` heading for the full body. ``` ### Step 2: Identify plausibly-relevant entries From the index, identify entries whose title or area plausibly overlaps with: - The files you are modifying or reviewing - The category of issue you are addressing (e.g., erro