bmad-agent-cora

Orchestrate dev-session boundaries and doc-harmonization routing for multi-agent repos.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-cora
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-cora
Source: https://github.com/jlenrique/course-DEV-IDE-with-AGENTS/tree/main/skills/bmad-agent-cora
Command: npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-cora

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pydantic, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Cora orchestrates dev-session boundaries and doc-harmonization routing for a multi-agent repo environment.

Core Features & Use Cases

  • Orchestrates session START/WRAPUP choreography and hot-start pair management.
  • Routes deterministic harmonization audits to Audra and manages memory sidecar state.
  • Maintains operator-facing narratives and boundaries for Marcus routing.

Quick Start

Initiate a new dev session by greeting the operator and summarizing the last session, then offer to run a harmonization sweep.

Frequently Asked Questions about bmad-agent-cora

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

FAQPage Schema
How do I orchestrate multi-agent dev-session boundaries for repo coherence?

Multi-agent dev-session orchestration is managed by applying choreography during session START and WRAPUP phases, maintaining hot-start pair management, and routing deterministic audits to ensure repo coherence.

What is doc-harmonization routing and when do I need it for my repository?

Doc-harmonization routing directs deterministic audits across a multi-agent repo environment. You trigger it during on-demand /harmonize invocations or session boundaries to maintain documentation consistency.

How do I start a dev session and run a harmonization sweep?

To start a dev session, initiate by greeting the operator and summarizing the last session, then offer to run a harmonization sweep to audit and align repository documentation.

Does this orchestration workflow require pydantic for session management?

Yes, pydantic is a required dependency for managing the memory sidecar state and data validation within the dev-session orchestration and harmonization routing workflow.

Can I use memory sidecar integration for safe delegation across multiple agents?

Memory sidecar integration enables safe delegation across agents by managing state and routing deterministic harmonization audits to designated agents like Audra, Paige, and Marcus.

What are the limitations of deterministic audits in a multi-agent repo environment?

Deterministic audits are bounded by the harmonization protocol routing rules, meaning delegation and operator-facing narratives are constrained to the defined session boundaries and agent-specific tasks.