pre-implement
Skill2 starsChanged 4 months agoMITView on GitHub
Before implementing one wave slice, produce a pre-flight checklist: verify the prior wave's human gate is satisfied, confirm contracts consumed from prior Ground Reports match what was actually built, then read specs/ADRs/rules. Gate-only — never opens a branch or implements product code. Use when starting a wave, checking readiness for /loop-spec, or asked what to read before coding.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- scottcarlson/skillstheir own version, first seen Aug 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- scottcarlson/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- ground-specSkill
- initiative-feasibilitySkill
- learning-extractSkill
- loop-specSkill
- purge-initiative-artifacts-appSkill
- spec-draftSkill
- spec-implementation-planSkill
- spec-technical-reviewSkill
- ensure-repo-graphSkill
- post-product-questionsSkill
- prd-codebase-mapSkill
- review-product-questionsSkill
- commit-workspaceSkill
- create-board-ticketsSkill
- open-draft-prSkill
- prd-impact-mapSkill
- prd-qualitySkill
- prd-thinkSkill
- purge-initiative-artifacts-metaSkill
- review-findingsSkill
- update-documentsSkill
- validate-requirementsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 6 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
If not: stop and state which gate is unsatisfied.
- Very specific: line 37
Read rules_glob per the domain-filter approach in references/governance.md — not all files.
- Distinctive: line 39
Read relevant ADRs (keyword-match, then deep-read matched Accepted ADRs).
- Distinctive: line 45
Verify spend freshness: product-spec H1–H3 citations (and G2 spec merge when applicable) still match live durable roots.
- Very specific: line 67
When Implementation-Plan-{initiative}.md is still on the tree, validate §9 with scripts/workmanifest_contract.py / validate_workmanifest …
- Very specific: line 70
When the plan file is already gone (post–initiative-closure purge is initiative-end only — during waves the plan should still exist), …
- Very specific: line 78
read-only: If seed or bound wave head is missing/partial: stop, emit Forge / external-action readiness (e.g.
- Distinctive: line 94
If any check fails: stop — do not produce a pass checklist or write product code.
- Very specific: line 96
If a codegraph provider is available (MCP tool matching prayog-skills/references/codegraph-tool-contract.md, or a local CLI), prefer it for …
- Very specific: line 99
Always fall back to direct source_roots reads when unavailable — never block or change outcome selection on its absence.
- Very specific: line 114
When board/branch readiness is absent: prefer blocked (or needs-input if authority cannot be read) and fill handoff.forge / recommend the …
- Distinctive: line 178
Gate for W0 (first wave): no prior Ground Report exists.
- Distinctive: line 182
Cross-service / cross-module: when this slice calls a module from another service or a prior wave that has NOT yet been grounded, flag it …
- Very specific: line 196
When the invocation binds handoff_path (orchestrator / AgentRunner baton), also overwrite that path with the same handoff: envelope before …
- Very specific: line 201
Follow prayog-skills/references/forge-side-effects.md#content-producers when this stage's pin has forge.commit_workspace other than …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Resolve paths from
.harness/profile.yamlwhen present; else references/layout-defaults.md. - 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 priorwave-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. - Read
rules_globper the domain-filter approach in references/governance.md — not all files. - Read relevant ADRs (keyword-match, then deep-read matched Accepted ADRs).
- Never implement product code and never open/create a branch. Output the checklist (+ Forge readiness when board/branch readiness is absent).
- Cite concrete file paths for this repo and slice.
- Describe contracts in engineering terms — entry points, input/output shapes, invariants. Do not use language-specific syntax.
- 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).
- Resolve
check_commandandtest_command. Resolveverify_commandas the live script underlive_verify_dirwhen 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:coversincludeCAP-{nn}and/orJ-{nn}, non-emptyfixturesunderfixtures_dir, andhuman_observationswhen opaque. Resolveground_commandwhen applicable. If the plan/profile/AGENTS.md/tests_readmecannot supply a required command, stop with MISSING command. The human runs{verify_command}(+ look-ats) at checkpointwave-acceptance; this skill does not execute it. Layer policy: references/live-smoke-policy.md. Human accept ingress is GitHub labelwave-accepted(skills never apply it; ack includes look-ats when declared). - WorkManifest spend authority — prefer the board wave/EPIC issues
seeded from plan §9 as long-term intent (see
prayog-skills/references/workmanifest-contract.md). WhenImplementation-Plan-{initiative}.mdis still on the tree, validate §9 withscripts/workmanifest_contract.py/validate_workmanifestand 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. - 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-ticketsor wave-head binding) — do not invoke mutation from this skill. - Spec merge gate — before W0 (and before any
/loop-spec), confirm:- bound wave head context is the integration branch (
develop) or afeature/INIT-*-w{N}-*wave branch cut from it — not an openchore/*-spec-*Draft spec PR branch (wave head is bound by Forge/human context — this skill does not open it); - product spec
INIT-*.mdwith H1–H3 citations exists on the integration branch; prefer also verifying mergedImplementation-Plan-{initiative}.mdwhen still present (spec PR merge / G2); - the merged spec PR head carried
spec-lgtm(verify viagh pr viewon the closed spec PR: label present andmergeCommit/headRefOidmatches attestation or Approvecommit_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.
- bound wave head context is the integration branch (
- 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 directsource_rootsreads when unavailable — never block or change outcome selection on its absence.
Outcome selection
Map evidence to delivery outcomes only (pinned workflow.yaml):
| Outcome | When |
pass | Gate verdict PASS; WorkManifest contract clean for this wave; preflight artifact written; commands resolved; board seeded; prior wave approved (or W0 plan PE sign-off); wave head bound in Forge/human context |
needs-input | Authoritative source absent/unreadable (plan, Ground Report, commands, profile, §9 YAML) so readiness cannot be determined |
blocked | Authoritative source exists and shows an unsatisfied gate (WorkManifest contract fail, TASK missing exit proof, missing/applicable live-verification contract when P15 applies, prior wave missing Ground Report or not human_approved from wave-acceptance, board seed missing/partial, open Draft spec branch) |
stale | Product-spec H1–H3 / G2 / tip authority drift |
failed | Execution error while reading inputs, running the WorkManifest validator, or writing the preflight artifact |
When board/branch readiness is absent: prefer blocked (or needs-input if
authority cannot be read) and fill handoff.forge / recommend the matching
forge skill — never create the branch or tickets here.
Happy path: pass → loop-spec (no PR STOP here). On pass, fill
handoff.forge for commit_workspace so Forge publishes
Pre-Implement-{INIT}-W{N}.md onto the bound head_ref before coding.
Draft PR open happens later at wave-pr-action (after loop-spec).
Chain position
Illustrative only — transitions SSOT: pinned root workflow.yaml
(dispatch: orchestrated on this node). Procedure gates below still apply.
spec merge (spec-lgtm on head) → board seed (Forge) → wave issue In Progress
↓
/ground-spec (prior wave) → human_approved from prior wave-acceptance [Wn>0 only]
↓
/pre-implement ← YOU ARE HERE (gate-only)
gate: spec merged + board seeded + prior Ground Report + human_approved?
reads: Ground-Report-W{N-1}.md §Contracts produced
produces: Pre-Implement-{INIT}-W{N}.md
↓
Forge commit_workspace (checklist on head_ref) → /loop-spec
↓
Forge commit_workspace (code) → wave-pr-action (open_draft_pr)
↓
wave-acceptance (human smoke / P15 N/A; label wave-accepted)
↓
closeout: /learning-extract → /ground-spec → wave-signoff (merge only)Do not run on an open Draft spec PR branch (chore/*-spec-*). Coding
starts only after the spec package is merged to develop and a wave head is
bound outside this skill.
Read order
- Source and gate check — spec merge gate (rule 12); plan on integration
branch; plan sources CURRENT; impact-map scope current; WorkManifest
contract pass for this wave (rule 10); canonical commands resolved; board
issues exist (read-only);
as-built/implementation-status.mdprior wave =human_approved(Wn>0)? If any answer is no: stop with the matching outcome- Forge readiness when mutation is required elsewhere.
- Contracts consumed —
reports/Ground-Report-W{N-1}.md§Contracts produced: for each contract this wave depends on, read the entry point, input shape, output shape, and invariants as verified by the prior Ground Report. Confirm against actual source (scansource_roots) — not against spec alone. AGENTS.md— constitution pin, verify commands, process links- Domain-filtered MDC rules — per references/governance.md
- Relevant ADRs — keyword-match slice scope; read matched Accepted ADRs
- Initiative / slice spec — path from tracker Spec path or plan wave section
- Plan wave section / §9 WorkManifest —
reports/Implementation-Plan-{initiative}.mdW{N}: carry forward source digests, command contract, MDC notes, ADR notes, and from the canonical WorkManifest for this wave: TASK ids,depends_on, file scope, ImplementsREQ-*, exit criteria/proof, and waveverification(check/unit/live). Cite the board wave issue URL and list everyTASK-*for this wave in the checklist (projection only). tests_readme— fixed pointer; usescripts/verify_coverage_query.pyfor actual coverage lookups when the slice adds or changes verification- Codegraph provider — OPTIONAL — see
prayog-skills/references/codegraph-tool-contract.md
Gate for W0 (first wave): no prior Ground Report exists. The gate is the implementation plan PE sign-off (§0 of the plan). Confirm it is marked complete before producing the W0 checklist.
Cross-service / cross-module: when this slice calls a module from another service or a prior wave that has NOT yet been grounded, flag it explicitly in the checklist under "Unconfirmed contracts" — do not silently assume the interface.
Output format
Write {reports_dir}/Pre-Implement-{INIT}-W{N}.md using
references/output-template.md. Fill
concrete paths for this repo and slice.
Workflow handoff
- Append/emit the envelope from
prayog-skills/references/handoff-envelope.mdto the checklist output. Use stagepre-implement. - When the invocation binds
handoff_path(orchestrator / AgentRunner baton), also overwrite that path with the samehandoff:envelope before exit. Leaving the baton empty is a failed stage for automated consumers.artifact.pathremains the workspace skill output, not the baton path. Seeprayog-skills/references/handoff-envelope.md(Orchestrator baton). - Derive
next_candidates,human_checkpoint, andexternal_actionfrom pinned rootworkflow.yamlfor(stage: pre-implement, outcome)perprayog-skills/references/handoff-envelope.md(Derive from pinned workflow). Sethuman_checkpoint: trueonly when the resolved next node'stypeishuman-checkpoint— never because the artifact "should be reviewed." Setexternal_action: trueonly when next isexternal-action. - Happy path:
outcome: pass→ nextloop-spec(type: skill) →human_checkpoint: false,external_action: false. Pin hasforge.commit_workspace: required— fillhandoff.forgeforcommit_workspaceso Forge publishes the Pre-Implement artifact onto the bound wave head before/loop-spec. Do not open the Draft PR here. - Follow
prayog-skills/references/forge-side-effects.md#content-producerswhen this stage's pin hasforge.commit_workspaceother thandisabledor next is anexternal-actionwithforge.requires— fillhandoff.forge/ recommend the matching/forgeskill; do not treat local CLI as skill success.
Transitions: pinned root workflow.yaml for this stage (SSOT). Human or
agent may run this skill; orchestrators may auto-dispatch when
dispatch: orchestrated and trigger + handoff authorize. Same legality rules
for both invoke paths.
Record the board issue URL/id, wave TASK-* list, and resolved command
contract in signals. next_candidates never authorize invoke.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

