skills.rest
B0yZ4kr14
B0yZ4kr14COMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-red-team-gate

Checks feature specs for red-team review triggers and required findings before planning.

Updated Mar 16, 2026
Search Tags:#specification#compliance#risk management#security review#red team#gatekeeping#planning control
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-red-team-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-red-team-gate
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-red-team-gate
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-red-team-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents a qualifying feature spec from moving forward without a red team findings report on record, reducing the risk of missing security, compliance, or contractual safeguards.

Core Features & Use Cases

  • Spec qualification gate: Scans the target spec for red team trigger criteria (e.g., money/regulatory content, LLM involvement, immutability/audit requirements, multi-party approvals, and contract/API boundary language).
  • Findings report enforcement: Verifies that a matching findings report exists in the expected repository locations, including archived paths.
  • Explicit waiver support: Allows an intentional opt-out via a skip token that must be recorded as an accepted risk in the plan output.

Quick Start

Ask the system to run the gate before planning a feature spec named by your current branch or by a provided spec path.

Frequently Asked Questions about speckit-red-team-gate

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

FAQPage Schema
How do I enforce a security review gate before planning a feature spec?▼

A red team review gate scans a feature spec for trigger criteria like regulatory content or multi-party approvals and halts planning if a matching findings report is missing.

What makes a feature spec qualify for a mandatory red team review?▼

A feature spec qualifies for red team review when it contains trigger keywords across defined categories, including money or regulatory content, LLM involvement, immutability requirements, and contract or API boundary language.

Can I skip the red team findings requirement if I accept the security risks?▼

Yes, you can skip the findings requirement using an explicit waived mode, which requires recording a skip token as an accepted risk in the plan output to maintain compliance transparency.

How do I run the compliance gate using my current git branch context?▼

You can run the compliance gate by invoking the before_plan hook without an explicit path; the system derives the feature spec from your current branch context and scans it automatically.

Where does the gatekeeping tool look for existing red team findings reports?▼

The gatekeeping tool locates existing findings reports by checking configured repository globs, including standard paths and archived locations, to verify that a matching report exists.

Related Skills

Explore More Legal & Compliance Skills→
NUMU-IONUMU-IO
2

speckit-red-team-gate

Scan spec text for red-team triggers and block planning without findings.

Official
Intermediate
hbvg234hbvg234
1

executing-plans

Execute approved plan steps one at a time without scope expansion.

Community
Advanced
GratefulJinx77GratefulJinx77

build-order

Scan specs/ and tasks.md to determine the next feature build order.

Community
Advanced
truongnattruongnat

gatekeeper-skill

Analyze verification status and review findings to allow, block, or defer command execution.

Community
Intermediate