command-center-1c

Use to deliver an approved OpenSpec change through execution matrix, Beads, checks, and handoff.

Use to verify the full pool run flow on a live contour through report and OData evidence.

Use to inspect, restart, and verify local frontend/backend runtimes with targeted probes.

Use for shipped UI action journal, request correlation, WebSocket churn, or frontend observability work.

Work with 1C databases via OData protocol: create batch operations, handle transactions (< 15 seconds!), debug OData requests.

Execute DevOps tasks for CommandCenter1C: start/stop services locally (host machine), check health endpoints, view logs, run migrations. Use when user needs to start development environment, check service status, debug deployment issues, or mentions local development, health checks, logs, restart.

Navigate monorepo structure, locate components, explain service dependencies.

Create Go services, Django apps, or React components following project conventions. Generates code from templates. Use when adding new functionality, endpoints, or UI components.

Track progress in Balanced approach roadmap (16 weeks), identify current phase/week, suggest next tasks from sprint plan, validate completed work.

Run and debug tests across all components: Go unit tests, Django tests, React tests, integration tests. Check coverage, analyze failures, suggest fixes. Use when user wants to run tests, check test coverage, debug test failures, or mentions testing, pytest, go test, jest.