// Addresses every blocker finding from phases 12 and 13 and re-runs build and tests.
| name | 14-fix-findings |
| description | Addresses every blocker finding from phases 12 and 13 and re-runs build and tests. |
| kind | leaf |
| executor | sonnet |
| model | claude-sonnet-4-6 |
Reads the implementation security and performance findings and resolves every blocker.
.pipeline/findings-12.json.pipeline/findings-13.jsondocs/architecture/<adr-number>-<slug>.mdblocker: true → verify: list captured.nix develop --command cabal build all && nix develop --command cabal test → verify: both pass.Assumptions:
blocker: true) must be fixed in this phase. Non-blockers are tracked but not blocking._ params, let..in/where, $, <>/++ for strings, raw String/IO/Either. The rule is scoped to files the fix already touches; nothing else gets reformatted. See ../references/nhcore-context.md#boy-scout-rule.If any assumption fails, refuse — do not guess.
.pipeline/findings-12.json and .pipeline/findings-13.json.blocker: true.file:line, read the surrounding code, and apply a targeted fix.nix develop --command cabal build all. If it fails, apply one more targeted fix and retry — bounded to a total of 3 attempts (1 initial + 2 retries). If still failing, refuse and surface the build log.nix develop --command cabal test. If it fails, apply one more targeted fix and retry — bounded to a total of 3 attempts (1 initial + 2 retries). If still failing, refuse and surface the test log.python3 .claude/skills/feature-pipeline-preview/scripts/pipeline.py complete 14.All blockers resolved; build and tests green; phase 14 marked complete.
file:line reference → refuse: "blocker is unactionable".Implements the feature per the architecture doc using nhcore-first, NeoHaskell style.
Reads build and test logs, identifies the root cause, and edits implementation files to fix it.
Iterates build and test until both are green, then captures hlint warnings without gating.
Use when implementing a new NeoHaskell feature end-to-end — from ADR draft through PR merge — and the work needs the structured 17-phase pipeline with ADR, security and performance reviews (each grounded against feature complexity and the Jess persona), outside-in test design, build loop, and PR/CI handling. Triggers on 'run feature pipeline', 'feature pipeline', 'start pipeline', 'implement feature', 'new NeoHaskell feature', 'implement issue
NeoHaskell code implementation guide. Use when implementing features, writing tests, build/test loops, or any task requiring NeoHaskell code. Handles pipeline phases 7-9 (tests, implementation, build loop), 12-13 (fix reviews, final build), and 16 (fix bot comments).
NeoHaskell coding style reference and enforcement rules. Load when writing, reviewing, or modifying any Haskell code in the NeoHaskell project. Triggers on 'NeoHaskell style', 'NeoHaskell conventions', 'how to write NeoHaskell', 'code style', 'style guide'.