Overview

Create method-tier and on-demand-tier instruction files for the Solution Space: Methods 4 (Brainstorming), 5 (User Concepts), and 6 (Low-Fidelity Prototypes). Also create the Solution Space exit handoff prompt. These methods guide users from divergent ideation through concept articulation to rapid experimentation.

Deliverables

Key Design Notes

• Method 5 includes M365 Copilot image prompt generation for concept visualization. The coach produces descriptive prompts users copy-paste into M365 Copilot.
• Method 6 enforces lo-fi quality constraints. Artifacts should signal "still being shaped" to prevent premature commitment.
• Each method has 3 sub-methods (planning → execution → documentation) and 2 specialized hats.

Artifact creation uses the RPI pipeline. All instruction and prompt files follow prompt-builder standards. After Phase 3 handoff integration evaluation, assess whether DT-native prompt variants are warranted for Solution Space methods.

Dependencies

• Phase 1 complete (coaching identity and ambient instructions)
• Methods 4-6 method-tier files depend only on Phase 1
• Deep files depend on their corresponding method-tier files

Success Criteria

• Three method-tier instructions with proper globs and ~1,500-2,000 tokens each
• Three deep instruction files with ~2,000-3,000 tokens each
• Lo-fi quality constraints enforced in all Solution Space methods
• M365 Copilot image prompt generation integrated into Method 5
• Solution Space exit handoff prompt produces RPI-ready .prompt.md targeting task-researcher (feasibility) or task-planner with concept rationale and prototype learnings
• All files pass task-reviewer validation against prompt-builder standards
• Artifacts registered in collections/design-thinking.collection.yml with path and kind fields
• Artifacts registered in collections/hve-core-all.collection.yml with path and kind fields
• npm run plugin:generate run after updating collection manifests