architect-brainstorm

To generate YAML scenario files for security training labs, you can use a guided four-phase brainstorming workflow that scaffolds topology, characters, plugins, and exploit paths into structured scenario_part1.yml, scenario_part2.yml, scenario_part3.yml, and exploit.yml outputs.

The best way to blueprint a network topology for a cybersecurity lab is through a phase-driven design process that captures company identity, machines, domains, and VLANs while applying real-world schemas to ensure structural consistency.

The gated handoff process works by enforcing a one-question-per-message cadence across four phases, using Haiku subagents to produce YAML artifacts before coordinating a structured handoff to an architect-validator for final review.

Yes, you can include optional exploit paths when scaffolding a training lab scenario by utilizing a specific output flow that generates an exploit.yml file alongside the scenario parts to document the exploit paths.

No specific dependencies are required to design scenario YAMLs for Rogue Arena, as the tool relies on internal schemas and brainstorm references to guide the blueprint generation without external components.

Automated subagents for lab scenario design are constrained by their gated interaction cadence, requiring one question per message, and they depend strictly on internal reference docs to maintain safety and consistency rather than dynamic external validation.