bmad-agent-cd

Generate deterministic creative directives conforming to the Creative Directive Contract.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Dan's Creative Director role provides deterministic, validator-clean creative directives that align Marcus's envelope with downstream resolver workflows, ensuring consistent experience-profile framing and run guidance.

Core Features & Use Cases

  • Generates directive artifacts that include experience_profile, slide_mode_proportions, all 11 narration_profile_controls, and creative_rationale in strict conformance to the Creative Directive Contract.
  • Operates within Marcus's envelope to produce advisory directives that downstream components (resolver, Irene) can translate into run constants, while preserving contract discipline and sanctum boundaries.
  • Supports loading contextual sanctum state (config.yaml, memory) and updating durable state through the memory guidance workflow after each directive cycle.

Quick Start

Load Marcus's envelope and produce a validated, complete directive with all required fields.

Frequently Asked Questions about bmad-agent-cd

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

FAQPage Schema
How do I generate creative directives that pass strict contract validation?

To generate validator-clean creative directives, this Skill produces deterministic artifacts containing experience_profile, slide_mode_proportions, and all 11 narration_profile_controls in strict conformance to the Creative Directive Contract, validating output with a dedicated Python validator.

What is a creative directive contract and when do I need it for downstream resolver workflows?

A creative directive contract defines required fields like experience_profile and creative_rationale to ensure consistent experience-profile framing. You need it when aligning advisory directives for downstream components like resolvers to translate into run constants.

Can I use creative directives within an envelope workflow without breaking sanctum boundaries?

Yes, you can operate within an envelope to produce advisory directives that downstream components translate into run constants. This preserves contract discipline and maintains sanctum boundaries during directive generation cycles.

How do I update durable state after completing a creative directive cycle?

You update durable state by loading contextual sanctum state like config.yaml and memory, then applying the memory guidance workflow after each directive cycle to persist changes and maintain consistent run guidance across sessions.

What's the best way to ensure all 11 narration_profile_controls are included in a creative directive?

The best way to ensure all 11 narration_profile_controls are included is to use a deterministic generation process that validates output against the Creative Directive Contract before returning, guaranteeing complete and compliant directive artifacts.

Why does my creative directive fail validation when passing it to a downstream resolver?

Creative directives fail validation when required fields like experience_profile, slide_mode_proportions, or narration_profile_controls are missing or non-conformant. Running the dedicated Python validator before returning identifies and prevents these contract violations.