grace-multiagent-execute

Execute a GRACE development plan with multiple agents while keeping planning artifacts and shared context consistent.

Prerequisites

• docs/development-plan.xml must exist with module contracts and implementation order
• docs/knowledge-graph.xml must exist
• docs/verification-plan.xml should exist with module-local verification commands and gate expectations
• if docs/operational-packets.xml exists, use it as the canonical packet and delta reference
• If the plan or graph is missing, stop immediately and tell the user to run $grace-plan themselves before dispatching a large wave
• If the verification plan is missing or still skeletal, stop immediately and tell the user to run $grace-verification themselves before dispatching a large wave
• Prefer this skill only when module-local verification commands already exist or can be defined clearly

Core Principle

Parallelize module implementation, not architectural truth.

• One controller owns shared artifacts: docs/development-plan.xml, docs/knowledge-graph.xml, docs/verification-plan.xml, phase status, and execution queue
• Worker agents own only their assigned module files and module-local tests
• Reviewers validate module outputs before the controller merges graph and plan updates
• Speed should come from better context packaging, batched shared-artifact work, and scoped reviews - not from letting workers invent architecture