progress-log

Propagate DAE handoff summaries into progress.md and tracker records.

134|9|Updated Feb 16, 2026

Search Tags:#progress tracking #mutation testing #ATDD #agentic workflows #handoff summaries #checkpoint orchestration #tracker synchronization

Ready to run

npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill progress-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: progress-log
Source: https://github.com/swingerman/disciplined-agentic-engineering/tree/main/engineer/skills/progress-log
Command: npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill progress-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineers lose track of where AI-written work stands because handoff summaries don’t automatically become a clear, per-feature progress state and a synced tracker update.

Core Features & Use Cases

Auto and scoped propagation: Converts new handoff summaries into the relevant feature’s progress.md and tracker state, either automatically after managed field changes or manually for a single feature or whole project.
Checkpoint-aware progress rendering: Recomputes the CURRENT header from the latest handoff’s exit_criteria, recommended_next, and any human-blocking unmet criteria.
Tracker synchronization with conflict rules: Upserts a TrackedFeature using local-wins for DAE-managed fields while preserving tracker-managed fields like comments and labels, with an optional project-wide drift reconciliation.

Quick Start

Run /engineer.progress-log <slug> to re-sync the chosen feature’s progress.md and external tracker from the latest handoffs.

Frequently Asked Questions about progress-log

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

FAQPage Schema

How do I convert AI handoff summaries into per-feature progress visibility?▼

AI handoff summaries are converted into per-feature progress visibility by propagating new handoff entries into the feature's progress.md and updating its CURRENT header with the latest exit criteria and recommended next steps.

How do I synchronize a local progress.md file with an external tracker without losing comments?▼

Synchronizing local progress.md with an external tracker uses a local-wins upsert strategy for DAE-managed fields while preserving tracker-managed fields like comments and labels during the TrackedFeature update.

What is checkpoint orchestration in agentic workflows?▼

Checkpoint orchestration in agentic workflows recomputes the CURRENT header from the latest handoff's exit_criteria, recommended_next, and any human-blocking unmet criteria to render accurate feature progress state.

Can I manually reconcile tracker drift for an entire project after handoff state updates?▼

Manual reconciliation for an entire project is supported by running a scoped propagation that resolves the methodology root, reads new handoffs, updates progress.md, and performs optional project-wide drift reconciliation.

Does tracker synchronization support mutation testing and ATDD workflows?▼

Tracker synchronization supports mutation testing and ATDD workflows by propagating checkpoint, verification, and fix-closure states from DAE handoff summaries into synchronized TrackedFeature records.

What are the limitations of local-wins upsert during tracker synchronization?▼

The limitation of local-wins upsert during tracker synchronization is that DAE-managed fields will always overwrite external tracker values, requiring optional drift reconciliation to detect and manage conflicting manual tracker edits.