implementlisted
Install: claude install-skill lamuniercosta/dotnet-agent-harness
## User Input
```text
$ARGUMENTS
```
## Prerequisites
- Human gate 1 passed (spec/plan/tasks approved). If acceptance tests were generated (opt-in), Human gate 2 (Gherkin spot-checked) also passed
- `FEATURE_DIR/acceptance/*.feature` exists **only if** the optional Gherkin stage ran — acceptance tests are opt-in for now
- Read the `agent-pipeline` rule (`.cursor/rules/agent-pipeline.mdc`) for stage order and handoff rules
Resolve feature directory via `.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks`.
## Goal
Implement the feature until all tests pass. **Test-first ordering is not required** — write acceptance bindings, unit tests, and production code in any order, but complete all before handoff.
## Required Reads
- `tasks.md` — execution order, task IDs, file paths
- `plan.md` — architecture, tech stack, layer rules
- `spec.md` — acceptance intent
- `acceptance/*.feature` — executable scenarios *(only if the optional Gherkin stage ran)*
- `.specify/memory/constitution.md` — non-negotiable constraints
- `contracts/` and `quickstart.md` if present
## Implementation Targets
| Artifact | Location |
|---|---|
| Step definitions | `tests/<Project>.AcceptanceTests/Steps/` |
| Unit tests | `tests/<Project>.UnitTests/` |
| Integration tests | `tests/<Project>.IntegrationTests/` |
| Production code | `src/` per plan.md |
Feature files are synced from `specs/**/acceptance/` into `Features/` at build time. The AcceptanceTests project exc