Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/impl-tracking
Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored. Covers the full tracking document template, dead ends prevention, cross-iteration continuity, spec compaction, and inter-session feedback protocol. Trigger phrases: "implementation tracking", "track progress", "session tracking", "what did the agent do", "dead ends", "failed approaches"
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 10 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When compacting the active implementation tracking file `impl-auth.md`, specify the standard directory path and file naming pattern for the created archive file.
| Checked | Without skill | With skill |
|---|---|---|
| The archive file path places the archive inside an archive subdirectory under impl. | Missed | Passed |
| The archive filename includes a version suffix such as v1 or v2. | Missed | Passed |
The instructions your model reads when the skill loads.
Implementation tracking documents are living records that agents read and update every session. They serve as persistent memory across iterations, preventing duplicate work and preserving hard-won knowledge about what works and what does not.
The most valuable information in an implementation tracking document is not what succeeded — it is what failed and why. Dead ends documented today prevent agents from wasting hours retrying the same failed approaches tomorrow.
| Purpose | What It Prevents |
|---|---|
| Cross-iteration continuity | Agents starting from scratch every session |
| Dead end prevention | Agents retrying approaches that already failed |
| Progress visibility | Humans not knowing what was done or what is left |
| Test health awareness | Agents not knowing current test state |
| Issue tracking | Known issues being forgotten between sessions |
| File change tracking | Uncertainty about what files were created or modified |
Without implementation tracking, every agent session begins with expensive rediscovery. With it, agents resume exactly where the last session left off.
Use this template for every implementation tracking document:
# Implementation Tracking: {Domain or Scope}
## Status: {IN_PROGRESS | COMPLETE | BLOCKED}
**Last Updated:** {Date}
**Current Phase:** {Spec | Plan | Implement | Iterate | Monitor}
**Blocking Issues:** {None | Brief description of blockers}
---
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.