gate-work

Execute gate document checkpoints and document artifact evidence.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/basher83/domain-chassis --skill gate-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-work
Source: https://github.com/basher83/domain-chassis/tree/main/skills/gate-work
Command: npx skills add https://github.com/basher83/domain-chassis --skill gate-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured methodology for executing predefined gate checkpoints within a validation plan, ensuring all criteria are met and evidence is meticulously documented before a gate is cleared.

Core Features & Use Cases

  • Checkpoint Execution: Works through a gate document step-by-step, marking checkpoints as complete.
  • Evidence Documentation: Requires concrete evidence (command output, file contents) to be documented inline for each completed checkpoint.
  • Lifecycle Adherence: Enforces the gate lifecycle (plan -> review -> work) by checking for prior review and completion status.
  • Use Case: After a gate plan is created and reviewed, this skill is used to perform the actual work outlined in the gate document, ensuring all tasks are completed and verified.

Quick Start

Use the gate-work skill to execute the gate document 'Q3-gate.md'.

Frequently Asked Questions about gate-work

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

FAQPage Schema
How do I document evidence for gate validation checkpoints?

Executing gate validation requires working through a gate document step-by-step, verifying all validation criteria are met, and documenting concrete artifact evidence like command outputs before clearance is granted.

What is the best way to enforce a gate lifecycle during operational execution?

Enforcing a gate lifecycle during operational execution requires checking for prior review and completion status, ensuring the workflow progresses from plan to review to work phases before satisfying post-clearance exit sequences.

How do I execute a gate document to satisfy validation criteria?

You execute a gate document by working through its checkpoints sequentially, marking each as complete, and providing concrete evidence inline until all validation criteria are satisfied for final clearance.

Do I need a reviewed gate plan before starting checkpoint execution?

Yes, you need a reviewed gate plan before starting checkpoint execution, because the lifecycle adherence mechanism checks for prior review and completion status before allowing the operational work phase to begin.

What happens if validation criteria are not met during gate execution?

If validation criteria are not met during gate execution, clearance is withheld, preventing the progression to post-clearance exit sequences until all checkpoints are marked complete with sufficient evidence.