Capture durable lessons from messy work into propagation-ready Evolution Records.
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill trace-climb
Please help me install this Agent Skill. Skill: trace-climb Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/trace-climb Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill trace-climb
Trace Climb prevents valuable lessons from disappearing after messy tasks by converting them into an inspectable, propagation-ready learning trace.
After a messy or non-trivial task, tell your agent to run Trace Climb and write an Evolution Record using the template, ending with a clear propagation decision.
High-intent search queries and answers about installing and using this skill.
Post-task reflection captures durable lessons from non-trivial work by converting them into an inspectable Evolution Record. This record preserves origin traces, structural gaps, and missed assumptions so valuable context is never lost.
An Evolution Record is a structured learning trace that documents architectural changes, migrations, and guidance gaps. It enforces an explicit propagation decision to ensure captured knowledge is actively applied rather than just stored.
During the close phase, trigger classification determines if work warrants a required or recommended record. You then capture origin traces, activation traces, and observed outcomes into a structured template for future reference.
Use post-task reflection when work exposes reusable deltas like architectural changes, guidance gaps, or migrations. Trigger classification evaluates whether the task requires a durable record or if skipping is permitted based on learning value.
To prevent learning from being stored without follow-through, every durable record must end with an explicit propagation decision. This mandates choosing to update canon, update operational surfaces, open an ADR path, or defer with a named boundary.
Yes, skipping is allowed for tasks that do not expose reusable deltas. The trigger-aware classification evaluates whether work warrants a required record, a recommended record, or permits a skip to avoid unnecessary documentation overhead.
vtgiang-dotcomReview non-trivial decisions with a structured CLAIM, EXTRACT, DOUBT, RECONCILE, STOP cycle.
8DionysusPlan, execute, verify, and report scoped repository changes.
dayvidphamCapture user feature requests verbatim and seed Phase 2 tasks.
adrozdenkoExtract and classify knowledge patterns, decisions, and principles into a structured vault.
