// Implements the feature per the architecture doc using nhcore-first, NeoHaskell style.
| name | 10-implementation |
| description | Implements the feature per the architecture doc using nhcore-first, NeoHaskell style. |
| kind | leaf |
| executor | sonnet |
| model | claude-sonnet-4-6 |
Replaces the phase 9 stubs with a real implementation that follows the architecture doc exactly.
docs/architecture/<adr-number>-<slug>.md — architecture doc.docs/architecture/<adr-number>-<slug>-tests.md — test spec (read-only reference).Ghc prefix as last resort → verify: imports list is auditable.nix develop --command cabal build all succeeds.Assumptions:
|>) over nesting, do+let over let..in/where, case...of over guards in arg lists, qualified imports, [fmt|...|] for strings, Task/Result not IO/Either, no $, no point-free.Strict enabled globally — never add ! annotations.String/IO/Either, $, let..in/where, <>/++). The rule does not apply to test bodies/assertions (still immutable) but it does apply to helpers, imports, and fixtures the phase legitimately touches. See ../references/nhcore-context.md#boy-scout-rule.If any assumption fails, refuse — do not guess.
Text, Array, Result, Task, EventStore, etc.) before any external package.Ghc prefix (e.g. import qualified Data.Map.Strict as GhcMap).nix develop --command cabal build all to confirm compilation.git diff --name-only HEAD -- 'core/test/' 'testbed/tests/' (and any other test directories the architecture doc names) must return empty. Refuse if any match — tests are immutable in phase 10.python3 .claude/skills/feature-pipeline-preview/scripts/pipeline.py complete 10.Stubs replaced with real implementations; nix develop --command cabal build all green; phase 10 marked complete.
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.
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'.