skills.rest
NUMU-IO
NUMU-IOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-red-team-gate

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

2|Updated Jan 6, 2026
Search Tags:#spec-kit#red team#findings report#compliance check#waiver#planning gate#keyword scan
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-red-team-gate-numu-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-red-team-gate
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-red-team-gate
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-red-team-gate-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents planning from moving forward on feature specs that meet red-team trigger criteria without an existing findings report, reducing missed review steps in spec-kit workflows.

Core Features & Use Cases

  • Detects trigger keywords in a spec body across money, regulatory, AI, audit, multi-party, and contract risk areas.
  • Verifies whether a red-team findings file already exists in the expected project or archive paths before planning continues.
  • Supports explicit opt-outs so teams can waive the gate and record the exception as an accepted risk.
  • Use it when a product spec may require security, compliance, or contractual scrutiny before /speckit.plan can run.

Quick Start

Use this Skill to check the current feature spec and tell me whether planning should proceed, be blocked, or be waived.

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 block risky feature specs before planning in a spec-kit workflow?▼

You can block risky feature specs before planning by applying a red-team gate that scans spec text for trigger keywords across money, regulatory, AI, audit, multi-party, and contract risk areas, preventing planning from proceeding without a findings report.

What red-team trigger keywords does the spec-kit gate scan for during compliance checks?▼

The red-team gate scans for deterministic trigger keywords in spec bodies covering money, regulatory, AI, audit, multi-party, and contract risk areas to determine if a findings report is required before planning continues.

Can I waive the red-team gate and still proceed with planning if I accept the risk?▼

Yes, you can waive the red-team gate by providing an explicit skip reason, which records the exception as an accepted risk and allows the planning process to proceed despite the unmet trigger criteria.

How does the gate locate an existing red-team findings report in a spec-kit repository?▼

The gate locates an existing red-team findings report by resolving default and archived findings paths within the spec-kit repository, verifying the file exists before it allows the planning process to proceed.

What is the difference between blocked, satisfied, and waived outcomes when checking spec text?▼

Blocked means trigger criteria are met but no findings report exists, satisfied means the report exists and criteria are met, and waived means an explicit skip reason was recorded as accepted risk to bypass the gate.

Related Skills

Explore More Software Engineering Skills→
juanca202juanca202

speckit-git-commit

Automate Git commits after Spec Kit command events.

Community
Basic
B0yZ4kr14B0yZ4kr14

speckit-red-team-gate

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

Community
Intermediate
abonetoaboneto

speckit.analyze

Identify cross-artifact inconsistencies among spec.md, plan.md, and tasks.md.

Community
Intermediate
AAbdulghanyAAbdulghany

design-review

Review architectural designs for soundness before code builds.

Community
Advanced