Implement Feature

Implement Feature

Execute one admitted package graph without weakening TDD, stable package identity, path ownership, or the blind-source firewall.

Required contracts

Before acting, read:

• FEATURE-WORKFLOW-ROUTING.md;
• FEATURE-WORKFLOW-STATE.md; and
• FEATURE-IMPLEMENTATION-CONTRACT.md.

Also follow runtime-local approved-plan, graph-plan, agent-boundary, review, worktree, and PR contracts.

Admission

Require one exact user-identified approved plan or exact released plan-feature state. A supplied plan must pass the shared graph parser plus approval, authoritative Jira snapshot paths/digests, repository freshness, path ownership, stack, and blind-handoff checks before binding. A released state is revalidated and atomically claimed through claim. Every mutation uses the exact state path through ../_shared/scripts/feature_workflow_state.py.

If neither input exists, stop without initializing, interviewing, or planning. Never claim a state whose recorded owner is build-feature. Enter only on a direct human request under the routing contract's human front door; refuse invocation by a spawned agent or another skill.

Pipeline

1. Ask state for dependency-ready WPn packages and run them one lane at a time, in the returned longest-gated-chain order, since Cursor admits exactly one live controlled claim. Create each runnable non-final package on its approved branch from the frozen base with a verified no-push worktree receipt.
2. For each package, run exact selected-layer RED, then send its decoded approved blind_green.handoff verbatim to the blind source writer together with the parser's resolved interface payload for that package, verifying both digests. Run its independent gate and phase-review audit; create and record exactly one approved checkpoint commit.
3. After all non-final checkpoints, preflight and deterministically restack them in stack_order, preserving and recording original/restacked identities.
4. Create the sole final-integration package at the assembled tip. Run its own RED/GREEN, final-only unit/CLI/docs/changelog work, gate, audit, checkpoint, and aggregate integration gate.
5. Reserve one exact report in the final worktree and run one report-only deep-review --gates --base <frozen-target-sha>. Completed gate failure ends with no remote write; passing gates open publication even when findings remain.
6. Record GitHub preflight, push every finalized branch in stack order, create every PR initially draft bottom-up, and recover an unrecorded successful create only through its exact create-pr resume receipt. Register the stack with one gh stack link over the ordered PR URLs; verify exact number/URL/title/head/base/draft/body JSON; and optionally verify authorized ready transitions with the same fields.

Only checkpointed dependencies release downstream packages. Every dispatch, gate, commit, push, and PR record names the stable WPn. Never leak planning, Jira, tests, runner output, coverage, siblings, or target-base material into a blind writer payload.

Revision and finish

Before terminal review, invalid plan assumptions or already-GREEN RED require recording the affected packages as blocked and a stop. Terminal findings do not loop back. Return exact plan and state identities, package evidence, restack map, review body/path/classification, residual risks, and the complete verified stacked-PR map or exact no-publication reason.

Resources

• REFERENCE.md — admission, package firewall, stack, and publication gates.
• EXAMPLES.md — supplied plan, released state, DAG, and terminal outcomes.
• writing style — normative prose rules and the pre-save self-check for every human-read artifact this skill produces.