gates

Define and enforce gate semantics for council reports and project status.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill gates-brucebanner010198-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gates
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/gates
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill gates-brucebanner010198-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This governance skill defines a single source of truth for gate colors, blocking vs informing, and the aggregation of council signals into a project-wide status, eliminating ambiguity in ship decisions.

Core Features & Use Cases

  • Defines color semantics (green/yellow/red/n/a) and when each applies to blocking vs informing councils.
  • Provides the gate emission and aggregation rules used by the CEO to derive project-wide status from council reports.
  • Supports waiver workflows to override non-blocking reds with user consent, and keeps follow-ups for remediation.

Quick Start

Map the current council reports into a project gate using the standard rules.

Frequently Asked Questions about gates

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

FAQPage Schema
How do I aggregate council status reports into a single project-wide gate?

Blocking gates prevent project progression until resolved, while informing gates provide visibility without halting work. Gate semantics define blocking versus informing behavior across councils to determine the aggregated project-wide status.

How do blocking and informing gates work in project risk management?

Blocking gates prevent project progression until resolved, while informing gates provide visibility without halting work. Gate semantics define blocking versus informing behavior across councils to determine the aggregated project-wide status.

Can I override a red gate status from a non-blocking council?

Gate color semantics use green, yellow, red, and n/a to indicate project status across blocking and informing councils. These colors standardize how per-council rules evaluate and aggregate into a single source of truth for ship decisions.

What do the different gate colors mean for council reports?

Gate color semantics use green, yellow, red, and n/a to indicate project status across blocking and informing councils. These colors standardize how per-council rules evaluate and aggregate into a single source of truth for ship decisions.

How do I set up per-council gate rules for project status reporting?

Gate aggregation rules apply when you need to derive project-wide ship status from multiple council reports. The framework eliminates ambiguity in ship decisions by providing a single source of truth for gate colors and blocking versus informing behavior.

When should I use a gate aggregation framework for project status?

Gate aggregation rules apply when you need to derive project-wide ship status from multiple council reports. The framework eliminates ambiguity in ship decisions by providing a single source of truth for gate colors and blocking versus informing behavior.