Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/go
Go phase. Reads the approved SPEC file, maps Requirements to tasks (plan), executes via TDD (build), and integrates results verifying all Acceptance Criteria.
Passed 10 of 16 test cases with the skill, and 7 of 16 without it.
and 5 more in the full report
8 fixed6 passed either way4 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
The build and integration phases have completed successfully with all acceptance criteria verified. What explicit instruction should be given to the user for pre-release validation?
| Checked | Without skill | With skill |
|---|---|---|
| Advises running the audit command prior to shipping. | Missed | Passed |
The instructions your model reads when the skill loads.
CRITICAL: Run HARNESS_DIR=$(epic-harness path) first. NEVER use .harness/ in the project directory.
This skill has 3 internal modes that run sequentially:
Decompose the spec into an execution plan.
Load the spec:
ls -t $HARNESS_DIR/specs/SPEC-*.md | head -1
Read the file. Confirm frontmatter has status: approved. If not, invoke the spec skill first.
Survey the codebase: Identify relevant files, modules, patterns for each requirement.
Decompose: Map each Requirement → one or more Tasks. Every task must reference its source requirement:
Task 1: [description] — satisfies: R1 — depends on: none — modifies: [file list]
Task 2: [description] — satisfies: R2 — depends on: Task 1 — modifies: [file list]
Task 3: [description] — satisfies: R1,R2 (integration) — depends on: Task 1,2 — modifies: [file list]
Conflict analysis:
test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.