workflow-track

Evaluates work package results against baselines and generates lessons learned and changelogs.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill workflow-track-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-track
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/workflow-track
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill workflow-track-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Closing a work package without structured evaluation loses lessons learned, leaves changelogs unwritten, and lets unverified claims accumulate as epistemic debt. This Skill enforces Phase 11 TRACK/EVALUATE of the THYROX workflow so every work package ends with documented results, risks, and knowledge. ## Core Features & Use Cases - Lessons Learned Capture: Generates a structured lessons-learned document with root causes, generalizable rules, and reusable patterns using a dedicated template. - Changelog & Risk Closure: Produces a Keep-a-Changelog-style WP changelog from commits and updates the risk register, closing risks that did not materialize. - Epistemic Debt Audit: Reviews all prior stages for inherited claims never re-verified, listing them with status and recommended actions. - Readiness Validation: Ships a bash script that checks required artifacts (lessons-learned, changelog, risk register) exist before allowing phase transition. - Use Case: After finishing implementation of a feature work package, run Phase 11 to produce the lessons-learned file, WP changelog, resolved technical-debt register, and updated state files before the human gate approves transition to Phase 12 STANDARDIZE. ## Quick Start Ask the assistant to run the workflow-track phase to evaluate the active work package, generate its lessons-learned and changelog artifacts, and close it out.

Frequently Asked Questions about workflow-track

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close a work package in the THYROX workflow?▼

Run Phase 11 TRACK/EVALUATE: verify all tasks are checked in the task plan, generate the lessons-learned and WP changelog documents, update the risk register, then pass the validate-session-close.sh gate. A human gate confirms before transitioning to Phase 12 STANDARDIZE.

What artifacts does Phase 11 TRACK/EVALUATE require?▼

It requires a lessons-learned document, a WP changelog in Keep a Changelog format, an updated risk register, and optionally a technical-debt-resolved record and final report. The validate-phase-readiness.sh script checks these exist before allowing progression.

What is epistemic debt in work package evaluation?▼

Epistemic debt refers to claims inherited from earlier stages that were never re-verified later. Before creating lessons-learned, you list each inherited claim with its origin stage, verification status, and a recommended action such as converting it to a technical-debt item.

When should I use the incremental correction methodology?▼

Use it when correcting 100 or more issues at scale, such as large batches of build warnings. It provides analysis, categorization, execution-log, and final-report templates. Do not use it for fewer than 10 issues or when speed is the only priority.

Does the root CHANGELOG.md get updated during work package closure?▼

No. The root CHANGELOG.md is only updated during releases with a version bump. Phase 11 generates a per-work-package changelog file in the track directory instead.