prereq-chain

Enforce ordered workflow gates with completion criteria and CLEARED or BLOCKED outputs.

1|Updated Apr 2, 2026

Search Tags:#governance #phased-execution #artifact-management #prereq-chain #workflow-gates #completion-criteria #plan-critic

Ready to run

npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill prereq-chain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prereq-chain
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/prereq-chain
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill prereq-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that each phase in a multi-step workflow only starts after the previous phase has met its defined completion criteria, preventing cascading defects and misalignment.

Core Features & Use Cases

Defines an ordered sequence of phases with explicit completion criteria for each phase.
Gates transitions between phases (e.g., Design → Implement → Test → Deploy) to ensure traceable progress and evidence-based advancement.
Emits clear gate outputs (CLEARED or BLOCKED) with concrete evidence, enabling fast remediation.
Use Cases: establishing discipline in complex pipelines, integrating with plan-critic gates, and enforcing artifact-driven workflows.

Quick Start

Define your phased workflow and run prereq-chain before each transition to block progress until criteria are met.

Frequently Asked Questions about prereq-chain

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

FAQPage Schema

How do I enforce workflow gates to prevent premature phase transitions in a multi-phase pipeline?▼

Workflow gates prevent premature phase transitions by defining ordered phases with explicit completion criteria, emitting CLEARED or BLOCKED outputs with concrete evidence to block progress until prerequisites are met.

What types of completion criteria can I use to gate transitions between workflow phases?▼

Completion criteria types for gating workflow phases include artifact, quality, decision, and confirmation criteria, ensuring downstream phases only start when upstream outputs satisfy these defined checks.

How do I stop cascading defects when downstream phases consume artifacts from earlier steps?▼

Cascading defects are stopped by enforcing ordered workflow gates that require explicit completion criteria, ensuring each phase produces verified artifacts or decisions before the next phase can begin.

Can I integrate plan-critic gates with artifact-driven workflows for phased execution?▼

Artifact-driven workflows can integrate with plan-critic gates to establish discipline in complex pipelines, using prereq-chain to gate transitions and enforce traceable, evidence-based advancement.

What is the best way to establish discipline in complex pipelines with multiple execution phases?▼

Establishing discipline in complex pipelines involves defining an ordered sequence of phases with explicit completion criteria, gating transitions between phases like Design to Implement to Test to Deploy, and emitting clear gate outputs.

When should I not use automated workflow gates for phased execution?▼

Automated workflow gates are unnecessary for simple, single-step processes without downstream artifact consumption, as the overhead of defining completion criteria and gate outputs provides no traceability benefit in non-cascading workflows.