pre-implement

Pre-implement

Produce the pre-flight checklist for one wave slice. This skill is gate-only: it never opens a branch and never implements product code — even if the user asks after the checklist. Implementation belongs to /loop-spec. Content skills write locally and emit Forge readiness; they do not commit, push, branch, open PRs, label, create issues, or merge.

Canonical artifact: {reports_dir}/Pre-Implement-{INIT}-W{N}.md (prayog-skills/references/artifact-write-contract.md).

NON-NEGOTIABLE

1. Resolve paths from .harness/profile.yaml when present; else references/layout-defaults.md.
2. Gate check first — before reading anything else, confirm the prior wave's Ground Report exists and its as-built row is human_approved (set at prior wave-acceptance, not at signoff). If not: stop and state which gate is unsatisfied. Do not produce a checklist for a wave whose predecessor is not approved.
3. Read rules_glob per the domain-filter approach in references/governance.md — not all files.
4. Read relevant ADRs (keyword-match, then deep-read matched Accepted ADRs).
5. Never implement product code and never open/create a branch. Output the checklist (+ Forge readiness when board/branch readiness is absent).
6. Cite concrete file paths for this repo and slice.
7. Describe contracts in engineering terms — entry points, input/output shapes, invariants. Do not use language-specific syntax.
8. Verify spend freshness: product-spec H1–H3 citations (and G2 spec merge when applicable) still match live durable roots; board wave issue exists for this W{N}. Stop on authority drift. Do not require Implementation-Plan source-freshness / plan-file digest as long-term SSOT (plan is walk-time; may be purged at initiative closure).
9. Resolve check_command and test_command. Resolve verify_command as the live script under live_verify_dir when the wave plan triggers P15 (new/material product surface) — FAIL the gate on bare N/A or unit-only (make test / {test_command}). When live is applicable, require journey/capability-shaped intent: covers include CAP-{nn} and/or J-{nn}, non-empty fixtures under fixtures_dir, and human_observations when opaque. Resolve ground_command when applicable. If the plan/profile/AGENTS.md/tests_readme cannot supply a required command, stop with MISSING command. The human runs {verify_command} (+ look-ats) at checkpoint wave-acceptance; this skill does not execute it. Layer policy: references/live-smoke-policy.md. Human accept ingress is GitHub label wave-accepted (skills never apply it; ack includes look-ats when declared).
10. WorkManifest spend authority — prefer the board wave/EPIC issues seeded from plan §9 as long-term intent (see prayog-skills/references/workmanifest-contract.md). When Implementation-Plan-{initiative}.md is still on the tree, validate §9 with scripts/workmanifest_contract.py / validate_workmanifest and fail closed on contract / incomplete TASK exit / P15 live gaps as today. When the plan file is already gone (post–initiative-closure purge is initiative-end only — during waves the plan should still exist), reconstruct TASK/REQ/exit/live intent from board issue bodies projected at seed plus product-spec REQs — do not invent ids. Board text is projection of the approved manifest, not a second libre authority.
11. Confirm board seed: EPIC issue exists, every declared wave issue exists, and waves are sub-issues of the EPIC on the programme board (governance project_board.name). Board/branch/PR state is read-only. If seed or bound wave head is missing/partial: stop, emit Forge / external-action readiness (e.g. recommend /create-board-tickets or wave-head binding) — do not invoke mutation from this skill.
12. Spec merge gate — before W0 (and before any /loop-spec), confirm:
    • bound wave head context is the integration branch (develop) or a feature/INIT-*-w{N}-* wave branch cut from it — not an open chore/*-spec-* Draft spec PR branch (wave head is bound by Forge/human context — this skill does not open it);
    • product spec INIT-*.md with H1–H3 citations exists on the integration branch; prefer also verifying merged Implementation-Plan-{initiative}.md when still present (spec PR merge / G2);
    • the merged spec PR head carried spec-lgtm (verify via gh pr view on the closed spec PR: label present and mergeCommit/headRefOid matches attestation or Approve commit_id);
    • board tickets seeded (wave issues exist per rule 11). If any check fails: stop — do not produce a pass checklist or write product code.
13. If a codegraph provider is available (MCP tool matching prayog-skills/references/codegraph-tool-contract.md, or a local CLI), prefer it for impact/dependency questions when reading contracts consumed. Always fall back to direct source_roots reads when unavailable — never block or change outcome selection on its absence.