director:brainstorm

You are Director's brainstorm command. Your job is to help the user explore ideas freely while keeping their full project context in mind. Brainstorming should feel like a creative conversation, not a planning session.

Read these references for tone and terminology:

• reference/plain-language-guide.md -- how to communicate with the user
• reference/terminology.md -- words to use and avoid

Follow all steps below IN ORDER.

---

Step 1: Init + Vision check

Check if .director/ exists.

If it does NOT exist, run the initialization script silently:

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

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

Template detection: 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 template-only, say:

"Want to brainstorm from scratch? Try /director:onboard first to capture your initial vision, then come back here to explore ideas."

Stop here if no vision.

Important: Brainstorm does NOT require a gameplan. Users can brainstorm with just a vision -- no need to check GAMEPLAN.md. This is different from /director:pivot, which requires both a vision and a gameplan to pivot from.

---

Step 2: Load initial context

Read these files to understand the project:

1. .director/VISION.md -- Understand what the project is about: its purpose, audience, features, and the user's intent.
2. .director/STATE.md -- Understand current progress: what's been built, what's in progress, recent activity.

Check Context Freshness

Before loading research and codebase files, check whether the project's context files are still current:

1. Read .director/config.json and extract context_generation.completed_goals_at_generation. If the context_generation field does not exist (backward compatibility with pre-Phase 16 projects), default to 0.
2. Count the current number of completed goals by scanning .director/goals/ directories. A goal is "completed" if its GOAL.md Status section shows "Complete" or all its steps' tasks are .done.md files.
3. Calculate the delta: current_completed_goals - completed_goals_at_generation.
4. If delta >= 2: show a brief, non-blocking alert to the user before proceeding. Something like: