des-workflow-status-update

Update DES workflow status files from planning and implementation evidence.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-workflow-status-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-workflow-status-update
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills-support/des-workflow-status-update
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-workflow-status-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents agent confusion and lost progress by maintaining an up-to-date, evidence-backed workflow status artifact across DES main phases and support-task cycles for data engineering projects.

Core Features & Use Cases

  • Central workflow continuity: Creates or updates a single workflow status file that records current progress, artifact states, open blockers/risks, and the routing decision.
  • Evidence-driven status updates: Scans main planning outputs and implementation/support artifacts, then marks items as Done only when evidence exists (otherwise uses Unknown/Missing/Not Applicable appropriately).
  • Operational handoff & next step: Produces required next actions and recommends the next skill/route while enforcing guardrails to avoid premature progression (e.g., release before code-review evidence).

Quick Start

Use des-workflow-status-update to scan your current DES planning and implementation artifacts and update _des-output/implementation-artifacts/des-workflow-status.md with the correct next route.

Frequently Asked Questions about des-workflow-status-update

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

FAQPage Schema
How do I sync data engineering workflow status across sprint planning and release phases?

To sync data engineering workflow status, this Skill scans lifecycle planning outputs and implementation reports to update a single workflow status artifact with consistent progress, blockers, risks, and next routing decisions.

What is evidence-driven workflow status tracking for agent orchestration?

Evidence-driven workflow status tracking marks data engineering lifecycle items as Done only when proof exists in planning outputs or support reports, otherwise applying Unknown, Missing, or Not Applicable states to prevent agent confusion.

How to update workflow status artifacts with current blockers and risks?

Updating workflow status artifacts requires scanning configured status sources and templates from customize.toml, then writing a fully populated status file with open blockers, risks, required next actions, and the next routing decision.

Does the workflow status update enforce release readiness guardrails?

Yes, the workflow status update enforces guardrails to avoid premature progression, preventing release before code-review evidence is found and ensuring correct-course decisions rely on verified implementation reports.

Can I use customize.toml templates to configure workflow status sources?

Yes, you can use customize.toml to configure templates and checklists for status sources, which the Skill scans to synthesize evidence and write a fully populated data engineering workflow status file.

Why does my data engineering agent lose progress between retrospective and sprint planning?

Agents lose progress without a central workflow continuity file; this Skill maintains an up-to-date status artifact across DES phases, ensuring handoffs include required next actions and routing decisions for sprint planning.