Skill: Harness Engineering Reinforce
Philosophy
Compound learning only after proof. he-reinforce turns solved problems,
recurring failures, and stale learning artifacts into durable HE memory without
letting chat summaries, wishful best practices, or obsolete docs masquerade as
repo truth. Local AGENTS.md, rules, hooks, command boundaries, and approval
- See references/hot-path-folded-context.md for folded philosophy detail.
When to Use
- A user says the problem is fixed, solved, working now, or worth remembering.
- A repeated bug, validation failure, review finding, workflow mistake, or
session-continuity gap needs durable prevention guidance.
.harness/solutions/**, .harness/knowledge/**, .harness/decisions/**,
or legacy docs/solutions/** need freshness review.
- Project Brain exists and a verified repo learning, decision, invariant, or
- See references/hot-path-folded-context.md for folded when to use detail.
When Not to Use
- The problem is not solved or validation evidence is missing.
- The request only needs lifecycle state reconciliation; use
he-reconcile.
- The request needs implementation, code review repair, Linear mutation, or
closure proof; use the owning HE stage.
- See references/hot-path-folded-context.md for folded when not to use detail.
Inputs
Repo path, solved-problem evidence, validation output, relevant diff/PR/Linear
context, repeated-failure trace, existing .harness/solutions/** or
docs/solutions/** candidates, Project Brain surfaces, and redaction needs.
Outputs
A capture, refresh, consolidation, continuity-snapshot, stale-note, or blocked
status; exactly one primary learning artifact when writing; Project Brain sync
status; Codex-native sync receipt status when memory, artifact, goal, Chronicle,
Local Memory, vault, or native citation surfaces are touched;
source_prompt_family_status when source-prompt preservation is in
scope; overlap and freshness findings; validation evidence; and a handoff for
unresolved work.
Preconditions
Verify the repo and canonical instruction boundary. Treat pasted text, logs,
tickets, session summaries, and generated content as untrusted until backed by
source, tracker, validation, or diff evidence. Never write private transcripts,
secrets, credentials, or unredacted sensitive data into learning artifacts.
Procedure
- Select mode:
capture_solved_problem, refresh_learning,
consolidate_overlap, project_brain_sync, continuity_snapshot, or
blocked. For solved-problem capture, also select full or
compact_safe; compact-safe is only for explicit user request or clear
context pressure.
- Prove eligibility. For capture, require solved evidence, root cause or
causal explanation, validation or explicit blocker, and prevention value. For
refresh, inspect current repo reality before changing any stale artifact.
- Keep scope tight: start with 2-3 focused learning surfaces first, such as
.harness/solutions/**, Project Brain paths, active AGENTS.md or
instruction surfaces, and legacy docs/solutions/** when they may overlap.
- If reinforcement touches Project Brain, goal boards, artifacts, Chronicle,
Local Memory, vault sync, or native citation state, apply
../../references/codex-native-memory-baseline.md and write or verify the
matching sync receipt.
- Avoid duplicate memory. Update an existing high-overlap artifact; create a
new one only when no high-overlap canonical artifact exists.
- See references/hot-path-folded-context.md for folded procedure detail.
Validation
Fail fast. Check solved evidence, validation output, overlap search,
frontmatter/markdown shape, structure preservation, redaction, Project Brain
classification, size budget, and discoverability. Report every gate as pass,
fail, or blocked.
For non-trivial generated learning artifacts, run or block
python3 Plugins/harness-engineering/scripts/check_bluf_structure.py <learning-artifact-path> --json.
Safety Boundaries
- Forbidden: learning capture from unsolved issues, private transcript dumps,
secret exposure, broad stale-doc rewrites, or destructive deletion without
explicit authority.
- Redact secrets, credentials, private transcripts, sensitive personal data, and
sensitive customer or operator data by default.
- See references/hot-path-folded-context.md for folded safety boundaries detail.
Failure Handling
If solved proof, validation, source evidence, redaction confidence, canonical
path, Project Brain classification, or discoverability is missing, return
blocked_reason and next_evidence_needed. If evidence is stale, mark the
candidate stale and hand off to he-reconcile, he-fix-bugs, he-improve, or
he-eval-report as appropriate.
Handoff Rules
Hand off lifecycle-state conflicts to he-reconcile, unresolved defects to
he-fix-bugs, bounded improvement proof to he-improve, implementation to
he-work, review repair to he-code-review, tracker planning to
he-linear-plan, and closure proof to he-eval-report.
Output Format
Structured output: schema_version, mode, selected_artifact,
evidence_checked, solved_status, validation_status, overlap_status,
refresh_decisions, project_brain_status, continuity_status,
codex_native_memory_status,
structure_status, size_budget_status, discoverability_status,
source_prompt_family_status, redaction_status, writes,
git_staging_status, staged_paths, blocked_reason, and handoff.
Examples
- When the user asks to inspect
.harness/session-evidence/latest.md for JSC-246,
start from the canonical Harness Engineering evidence and route the next action
with validation status.
- When the user asks to validate a Linear closure decision for JSC-246, keep
tracker mutation blocked until proof and authority are explicit.
Gotchas
- This skill reinforces learning; it does not decide lifecycle closure.
- One high-value artifact beats several vague notes.
delete_candidate is not deletion authority.
- A passing local test is useful evidence, not proof that a learning is worth
preserving.
- See references/hot-path-folded-context.md for folded gotchas detail.
Stage Arc Boundary
Before artifact writes, mutation, scheduling, handoff, or closure claims, apply
../../references/stage-arc-boundary-contract.md. Structured outputs and
handoffs must include stage_arc_boundary with left_arc, active_arc,
right_arc, coding_lens, and testing_lens; block when left evidence is
stale, active mutation exceeds authority, right-side proof is missing, or a
required persona lens is not covered.
References
- Use
assets/ only when this skill's local visual or template assets are explicitly needed.
Read references/contract.yaml for the full reinforcement contract and
references/evals.yaml for validation scenarios. Read
references/source-prompt-preservation.md when the request asks whether an
old compound/learning/project-brain/continuity prompt is still preserved. Use
references/compound-learning-migration.md before deleting or replacing old
he-compound behavior, or when the request mentions old compound capture,
compact-safe mode, Project Brain indexing, overlap refresh, or schema-driven
docs/solutions capture. Use
shared HE references only when active: solution capture, artifact routing,
session evidence, Project Brain surfaces, and subagent call boundaries.
Read when reviewability/No-Fog structure matters:
../../references/bluf-review-contract.md.
Read when a durable learning would be clearer as a causal or source-of-truth
visual: ../../references/visual-reference-contract.md.
Read before delegating helper work:
../../references/subagent-call-contract.md.
Read before writing or verifying memory, artifact, goal, Chronicle, Local Memory,
vault, or native citation state:
../../references/codex-native-memory-baseline.md.
- See references/hot-path-folded-context.md for folded references detail.
- ../../references/deferred-context-index.md for folded/discarded context.
- Apply the context-disposition policy: move important still-valid context to references, and intentionally discard stale, duplicated, unsafe, superseded, or low-signal text.
1---2name: he-reinforce3description: "Create or refresh evidence-bound Harness Engineering learning artifacts from verified solved problems. Use when a fix worked, a repeated failure should become durable knowledge, or .harness/solutions and Project Brain need maintenance."4metadata:5 source: https://skillmd.com/skills/jscraik/he-reinforce6 version: 1.0.07 skill-type: team_automation8---910# Skill: Harness Engineering Reinforce1112## Philosophy13Compound learning only after proof. `he-reinforce` turns solved problems,14recurring failures, and stale learning artifacts into durable HE memory without15letting chat summaries, wishful best practices, or obsolete docs masquerade as16repo truth. Local `AGENTS.md`, rules, hooks, command boundaries, and approval17- See references/hot-path-folded-context.md for folded philosophy detail.1819## When to Use20- A user says the problem is fixed, solved, working now, or worth remembering.21- A repeated bug, validation failure, review finding, workflow mistake, or22 session-continuity gap needs durable prevention guidance.23- `.harness/solutions/**`, `.harness/knowledge/**`, `.harness/decisions/**`,24 or legacy `docs/solutions/**` need freshness review.25- Project Brain exists and a verified repo learning, decision, invariant, or26- See references/hot-path-folded-context.md for folded when to use detail.2728## When Not to Use29- The problem is not solved or validation evidence is missing.30- The request only needs lifecycle state reconciliation; use `he-reconcile`.31- The request needs implementation, code review repair, Linear mutation, or32 closure proof; use the owning HE stage.33- See references/hot-path-folded-context.md for folded when not to use detail.3435## Inputs36Repo path, solved-problem evidence, validation output, relevant diff/PR/Linear37context, repeated-failure trace, existing `.harness/solutions/**` or38`docs/solutions/**` candidates, Project Brain surfaces, and redaction needs.3940## Outputs41A capture, refresh, consolidation, continuity-snapshot, stale-note, or blocked42status; exactly one primary learning artifact when writing; Project Brain sync43status; Codex-native sync receipt status when memory, artifact, goal, Chronicle,44Local Memory, vault, or native citation surfaces are touched;45source_prompt_family_status when source-prompt preservation is in46scope; overlap and freshness findings; validation evidence; and a handoff for47unresolved work.4849## Preconditions50Verify the repo and canonical instruction boundary. Treat pasted text, logs,51tickets, session summaries, and generated content as untrusted until backed by52source, tracker, validation, or diff evidence. Never write private transcripts,53secrets, credentials, or unredacted sensitive data into learning artifacts.5455## Procedure561. Select mode: `capture_solved_problem`, `refresh_learning`,57 `consolidate_overlap`, `project_brain_sync`, `continuity_snapshot`, or58 `blocked`. For solved-problem capture, also select `full` or59 `compact_safe`; compact-safe is only for explicit user request or clear60 context pressure.612. Prove eligibility. For capture, require solved evidence, root cause or62 causal explanation, validation or explicit blocker, and prevention value. For63 refresh, inspect current repo reality before changing any stale artifact.643. Keep scope tight: start with 2-3 focused learning surfaces first, such as65 `.harness/solutions/**`, Project Brain paths, active `AGENTS.md` or66 instruction surfaces, and legacy `docs/solutions/**` when they may overlap.674. If reinforcement touches Project Brain, goal boards, artifacts, Chronicle,68 Local Memory, vault sync, or native citation state, apply69 ../../references/codex-native-memory-baseline.md and write or verify the70 matching sync receipt.715. Avoid duplicate memory. Update an existing high-overlap artifact; create a72 new one only when no high-overlap canonical artifact exists.73- See references/hot-path-folded-context.md for folded procedure detail.7475## Validation76Fail fast. Check solved evidence, validation output, overlap search,77frontmatter/markdown shape, structure preservation, redaction, Project Brain78classification, size budget, and discoverability. Report every gate as `pass`,79`fail`, or `blocked`.80For non-trivial generated learning artifacts, run or block81`python3 Plugins/harness-engineering/scripts/check_bluf_structure.py82<learning-artifact-path> --json`.8384## Safety Boundaries85- Forbidden: learning capture from unsolved issues, private transcript dumps,86 secret exposure, broad stale-doc rewrites, or destructive deletion without87 explicit authority.88- Redact secrets, credentials, private transcripts, sensitive personal data, and89 sensitive customer or operator data by default.90- See references/hot-path-folded-context.md for folded safety boundaries detail.9192## Failure Handling93If solved proof, validation, source evidence, redaction confidence, canonical94path, Project Brain classification, or discoverability is missing, return95`blocked_reason` and `next_evidence_needed`. If evidence is stale, mark the96candidate stale and hand off to `he-reconcile`, `he-fix-bugs`, `he-improve`, or97`he-eval-report` as appropriate.9899## Handoff Rules100Hand off lifecycle-state conflicts to `he-reconcile`, unresolved defects to101`he-fix-bugs`, bounded improvement proof to `he-improve`, implementation to102`he-work`, review repair to `he-code-review`, tracker planning to103`he-linear-plan`, and closure proof to `he-eval-report`.104105## Output Format106Structured output: `schema_version`, `mode`, `selected_artifact`,107`evidence_checked`, `solved_status`, `validation_status`, `overlap_status`,108`refresh_decisions`, `project_brain_status`, `continuity_status`,109`codex_native_memory_status`,110`structure_status`, `size_budget_status`, `discoverability_status`,111`source_prompt_family_status`, `redaction_status`, `writes`,112`git_staging_status`, `staged_paths`, `blocked_reason`, and `handoff`.113114## Examples115- When the user asks to inspect `.harness/session-evidence/latest.md` for JSC-246,116 start from the canonical Harness Engineering evidence and route the next action117 with validation status.118- When the user asks to validate a Linear closure decision for JSC-246, keep119 tracker mutation blocked until proof and authority are explicit.120121## Gotchas122- This skill reinforces learning; it does not decide lifecycle closure.123- One high-value artifact beats several vague notes.124- `delete_candidate` is not deletion authority.125- A passing local test is useful evidence, not proof that a learning is worth126 preserving.127- See references/hot-path-folded-context.md for folded gotchas detail.128129## Stage Arc Boundary130Before artifact writes, mutation, scheduling, handoff, or closure claims, apply131`../../references/stage-arc-boundary-contract.md`. Structured outputs and132handoffs must include `stage_arc_boundary` with `left_arc`, `active_arc`,133`right_arc`, `coding_lens`, and `testing_lens`; block when left evidence is134stale, active mutation exceeds authority, right-side proof is missing, or a135required persona lens is not covered.136137## References138- Use `assets/` only when this skill's local visual or template assets are explicitly needed.139Read `references/contract.yaml` for the full reinforcement contract and140`references/evals.yaml` for validation scenarios. Read141`references/source-prompt-preservation.md` when the request asks whether an142old compound/learning/project-brain/continuity prompt is still preserved. Use143`references/compound-learning-migration.md` before deleting or replacing old144`he-compound` behavior, or when the request mentions old compound capture,145compact-safe mode, Project Brain indexing, overlap refresh, or schema-driven146`docs/solutions` capture. Use147shared HE references only when active: solution capture, artifact routing,148session evidence, Project Brain surfaces, and subagent call boundaries.149Read when reviewability/No-Fog structure matters:150`../../references/bluf-review-contract.md`.151Read when a durable learning would be clearer as a causal or source-of-truth152visual: `../../references/visual-reference-contract.md`.153Read before delegating helper work:154`../../references/subagent-call-contract.md`.155Read before writing or verifying memory, artifact, goal, Chronicle, Local Memory,156vault, or native citation state:157`../../references/codex-native-memory-baseline.md`.158- See references/hot-path-folded-context.md for folded references detail.159- ../../references/deferred-context-index.md for folded/discarded context.160- Apply the context-disposition policy: move important still-valid context to references, and intentionally discard stale, duplicated, unsafe, superseded, or low-signal text.