gathering-architecture

Orchestrate multi-phase architecture design with subagent gate checks and CI verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/shuretokki/void --skill gathering-architecture-shuretokki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gathering-architecture
Source: https://github.com/shuretokki/void/tree/main/.agents/skills/gathering-architecture
Command: npx skills add https://github.com/shuretokki/void --skill gathering-architecture-shuretokki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual coordination burden of turning a vision into a buildable foundation by orchestrating a disciplined, multi-phase architectural workflow that enforces isolation, gate checks, and artifact-driven handoffs.

Core Features & Use Cases

  • Conductor orchestration: Dispatches specialized subagents (Eagle, Crow, Swan, Elephant) in sequence to design, adversarially review, specify, and implement a system foundation.
  • Fresh-eyes gatekeeping: Enforces isolated inputs and verification between phases so challenges are unfiltered and implementations follow a single source of truth.
  • Artifact and CI verification: Produces architecture docs, technical specs, and a file-level build manifest with required CI checks to ensure the foundation compiles.
  • Use Cases: Designing new systems end-to-end, major refactors of core infrastructure, delivering a spec-to-foundation pipeline, or performing rigorous architecture reviews.

Quick Start

Invoke the gathering-architecture conductor and provide a concise system specification so it can orchestrate Eagle, Crow, Swan, and Elephant to produce an architecture, a detailed specification, and a buildable foundation.

Frequently Asked Questions about gathering-architecture

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

FAQPage Schema
How do I orchestrate multi-agent architecture design for a complex system?

Multi-agent architecture design is orchestrated by dispatching specialized subagents in sequence to design, adversarially review, specify, and implement a buildable system foundation with enforced gate checks and artifact handoffs.

What is an adversarial architecture review and when do I need one?

An adversarial architecture review is an isolated gate check that challenges system designs with unfiltered inputs before implementation. You need it when creating major systems or refactoring core infrastructure to ensure a single source of truth.

How do I generate a buildable foundation from a system specification?

Generate a buildable foundation by providing a concise system specification to an orchestration conductor, which coordinates subagents to produce architecture docs, technical spec files, and a compile-ready file-level build manifest.

Can I use multi-agent orchestration for major infrastructure refactors?

Yes, you can use multi-agent orchestration for major infrastructure refactors. It applies disciplined, multi-phase architectural workflows to deliver detailed specifications and a buildable foundation with CI verification.

Does this architecture workflow enforce CI verification for foundation artifacts?

Yes, this architecture workflow enforces CI verification by producing a file-level build manifest with required CI checks, ensuring the compile-ready foundation artifacts and technical specifications meet isolated gate checks.

What are the limitations of using isolated subagent inputs for system design?

The limitation of isolated subagent inputs is that coordination requires strict artifact-driven handoffs between phases, meaning any missing gate checks or incomplete technical specifications will block downstream implementation.