jds-bootstrap

To enforce a mandatory workflow check at session start, you need a process governance mechanism that blocks bypasses and initializes strict participation rules. This skill implements a gated software-engineering workflow to prevent unintended actions before any task execution begins.

A skill-check gate is a process governance control that initializes a workflow at session start, verifying mandatory rules before allowing task execution. It prevents bypasses by requiring strict participation and coordinating downstream clarification, planning, execution, and verification phases.

You initialize a gated workflow by triggering a session-start gateway that orchestrates downstream skills for thinking, planning, executing, and verifying. This coordinates the disciplined task execution sequence while applying domain rules to block unauthorized bypasses.

Yes, a session-start gateway can block workflow bypasses by applying mandatory skill-check rules before any action occurs. It maintains process safety through strict participation requirements, ensuring disciplined task execution across the entire software engineering workflow.

A disciplined workflow requires a mandatory initialization check to prevent unintended actions and embed process governance from the very beginning. Without this gating mechanism, downstream phases like clarification and planning could be bypassed, compromising execution safety and task integrity.

The limitation of a mandatory skill-check gate is its strictness; it blocks all bypasses and requires full participation, which may restrict rapid ad-hoc actions. It enforces domain rules rigidly, meaning any task execution outside the initialized workflow is prevented.