skills.rest
Luis-ERP
Luis-ERPCOMMUNITY
Explore all skills by this author →
GitHub

Workflow Enforcement

Validate phase progression and artifacts against the canonical WORKFLOW.md.

Updated Feb 5, 2026
Search Tags:#workflow#governance#handoff#enforcement#artifact-validation#phase-ordering#team-workflow
One-click install
npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill workflow-enforcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Workflow Enforcement
Source: https://github.com/Luis-ERP/dev-agent-crew/tree/main/skills/workflow-enforcement
Command: npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill workflow-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces that all work follows the canonical team workflow topology defined in docs/team/WORKFLOW.md, preventing phase skipping, ownership conflicts, and missing artifacts.

Core Features & Use Cases

  • Phase-order compliance: Ensures the current phase is complete before the next phase starts.
  • Ownership and governance: Detects ownership conflicts and coordination requirements.
  • Artifact validation: Verifies required artifacts exist and are non-empty for the active phase.
  • Gate enforcement: Checks all defined gates and surfaces blockers when unmet.

Quick Start

Trigger the workflow enforcement when a feature attempts to advance a phase, or when artifacts are missing, or there is a dispute about progress.

Frequently Asked Questions about Workflow Enforcement

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

FAQPage Schema
How do I enforce phase ordering and prevent skipping gates in a team workflow?▼

Workflow enforcement validates phase progression against a canonical WORKFLOW.md file, ensuring the current phase is fully complete before the next phase starts. It blocks advancement whenever required artifacts are missing or phase gates are unmet.

What is workflow compliance validation and when do I need it for governance?▼

Workflow compliance validation checks work progression against canonical team governance rules. You need it when features attempt to advance phases, work skips a phase, or required artifacts are missing or incomplete.

How do I check for missing artifacts and ownership conflicts before a phase handoff?▼

Trigger workflow enforcement to verify required artifacts exist and are non-empty for the active phase. It detects ownership conflicts and records blockers in HANDOFF.md before the phase handoff occurs.

Can I use workflow enforcement to raise escalation signals when team workflow is unclear?▼

Yes, workflow enforcement raises escalation signals whenever the canonical workflow topology is unclear. It also produces compliance notes on the current phase artifact to document unresolved governance issues.

What are the limitations of relying on a canonical WORKFLOW.md for phase gating?▼

Enforcement depends entirely on a predefined canonical WORKFLOW.md file. If the workflow topology is unclear, it raises escalation signals rather than resolving the governance ambiguity automatically.

Related Skills

Explore More Product & Management Skills→
KentoShimizuKentoShimizu
7

git-branch-strategy

Define Git branch topology, lifecycle rules, and merge policy.

Community
Advanced
rsicarellirsicarelli
63

implementation-tracker

Track Fakt implementation progress across phases, tests, compilation, milestones, and blockers.

Community
Intermediate
leejaedusleejaedus

ultrapilot

Orchestrate parallel subtasks with exclusive file ownership and coordinated integration.

Community
Advanced
SHGrowthSHGrowth
6

om-implement-spec

Coordinate subagents to implement specs phase-by-phase with code-review gates.

Official
Advanced