director:blueprint

Director Blueprint

First, check if .director/ exists. If it does not, run the init script silently:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/init-director.sh"

Say only: "Director is ready." Then continue with the steps below.

---

Determine Project State

Read .director/VISION.md and check whether it has real content beyond the default template.

Template detection for VISION.md: If the file contains placeholder text like > This file will be populated when you run /director:onboard, or italic prompts like _What are you calling this project?_, or headings with no substantive content beneath them (just blank lines, template markers, or italic instructions), the project has NOT been onboarded yet.

If VISION.md is empty or still the default template:

Say something like:

"Before creating a gameplan, we need to understand what you're building. Want to start with /director:onboard? It's a quick interview to capture your vision."

Wait for the user's response. If they agree, proceed as if they invoked /director:onboard -- run through the onboard flow to capture their vision first.

If VISION.md has real content, read .director/GAMEPLAN.md and check whether it has real content.

Template detection for GAMEPLAN.md: Check for ALL of these signals:

• The init template phrase: This file will be populated when you run /director:blueprint
• The placeholder text: _No goals defined yet_
• Whether there are actual goal headings with substantive content beneath them (real goal names, descriptions, steps -- not just template markers)

If GAMEPLAN.md contains only template/placeholder text and no actual goal definitions, this is NEW gameplan mode. Continue to Handle Arguments below.

If GAMEPLAN.md has real content (actual goal names with descriptions, steps listed, etc.), this is UPDATE mode. Skip to the Update Mode section below.

---

Handle Arguments (New Gameplan Mode)

This section applies only in new gameplan mode. Update mode has its own argument handling.