ground-spec

Ground spec

Validate implementation against the product spec REQs assigned to this completed wave (plan / WorkManifest TASK implements lists) and actual repo artifacts — not every future REQ in the full product spec, and not PRD text alone. Produce a Ground Report that the next wave's /pre-implement consumes as a contract baseline.

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}/Ground-Report-{SPEC}-W{N}.md (prayog-skills/references/artifact-write-contract.md). Checks: references/checks.md (G1–G10). Ids: prayog-skills/references/id-conventions.md (GF-* for findings).

NON-NEGOTIABLE

1. Resolve paths from .harness/profile.yaml or references/layout-defaults.md. Include tests/** in scope when mapping evidence.
2. Run the repo's automated ground check when {ground_command} is defined in the harness profile. Include full output in the report. If {ground_command} is not defined, perform manual REQ validation by reading source_roots and tests/** directly.
3. Check every REQ-* assigned to this wave via plan / WorkManifest TASK rows — map each to a verifiable artifact (test result, entry point, module boundary, verify script output). Do not require coverage of REQs owned only by future waves. Use engineering terms: "entry point", "module boundary", "output shape" — not language-specific terms.
4. Consume approved plan/manifest intent plus actual loop/unit evidence and human accept (Wave-Execution-*, unit results, wave-accepted / wave-acceptance). Optional/legacy Live-Verify-* is not required. Cite layers separately.
5. Check cross-spec contracts: modules from this wave may only consume interfaces from prior waves as documented in those waves' Ground Reports.
6. Check boundary rules per ADRs and domain-filtered MDC rules (G5/G6).
7. Do not mark spec human_approved — already set at wave-acceptance (only approval signal). This skill prepares the merge package for wave-signoff (merge/publish only).
8. Populate the Contracts Produced section — structured handoff for /pre-implement of the next wave. Without it, the chain is broken.
9. Cite learning ids — when {reports_dir}/Learning-Extract-{initiative}-W{N}.md exists, add a Learning cited table of L-* ids (do not re-author learning SSOT).
10. Discrepancy / blocker ids use stable GF-* — cite REQ-* in the row, not as the blocker primary key. Do not reuse feasibility FF-*.
11. Write Ground Report and as-built updates locally; prepare the exact-head merge package for wave-signoff; pin routes to wave-done-action then wave-signoff (merge only). Never commit or merge from this skill. As-built writes follow the split in prayog-skills/references/artifact-write-contract.md — Implementation-Status-{INIT}.md for detail, one index row in implementation-status.md for the pointer; never append a new table to the shared index.
12. If a codegraph provider is available (MCP tool matching prayog-skills/references/codegraph-tool-contract.md, or a local CLI), prefer it for cross-spec contract / boundary questions. Always fall back to direct source_roots reads when unavailable — never block or change outcome selection on its absence.