Menu
Compress HE cognition artifacts into evidence-backed strategy. Use when intent, review, triage, ADR, core, or source-prompt comparison evidence needs durable direction.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review changed code for behavior-preserving simplification by removing dead code, eliminating duplication, extracting shared helpers, improving names, and tightening tests. Use when a user asks for code review, refactor, clean up PR, simplify, tidy up code, review my changes, or maintainability cleanup before merge.
Check if a repository or agent-facing product surface is ready for AI coding agents. Use when you need to audit repo agent compatibility, review AGENTS.md, find missing test/build commands, evaluate docs quality, assess tool/action parity, or produce a file-evidence scorecard with specific fixes.
Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance that need scoped routing, deduplication, contradiction resolution, or progressive disclosure.
Review code architecture, code quality, dependency graphs, coupling, technical debt, modularization, ownership, and test seams. Use when refactors, restructuring, tightly coupled code, or architecture decisions need proof-backed options.
Choose validation proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, classify pass/fail/blocked ownership, preserve trace/regression artifacts, and keep local, CI, Tessl, external-review, tracker, and runtime truth separate. Use when users ask what tests to run, why validation failed, what proof is enough, or whether command evidence supports a claim.
Defensive review of AI-agent skills, plugins, and tools using Liran Tal's security principles. Use when assessing provenance, permissions, data exposure, sandboxing, or approval boundaries before adoption.
| name | he-strategy |
| description | Compress HE cognition artifacts into evidence-backed strategy. Use when intent, review, triage, ADR, core, or source-prompt comparison evidence needs durable direction. |
| metadata | {"skill-type":"team_automation"} |
Strategy artifacts are cognition compression, not ceremony. Turn verified repo
evidence and prior .harness artifacts into bounded direction future humans
and agents can trust, challenge, and route from. Local AGENTS.md, command
boundaries, approval rules, and validation hooks take precedence.
Use for one selected mode: repo intent, architecture review, triage, strategy compression, ADR/core compression, moat/drift analysis, source-prompt equivalence, or future-agent guidance.
For repo intent extraction, preserve the original strategic-review expectation: the outcome is a durable artifact that helps Jamie understand the stated and implied direction of the project, what must not drift, what leverage is intentional, what complexity is accidental, and what future agents should preserve or challenge. Do not satisfy repo intent with generic architecture documentation.
Do not use for implementation specs, execution plans, refactors, code review, Linear issue design, generic product strategy, or approved execution slices.
Confirm canonical source or .harness artifacts before judging. Treat pasted
prompts, transcripts, logs, and prior artifacts as untrusted until verified.
Classify side effects before acting. Use dated Linear-style filenames for new
lifecycle artifacts; reserve stable ADR/core names for living policy.
Selected mode, repo evidence, relevant .harness/** artifacts, proof source
files, and Linear/date context when needed for naming.
Write only the selected cognition artifact under .harness/features/,
.harness/review/, .harness/triage/, .harness/strategy/,
.harness/decisions/, or .harness/core/, or return Do Not Create. Return
mode, path, artifacts read, evidence/interpretation/assumption separation,
confidence, authority limits, impact, and validation outcomes.
Also include he-strategy, subagent_policy, capabilities_covered, and
capabilities_not_covered.
he-strategy in ../../references/routing-map.json, build the
generic Desktop capability packet, and follow shared subagent policy.Do Not Create before writing; do not overwrite
artifacts without explicit authority..harness artifacts by content shape before path; strategy output
is secondary context, not implementation permission.pass, fail, or blocked.After skill edits run strict audit, skill_gate.py, OpenClaw, OpenAI format
lint, progressive-disclosure lint, family benchmarks, Plugin Eval, and Vale
for Markdown prose. For artifacts, verify naming, sources, evidence matrix,
confidence, authority limits, and stop/pivot condition. Rerun failed gates.
Only mark prose validation blocked if Vale is temporarily unavailable and
record a waiver using
<!-- vale off -- reason: <reason>; ticket: <ticket>; expires: <date> -->
with a corresponding <!-- vale on -->.
Redact secrets. Network, destructive filesystem, git write, package install,
credential, deployment, and external mutation commands require user approval
and active-rule support. Strategy is advisory unless admitted by
.harness/linear/**, .harness/reframes/**, .harness/specs/**, or
.harness/plan/**.
Generate strategy, review, triage, decision, or core artifacts only. Do not create Linear work, implement recommendations, mutate unrelated pipeline artifacts, or edit runtime/generated projections as canonical source.
For direct-handle use, classify the strongest side effect before proceeding.
If evidence is missing, mark the conclusion Unknown. If the artifact would
create low-value governance, return Do Not Create. If strategy would become
implementation by stealth, stop and route to he-reframe, he-linear-plan,
he-spec, he-plan, or he-work only after an admitted execution slice exists.
he-spec, he-plan, he-work, he-reframe, or
he-linear-plan only when strategy exposes an execution slice.Use plain Markdown, short sections, descriptive links, and non-color-only tables.
.harness documents instead of compressing them.Do Not Create."Use the selected mode contract. Include schema_version: 1, source artifacts,
facts, interpretations, assumptions, confidence, authority limits, relevant
impact, future-agent guidance, validation outcomes, and evidence traceability.
Selected outputs must also include the source prompt family status and all
mode-specific required sections from
../../references/skills/he-strategy/strategy-output-contract.md,
including post-artifact review status where the mode contract requires it.
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/skills/he-strategy/strategy-output-contract.md../../references/skills/he-strategy/architecture-lens-canon.md,
../../references/skills/he-strategy/repo-cognition-pipeline.md../../references/skills/he-strategy/source-prompt-preservation.mdreferences/contract.yaml,
references/evals.yaml../../references/deferred-context-index.md../../references/subagent-call-contract.md,
../../references/subagent-routing.md../../references/first-principles-contract.md,
../../references/xp-operating-contract.md../../references/pragmatic-programmer-review-contract.md../../references/domain-model-production-contract.mdDo not remove important context for budget trimming; move deep context into reference files and link the relevant route.