Orchestrates the CRISPR-Connect lifecycle for Connect opportunities, from idea through app building, deployment, LLO management, and closeout.

ACE is a Claude Code plugin with the same architecture as canopy: agents orchestrate skills, skills are prompt-based capability definitions, and MCP servers provide programmatic access to external systems.

Install as a Claude Code plugin, then:

/ace:run <opp-name> --mode review    # Run full lifecycle
/ace:run <opp-name> --dry-run        # Test without side effects
/ace:run <opp-name> --sandbox        # Route to staging endpoints
/ace:step <skill-name> <opp-name>    # Run a single step
/ace:status                          # Show all opportunities
/ace:docs                            # Generate playbook

• 5 agents — ace-orchestrator + 4 phase agents (app-builder, connect-setup, llo-manager, closeout)
• 19 skills — one per process step, each a SKILL.md that Claude executes
• 4 commands — run, step, status, docs
• 2 MCP servers — Google Drive (built), OCS (scaffold)
• 2 execution modes — auto (hands-off) and review (pauses at gates)

• Design Spec — full architecture and rationale
• Generated Playbook — human-readable process flow (generated from agent/skill definitions)
• Integration Specs — what APIs exist vs. need to be built
• ACE Web Harness Design — cross-cutting architecture spec for the browser-based ACE frontend
• IDD Stress-Test Observations — how to validate an IDD and verify LLO execution, with two sample IDDs worked through end-to-end

• ace-web — the browser-based chat + transcript harness for ACE. Django + Channels + React on GCP Cloud Run, built against the design spec above. Implementation plans (1A, 1B, 1C, 1D) live inside that repo at docs/plans/. Work on ace-web implementation happens directly in the ace-web checkout, not from this repo.

https://docs.google.com/spreadsheets/d/1XxcPxK1oYtDxcfmElBb73U2UtLYEodiaMUazjmEVAWE/edit