workflow-track

Generates lessons-learned documents, changelogs, and closure artifacts for completed work packages.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill workflow-track-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-track
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/workflow-track
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill workflow-track-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Closing a work package often leaves undocumented lessons, missing changelogs, and stale state files, causing teams to repeat mistakes and lose track of what was delivered. This Skill standardizes Phase 11 TRACK/EVALUATE of the THYROX workflow so every work package ends with consistent, auditable closure artifacts. ## Core Features & Use Cases - Lessons Learned Capture: Generates a structured lessons-learned document with root causes, generalizable rules, and an epistemic-debt review of unverified claims from earlier phases. - Changelog & Risk Closure: Produces a Keep-a-Changelog-style WP changelog from git commits, updates the risk register, and archives resolved technical debt entries. - Readiness Validation: Ships a bash script that verifies required artifacts exist before allowing transition to Phase 12 STANDARDIZE. - Use Case: After finishing implementation of a feature branch, run this Skill to produce the lessons-learned file, WP changelog, updated risk register, and closed state files before merging. ## Quick Start Ask the assistant to run the workflow-track phase to evaluate results, document lessons learned, and close the active work package.

Frequently Asked Questions about workflow-track

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

FAQPage Schema
How do I document lessons learned after completing a work package?▼

Run the workflow-track phase, which generates a lessons-learned document from a template capturing what happened, root causes, applied fixes, and generalizable rules. It also includes an epistemic-debt review listing claims from earlier phases that were never re-verified.

How to generate a changelog from git commits for a feature branch?▼

The Skill creates a WP changelog using a Keep a Changelog format, grouping commits by type (Added, Changed, Fixed, Removed). It derives entries from git log output between the base branch and HEAD of the work package.

What artifacts are required before closing a work package?▼

Required artifacts include a lessons-learned file, a WP changelog, an updated risk register, and a technical-debt-resolved document if TDs were closed. The validate-phase-readiness.sh script checks that all required files exist before allowing transition to Phase 12.

Does this workflow require human approval before closing a phase?▼

Yes, Phase 11 includes a human gate that pauses after presenting the summary of artifacts, key lessons, and metrics versus baseline. Explicit confirmation is required before transitioning to Phase 12 STANDARDIZE.

When should I not use the incremental correction methodology referenced here?▼

Do not use it for small correction batches under 10 issues or when issues have uniform complexity. The methodology targets large-scale corrections of 100+ issues where structured analysis, batching, and validation checkpoints prevent regressions.