// Iterates build and test until both are green, then captures hlint warnings without gating.
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.
Addresses every blocker finding from phases 12 and 13 and re-runs build and tests.
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'.
| name | 11-build-loop |
| description | Iterates build and test until both are green, then captures hlint warnings without gating. |
| kind | process |
| executor | haiku |
| model | claude-haiku-4-5-20251001 |
Drives the implementation to a state where cabal build all and cabal test are green. Hlint runs at the end to collect warnings for the PR body — it does not gate the loop.
./01-build/SKILL.md and follow it. Verify: .pipeline/build.log exists and exit was 0../02-test/SKILL.md and follow it. Verify: .pipeline/test.log exists and exit was 0../03-fix-iter/SKILL.md and follow it. Verify: at least one of build/test now passes that did not before, or the iteration counter advances../04-hlint/SKILL.md and follow it. Verify: .pipeline/hlint.log exists (may be empty or non-empty); exit is 0 unless hlint is missing.Walk these steps in order. If step 1 or 2 fails, jump to step 3 then back to step 1. After step 4 records the log, mark phase 11 complete regardless of how many warnings were captured.
.pipeline/hlint.log has been written.