speckit-red-team-run

To run an adversarial red-team review on a functional spec, execute the command targeting your spec file path. The review uses parallel, lens-driven agents to uncover hidden spec weaknesses and aggregates structured findings for maintainer resolution.

A red-team spec review adversarially tests functional specifications before architecture lock-in. It applies multiple configurable risk lenses in parallel to identify vulnerabilities and outputs a structured findings report classifying resolutions.

Yes, you can explicitly override lenses for controlled red-team runs. By default, the system automatically selects lenses by heuristically matching triggers in the target spec, but explicit overrides bypass this automatic trigger matching.

No, the red-team review does not auto-edit historical SpecKit working records. It writes a deterministic findings report to the feature directory and guides maintainers through classifying resolutions like spec-fix, new open question, or accepted risk.

Yes, you can use this adversarial spec review in CI pipelines through its dry-run reporting mode. It writes deterministic reports to the feature directory and enforces per-lens finding bounds, supporting both CI and interactive workflows.

You need a SpecKit project with a functional spec target and a configurable red-team lens catalog YAML. The system locates the target spec, parses the lens catalog, and performs trigger matching to execute the review.