he-phase-work

Runs approved Harness Engineering plans in recurring phases: check live state, confirm continuation authority, execute only the active he-work slice, verify gates, update Linear only with approval, and stop before unsafe staging or closure. Use when a plan, issue, or PR needs continued phase-by-phase execution.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized orchestration skill body with a clear numbered workflow, explicit validation checkpoints and feedback routing, concrete delegation examples, and a usable output template. Minor conciseness padding, parameterized command placeholders, and some inline contract detail keep it from a perfect score.

Suggestions

Trim the Philosophy section and de-duplicate content across Inputs, Outputs, and Procedure to tighten token efficiency.

Replace generic placeholders (e.g. <approved-plan-path>, <touched-skill-path>) with a concrete worked example alongside the parameterized form to lift actionability.

Move the inline Stage Arc Boundary contract detail fully into references/stage-arc-boundary-contract.md and reference it, keeping the body a pure overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely lean, assuming Claude's competence without explaining basic concepts, but the Philosophy section and some overlap between Inputs/Outputs/Procedure add minor padding that could be trimmed.	4 / 5
Actionability	Concrete commands (git status --short, git branch --show-current, rg, ./bin/ask skills audit), copy-paste delegation text blocks, and a full YAML output template make it mostly executable; parameter placeholders like <approved-plan-path> keep it just shy of fully copy-paste ready.	4 / 5
Workflow Clarity	A clearly sequenced 7-step Procedure pairs with a 'Fail fast' Validation section, a Failure Mode stop-condition block, and an explicit feedback loop ('If it fails, route to he-work or he-code-review'), satisfying the checkpoint and error-recovery anchors.	5 / 5
Progressive Disclosure	The body acts as an overview pointing to one-level-deep references that exist in the bundle (references/phase-gate-contract.md, contract.yaml, evals.yaml), but the Stage Arc Boundary section inlines contract detail and several references point to a parent ../../references/ tree not present in this bundle.	4 / 5
	Total	17 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill does and when to use it, with concrete enumerated actions and explicit trigger guidance. Slight jargon load and overlap with sibling he-* skills keep it just short of perfect on trigger quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'check live state, confirm continuation authority, execute only the active he-work slice, verify gates, update Linear only with approval, and stop before unsafe staging or closure' — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers both what (the enumerated phase actions) and when ('Use when a plan, issue, or PR needs continued phase-by-phase execution') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when a plan, issue, or PR needs continued phase-by-phase execution' clause plus metadata trigger_terms ('continue approved plan', 'keep issue moving', 'run phases') give good natural coverage, though phrasing leans on jargon ('Harness Engineering', 'he-work slice') and misses some common synonyms.	4 / 5
Distinctiveness Conflict Risk	The recurring phase-gated heartbeat niche is distinct from one-off work, but it sits in a family of sibling he-* skills (he-work, he-plan, he-spec) creating minor overlap risk on shared trigger terms like 'plan' and 'issue'.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jscraik/Agent-Skills
Path: Plugins/harness-engineering/skills/he-phase-work/SKILL.md
Commit: 2f91362

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.