feat: Material Analysis Phase — analyze docs before asking questions

When users provide existing materials (PRD, brief, research), Saga now:
1. Reads and extracts information into categories (vision, users, etc.)
2. Presents findings ONE category at a time for user confirmation
3. Identifies gaps after all confirmed categories
4. Plans which steps need full conversation vs quick confirmation
5. Skips exploratory questions for already-confirmed topics

Updated 13 files:
- working-with-existing-materials.md: complete rewrite with new protocol
- step-01-init.md: Material Analysis Phase trigger after welcome
- Steps 02-11: "Check Material Analysis Status" gate before exploration

Fixes the "black hole" problem where Saga acknowledged documents
but then asked questions whose answers were in those documents.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mårten Angner 2026-03-18 13:30:26 +01:00
parent dd5fa936bb
commit 6287dce0b9
13 changed files with 355 additions and 80 deletions

View File

@ -1,16 +1,16 @@
# Working with Existing Materials
**Purpose:** Guide for naturally incorporating existing materials into conversational PB workflow.
**Purpose:** Guide for incorporating existing materials into the PB workflow. When users provide documentation, Saga MUST analyze it first, present findings for confirmation, and only ask questions about gaps.
---
## Core Principles
1. **Reference, don't re-ask** - Build on documented work
2. **Validate currency** - "Is this still accurate?"
3. **Focus on gaps** - What's missing or needs refinement?
4. **Document refinement** - Capture UPDATE conversation, not just creation
5. **Stay casual** - No judgment about what exists or doesn't
1. **Analyze first, ask second** — Read and extract before any questions
2. **Present, don't pocket** — Show the user what you found, structured by topic
3. **Confirm step by step** — Each extracted insight gets a yes/no/refine from the user
4. **Only ask about gaps** — If the answer is in the document, don't ask the question
5. **Stay casual** No judgment about what exists or doesn't
---
@ -29,26 +29,126 @@ existing_materials:
context_notes: "[brief notes]"
```
**If materials exist:** Read them before starting PB steps
**If materials exist:** Read them COMPLETELY before starting PB steps. Then run the Material Analysis Phase.
---
## Adaptation Pattern
## Material Analysis Phase (MANDATORY when materials exist)
### Opening Adaptation
This phase runs ONCE, after Step 1 (Init) and BEFORE Step 2 (Vision). It replaces the old "reference and ask" pattern with "analyze, present, confirm, then fill gaps."
**Without materials:**
> "Let's start with vision. What are you envisioning?"
### Step A: Read and Extract
**With materials:**
> "I see you mentioned [reference from materials]. Let's build on that - tell me more."
Read every provided document completely. Extract information into these categories:
### Follow-Up Patterns
| Category | What to look for |
|----------|-----------------|
| **Vision** | Purpose, mission, "why this exists", aspirational statements |
| **Positioning** | Target market, differentiators, alternatives, category |
| **Business Model** | Revenue, pricing, monetization, cost structure |
| **Target Users** | User types, personas, segments, pain points |
| **Product Concept** | Core features, key interactions, product shape |
| **Success Criteria** | KPIs, metrics, milestones, definition of done |
| **Competitive Landscape** | Named competitors, alternatives, market gaps |
| **Constraints** | Technical limits, budget, timeline, team, regulations |
| **Tone & Brand** | Voice, personality, visual direction, existing brand |
- **Validate:** "You wrote X - is that still accurate?"
- **Fill gaps:** "Your brief mentions Y, but I'm curious about Z..."
- **Refine:** "When you said X, did you mean [interpretation]?"
- **Update:** "Has your thinking evolved since you wrote this?"
For each category, note:
- **Complete** — enough information to draft this section
- **Partial** — some information, needs clarification or expansion
- **Missing** — not covered in the materials
### Step B: Present the Analysis
Present your findings to the user, organized by category. Use this pattern:
```
I've read through your materials. Here's what I found — let me walk you through
it section by section so you can confirm, correct, or add to each one.
**Vision**
From your [document name]: "[relevant quote or paraphrase]"
My interpretation: [your synthesis in one sentence]
→ Does this capture it? Anything that's evolved?
**Positioning**
From your [document name]: "[relevant quote or paraphrase]"
My interpretation: [your synthesis]
→ Still the direction?
[...continue for each category that has content...]
```
**Rules for presentation:**
- Present ONE category at a time. Wait for user response before moving to the next.
- Quote or closely paraphrase the source material so the user can see what you're working from
- Add your interpretation — this is where your strategic thinking adds value
- Ask for confirmation explicitly: ✓ confirm / ✗ reject / ~ refine
- If the user refines, capture the refinement before moving on
### Step C: Identify Gaps
After all extracted categories are confirmed, present the gaps:
```
That covers what I found in your materials. Here's what we still need to explore:
- [Gap 1]: Not covered in your documents
- [Gap 2]: Mentioned briefly but needs more depth
- [Gap 3]: Implied but not explicit
These are the topics I'll focus our conversation on.
The rest is already solid from your materials.
```
### Step D: Adjusted Workflow Plan
Tell the user which steps will be quick confirmations vs. full conversations:
```
Here's how the rest of the workflow will go:
Quick confirmation (already covered):
- Vision ✓ — confirmed from your materials
- Target Users ✓ — confirmed from your materials
Needs conversation (gaps to fill):
- Competitive Landscape — not covered yet
- Success Criteria — mentioned but needs specifics
- Constraints — partially covered, need technical details
This should be much faster since you've already done a lot of the thinking.
```
---
## Adapted Step Execution (after Material Analysis)
Once the Material Analysis Phase is complete, each subsequent step runs in one of two modes:
### Confirmation Mode (category = Complete)
The step's content was already extracted and confirmed during the analysis phase. The step becomes a quick pass:
1. Reference the confirmed content: "We already confirmed your vision as [synthesis]. I've documented it."
2. Ask if anything to add: "Anything else before we move on?"
3. If nothing: document and advance
4. If additions: capture them, update, confirm, advance
**This replaces the full exploratory conversation.** Do NOT re-ask questions the user already answered during the analysis phase.
### Gap-Filling Mode (category = Partial or Missing)
The step needs real conversation, but scoped to what's missing:
1. Reference what IS known: "From your materials, I know [X]. What I'm missing is [Y]."
2. Explore only the gap — do not re-cover confirmed ground
3. Synthesize the gap content with the confirmed content
4. Present the combined picture for confirmation
### CRITICAL RULE
**Never re-ask a question whose answer was already confirmed in the Material Analysis Phase.** If the user confirmed their vision during analysis, Step 2 (Vision) should take 30 seconds, not 10 minutes. The exploratory conversation pattern is for discovery — when materials exist, the discovery already happened.
---
@ -56,15 +156,14 @@ existing_materials:
**Apply to all conversational steps** (2, 3, 5, 7, 7a, 8, 9, 10, 11, 12):
| Step | No Materials | With Materials |
|------|-------------|----------------|
| Vision (2) | "What are you envisioning?" | "You mentioned [vision]. Tell me more." |
| Positioning (3) | "Let's explore positioning." | "Your brief positions this as [quote]. Still accurate?" |
| Users (7) | "Who are ideal users?" | "You described [archetypes]. Still primary users?" |
| Concept (7a) | "What's the core concept?" | "I see [concept from materials]. Tell me more about that principle." |
| Success (8) | "What does success look like?" | "You mentioned success means [quote]. Still the goal?" |
**Pattern:** Reference existing → Validate → Build on it
| Step | No Materials | With Materials (Confirmed) | With Materials (Gap) |
|------|-------------|---------------------------|---------------------|
| Vision (2) | Full exploration | "Confirmed as [X]. Anything to add?" | "You mentioned [X] but I need [Y]." |
| Positioning (3) | Full exploration | "Confirmed as [X]. Anything to add?" | "Target is clear, but differentiator needs work." |
| Business Model (5) | Full exploration | "Confirmed as [X]. Anything to add?" | "Revenue model clear, pricing needs detail." |
| Users (7) | Full exploration | "Confirmed as [X]. Anything to add?" | "Primary users clear, need to explore secondary." |
| Concept (7a) | Full exploration | "Confirmed as [X]. Anything to add?" | "Core concept clear, need interaction model." |
| Success (8) | Full exploration | "Confirmed as [X]. Anything to add?" | "Goals clear, need measurable KPIs." |
---
@ -73,83 +172,91 @@ existing_materials:
When materials exist, capture:
1. **What existed:** Quote/summarize existing material
2. **Validation:** User's response to "Is this still accurate?"
3. **Refinement:** What changed, added, or clarified
4. **Why:** Rationale for changes
5. **Synthesis:** Updated version (old + new integrated)
2. **Analysis presented:** What Saga extracted and interpreted
3. **User response:** Confirmed / Refined / Rejected
4. **Gaps identified:** What was missing
5. **Gap conversation:** Discovery for missing pieces only
6. **Synthesis:** Final version (confirmed material + gap fills + refinements)
**Template:**
```markdown
**Existing context:** [What was documented]
**Source material:** [Document name, relevant section]
**Opening:** "I see [reference]. [Question]"
**Saga's extraction:**
> [Quote from material]
Interpretation: [Saga's synthesis]
**User response:** [Confirmed/refined/changed]
**User response:** [Confirmed ✓ / Refined ~ / Rejected ✗]
[If refined/rejected: what changed and why]
**Key exchanges:**
- [Exploration]
- [Gaps filled]
- [Evolution]
**Gaps explored:**
- [Gap topic]: [Discovery conversation summary]
**Reflection checkpoint:**
"Building on your earlier work: [synthesis].
Keeps [solid parts], adds [new], refines [changed].
Does that capture it?"
**Final synthesis:** [Confirmed content + gap fills integrated]
**User confirmation:** [Confirmed / Corrected]
**Final:** [Updated artifact]
```
---
## Common Scenarios
**Scenario: Comprehensive PRD provided**
1. Read it thoroughly — this is the primary source
2. Run full Material Analysis Phase (Steps A-D)
3. Most categories will be Complete — workflow becomes mostly confirmations
4. Focus conversation on strategic gaps (positioning nuance, success metrics, constraints)
5. Result: 15-minute workflow instead of 60-minute workflow
**Scenario: Previous brief exists**
1. Read it thoroughly
2. Identify solid vs gaps/unclear
3. Open: "I read your brief. [Strong points] captured well. Questions about [gaps]."
4. Explore gaps conversationally
5. Dialog: what was there + what we added + why
2. Run Material Analysis Phase
3. Identify what's solid vs outdated vs missing
4. Present: "Your brief from [date] covers X, Y, Z well. Has anything evolved?"
5. Focus on evolution and gaps
**Scenario: Existing website**
1. Review site (if URL in materials)
2. Note current positioning/tone/UX
3. Reference: "I looked at your site. It positions you as [observation]. Still the direction?"
2. Extract positioning, tone, target audience signals
3. Present observations: "Your site positions you as [X], targets [Y], tone is [Z]"
4. Use as baseline for "what's changing?"
**Scenario: Brand guidelines exist**
1. Read guidelines (voice, values, identity)
2. Reference when discussing tone: "Your guidelines describe tone as [quote]. Match exactly or evolve?"
3. Don't re-ask defined things (colors, values)
4. Focus on how brand translates to this project
2. Extract: personality, tone, visual direction, constraints
3. Present: "Your brand guidelines define [X]. These carry forward unless you say otherwise."
4. Mark brand-related categories as Complete
5. Focus on how brand translates to this specific product
**Scenario: Research exists**
1. Review findings
2. Reference insights: "Your research showed [finding]. Great insight for..."
3. Validate currency: "Is this still what you hear from customers?"
**Scenario: Research / user interviews exist**
1. Review findings thoroughly
2. Extract: user pain points, needs, behaviors, quotes
3. Present: "Your research identified these user patterns: [list]"
4. Validate currency: "Is this still what you hear from users?"
5. Use as foundation for Target Users and Success Criteria steps
---
## What NOT to Do
❌ Ignore existing materials (if outline says they exist)
❌ Make users repeat documented work
❌ Assume everything is still current (validate!)
❌ Judge quality of existing work
❌ Create separate "refinement workflow" (same conversational pattern, just adapt openings)
- Say "thank you" and move on as if nothing was provided
- Pocket the information silently and only reference it in passing
- Ask questions whose answers are clearly in the provided documents
- Make the user repeat or re-explain documented work
- Assume everything is still current without asking (validate!)
- Judge quality of existing work
- Skip the Material Analysis Phase and go straight to step-by-step questions
---
## Benefits
✅ Efficiency - Don't re-explore documented areas
✅ Continuity - Build on previous work
✅ Respect - Acknowledge existing thinking
✅ Focus - Spend time on gaps/unclear areas
✅ Natural flow - Same pattern, context-aware
✅ Rich dialog - Captures refinement, not just creation
- Efficiency — 15 minutes instead of 60 when materials are comprehensive
- Respect — Acknowledges the thinking already done
- Trust — User sees that Saga actually read and understood their materials
- Focus — Conversation time spent on real gaps, not re-discovery
- Quality — Final brief builds on confirmed foundation, not fresh guesses
---
@ -157,16 +264,18 @@ Does that capture it?"
**Check:** `existing_materials.has_materials` in outline
**If true:**
1. Read materials before starting PB
2. Adapt openings to reference what exists
3. Validate currency with each step
4. Fill gaps conversationally
5. Document: old + new + why
**If true — run Material Analysis Phase:**
1. Read ALL materials completely
2. Extract information into categories (vision, positioning, users, etc.)
3. Present findings ONE category at a time, wait for confirmation
4. Identify gaps after all categories confirmed
5. Tell user which steps will be quick vs. need conversation
6. Execute steps in Confirmation Mode or Gap-Filling Mode accordingly
**Dialog pattern:** Existing → Validate → Refine → Synthesize → Confirm
**If false — run standard discovery:**
1. Full exploratory conversation per step
2. Standard pattern: Open → Explore → Reflect → Synthesize → Confirm
---
**Remember:** Not a separate workflow - same conversational pattern, just context-aware.
If materials exist, read and adapt. If not, explore from scratch. Either way, natural conversation.
**The golden rule:** If the user gave you a document, they expect you to USE it — not just acknowledge it. Analyze it, show them what you found, and only ask about what's missing.

View File

@ -56,9 +56,28 @@ Welcome the user and explain that this is their strategic foundation. This workf
- Competitive landscape (what alternatives exist)
- Constraints & context (real-world limitations)
Set time expectations (30-60 minutes) and ask about any existing context that should be considered.
Set time expectations and ask about any existing context that should be considered.
### 2. Design Log Update
If the user provides or has provided existing materials (PRD, brief, research, website, guidelines), acknowledge them and tell the user you will analyze them before starting the strategic conversation.
### 2. Material Analysis Phase (if materials exist)
**MANDATORY when `existing_materials.has_materials` is true or when the user provides documents during this step.**
Load and follow `src/data/agent-guides/saga/working-with-existing-materials.md` — specifically the **Material Analysis Phase** (Steps A through D).
This means:
1. **Read** every provided document completely
2. **Extract** information into categories (vision, positioning, users, business model, etc.)
3. **Present** your findings ONE category at a time — quote the source, add your interpretation, ask the user to confirm/refine/reject each one
4. **Identify gaps** — tell the user which topics are not covered in their materials
5. **Plan the workflow** — tell the user which steps will be quick confirmations vs. full conversations
**Time estimate adjustment:** If materials are comprehensive, tell the user: "Since you've already done a lot of the thinking, this will be faster — probably 15-20 minutes to confirm and fill gaps, rather than a full 60-minute discovery."
**CRITICAL:** Do NOT skip this phase and jump to Step 2 (Vision). The analysis must happen here, before any step-by-step workflow begins. If you acknowledge the materials and then proceed to ask "What's your vision?" — that is a SYSTEM FAILURE.
### 3. Design Log Update
**Mandatory:** Update `dialog/00-context.md` before marking this step complete.
Fill in:
@ -89,8 +108,9 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
### ✅ SUCCESS:
- User welcomed and expectations set
- Time estimate communicated (30-60 minutes)
- Time estimate communicated
- Existing context gathered (or noted as none)
- If materials provided: Material Analysis Phase completed (extract → present → confirm → identify gaps → plan workflow)
- Design log updated with project metadata
- User confirms readiness to proceed
@ -99,5 +119,8 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
- Generated content without user input
- Skipped design log update
- Did not wait for user confirmation before proceeding
- Materials provided but NOT analyzed (acknowledged and moved on = FAILURE)
- Materials analyzed but NOT presented to user for confirmation (pocketed silently = FAILURE)
- Asked questions whose answers are clearly in the provided documents
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

View File

@ -48,6 +48,19 @@ Help the user explore and articulate their vision through natural conversation,
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If vision was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed vision: "We confirmed your vision as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to Step 5 (State Update)
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip substeps 1-3 below — they are for discovery, not re-discovery
**If no materials exist or vision was not covered:**
Run the full exploration below.
### 1. Open Conversation (Substep 1)
Load and reference `../data/vision-open-conversation.md`. Adapt opening question to context, invite user to think out loud about what they are building and why it matters.

View File

@ -48,6 +48,19 @@ Help the user explore and articulate their positioning through natural conversat
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If positioning was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed positioning: "We confirmed your positioning as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or positioning was not covered in materials:**
Run the full exploration below.
### 1. Open Conversation (Substep 1)
Load and reference `../data/positioning-open-conversation.md`. Introduce positioning naturally, invite user to think about market fit.

View File

@ -48,6 +48,19 @@ Help the user identify and understand their business model (B2B, B2C, or both) t
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If business model was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed business model: "We confirmed your business model as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or business model was not covered in materials:**
Run the full exploration below.
### 1. Open the Conversation
Start naturally based on context. If they have mentioned customers already, reference that. If unclear, ask about who pays for the product. Adapt tone to stakes level.

View File

@ -54,6 +54,19 @@ Help the user define their ideal business customer profile, including company ch
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If business customers were already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed business customers: "We confirmed your business customers as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or business customers were not covered in materials:**
Run the full exploration below.
### 1. Guide Business Customer Definition
Ask about company size, industry, decision-making structure, and budget authority. Also identify buying roles (buyer vs. user).

View File

@ -54,6 +54,19 @@ Help the user define their ideal customer profile by exploring who we are design
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If target users were already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed target users: "We confirmed your target users as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or target users were not covered in materials:**
Run the full exploration below.
### 1. Guide User Description
Guide user to describe their ideal users in detail. Ask about their role, demographics, daily experience, frustrations, goals, and current solutions. Also identify any secondary users or stakeholders.

View File

@ -54,6 +54,19 @@ Capture the designer's STRUCTURAL vision — the founding idea, key concept, or
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If product concept was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed product concept: "We confirmed your product concept as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or product concept was not covered in materials:**
Run the full exploration below.
### 1. Open the Concept Conversation
Check for existing materials first. Without materials: Ask about the core concept, the structural idea, what everything builds from. With materials: Reference what they mention and probe deeper.

View File

@ -47,6 +47,19 @@ Help the user explore and define what success looks like through conversational
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If success criteria were already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed success criteria: "We confirmed your success criteria as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or success criteria were not covered in materials:**
Run the full exploration below.
### 1. Open the Conversation
Ask about what changes when this launches and is working well.

View File

@ -47,6 +47,19 @@ Help user explore alternatives and discover their unfair advantage. Explore what
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If competitive landscape was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed competitive landscape: "We confirmed your competitive landscape as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or competitive landscape was not covered in materials:**
Run the full exploration below.
### 1. Open with Alternatives
Start broad: what do people do today? Include manual solutions, do-nothing, different approaches.

View File

@ -47,6 +47,19 @@ Help user identify constraints as design parameters.
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If constraints were already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed constraints: "We confirmed your constraints as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or constraints were not covered in materials:**
Run the full exploration below.
### 1. Frame Positively
Design parameters.

View File

@ -47,6 +47,19 @@ Establish the technical platform strategy and device support requirements that w
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If platform strategy was already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed platform strategy: "We confirmed your platform strategy as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or platform strategy was not covered in materials:**
Run the full exploration below.
### 1. Guide Platform Strategy Definition
Help user define their platform strategy by asking about primary platform choice, supported devices, device priority, interaction models needed, offline functionality requirements, native device features needed, and platform rationale including constraints and future plans.

View File

@ -47,6 +47,19 @@ Establish the product's communication personality and style for consistent UI mi
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 0. Check Material Analysis Status
**If tone and brand personality were already confirmed during the Material Analysis Phase (Step 1):**
Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
1. Reference the confirmed tone: "We confirmed your tone and brand personality as [synthesis from analysis phase]."
2. Ask: "Anything to add or refine before I document it?"
3. If nothing: synthesize, document, and advance to the Design Log / State Update step
4. If additions: capture them, update the synthesis, confirm, then advance
5. Skip the exploratory substeps below — they are for discovery, not re-discovery
**If no materials exist or tone was not covered in materials:**
Run the full exploration below.
### 1. Analyze Product Context
Review what you've learned:
- Vision & positioning