slight76/project-flood
A governed Copilot squad that can create bounded research and worktree swarms.
Revalidate, compact, archive, or discard stale Project Flood repository context when memory or orchestration state has become noisy or contradictory.
Decide whether multi-part work merits a bounded squad or swarm, then define safe waves, dependencies, ownership, gates, and convergence.
Verify, promote, supersede, archive, or reject durable Project Flood memory after accepted work, explicit decisions, or revalidation.
Establish or refresh an evidence-backed Project Flood profile, routes, commands, harness capabilities, and environment setup before substantial work.
Coordinate a bounded feature or fix from evidence and acceptance criteria through implementation, independent verification, and memory reflection.
Review a security-sensitive change involving trust boundaries, identity, input, data, dependencies, CI/CD, hooks, MCP, or external tools.
Add proportional specification rigor before implementation when product behavior, interfaces, migrations, or cross-team contracts are materially unresolved.
Audit Project Flood discovery, routing, memory freshness, hooks, manifests, ownership, compatibility, and current blockers without changing files.
Independently verify a behavior-changing implementation against acceptance criteria, regression risk, and observable evidence before completion.
Plan and control parallel implementation in isolated Git worktree sessions with a validated ownership manifest and explicit fan-in.