// Shape top ideas into actionable concept briefs using Disney Strategy — Dream, Reality, Critique.
| name | forge |
| description | Shape top ideas into actionable concept briefs using Disney Strategy — Dream, Reality, Critique. |
| version | 1.0.0 |
<degrees_of_freedom> MEDIUM-LOW — Structured shaping with high co-build ratio. User and AI refine together. </degrees_of_freedom>
ALWAYS apply Disney Strategy in sequence: Dreamer → Realist → Critic NEVER mix phases — keep Dreamer, Realist, and Critic strictly separate ALWAYS involve user in Critic phase — this is the primary co-build moment NEVER produce a Concept Brief without user validation of the core concept ALWAYS make Concept Briefs polished enough to share in a meeting - `.specsmd/ideation/shared/protocols/interaction-adaptation.md` — Generate:40% / Elicit:20% / Co-build:40% - `.specsmd/ideation/shared/protocols/diverge-converge.md` — Alternating diverge-converge (Disney pattern) - `references/disney-method.md` — Disney Creative Strategy for AI execution - `references/pitch-framework.md` — Concept structuring and pitch patterns Load shortlisted ideas from flame-report.md Present the shortlist: "Here are your top ideas. Which one shall we shape first?" Accept ideas as input Which ideas would you like to develop into full concepts? Select one idea to forge at a time (depth over breadth) Enter Dreamer mode — pure possibility, no limits Signal the mode: "Let's dream big first — no limits, no criticism, just possibility." Expand the idea with: - What's the most ambitious version of this? - What would it look like if everything went perfectly? - What adjacent possibilities does this unlock? - What would make users absolutely love this? - How could this grow beyond its initial scope? Present the expanded vision (3-5 paragraphs) Invite user additions: "What else would you dream for this?" Enter Realist mode — practical implementation thinking Signal the mode: "Now let's get practical. How would this actually work?" Ground the dream with: - What are the core components needed? - What's the simplest version that still delivers the magic? - What resources are required (time, money, skills, technology)? - What's the implementation sequence? - What existing solutions or tools can be leveraged? - What's the timeline from start to first value? Present a practical breakdown Ask: "Does this implementation path make sense? What would you adjust?" Enter Critic mode — constructive stress-testing Signal the mode: "Time to stress-test. Let's find the weak spots — and fix them." Present AI's concerns: - What's the biggest risk? - What assumption is most likely wrong? - What would a skeptic say? - Where could this fail? - What's the competitive response? What concerns you most about this concept? What feels risky? For each concern (AI's and user's), co-develop a mitigation: **Concern**: {concern} **Mitigation**: {proposed mitigation} Iterate until user is satisfied with mitigations Synthesize Dreamer + Realist + Critic into a polished Concept Brief Generate using template: templates/concept-brief.md.hbs Present the brief to user for final review How does this look? Any final adjustments? Save to: .specs-ideation/sessions/{session-id}/concept-briefs/{concept-name}.md Update session.yaml: track concept brief Ready to shape the next idea? If yes, return to step 1 with next idea Update session.yaml: phase → "complete" Your ideation session is complete! **Created**:
- Spark Bank: {N} ideas generated
- Flame Report: {M} ideas evaluated, {K} shortlisted
- Concept Briefs: {B} concepts shaped
All artifacts saved in .specs-ideation/sessions/{session-id}/
</output>
</check>
<output_artifacts>
| Artifact | Location | Template |
|---|---|---|
| Concept Brief | .specs-ideation/sessions/{id}/concept-briefs/{name}.md | ./templates/concept-brief.md.hbs |
| </output_artifacts> |
<success_criteria> Disney Strategy applied in strict sequence: Dreamer → Realist → Critic User actively involved in Critic phase (co-build) Concept Brief is polished enough to share in a meeting Risks identified AND mitigated (not just listed) Clear next steps included in every brief Session state updated and all artifacts saved </success_criteria>
Execute work items based on their assigned mode (autopilot, confirm, validate). Supports single-item and multi-item (batch/wide) runs.
Generate implementation walkthrough for human review after run completion. Documents decisions, changes, and verification steps.
Multi-perspective idea evaluation using Six Hats analysis, impact/feasibility scoring, and collaborative shortlisting.
Rapid idea generation with cross-domain diversity, anti-bias enforcement, and deep thinking.
Review code written during a run, auto-fix no-brainer issues, and suggest improvements requiring confirmation. Invoked after tests pass.
Display current run status and progress. Shows work item, mode, duration, and files changed.