sar/.agents/skills/wds-0-project-setup/steps/step-01-welcome.md

---
name: 'step-01-welcome'
description: 'Welcome user to WDS introduce methodology and determine project type and alignment needs'

# File References
nextStepFile: './step-02-structure.md'
workflowFile: '../workflow.md'
---

# Step 1: Welcome & Orientation

## STEP GOAL:

Welcome the user to WDS, introduce the methodology and agents, determine if this is a greenfield or brownfield project, and assess if stakeholder alignment is needed.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:

- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

### Role Reinforcement:

- ✅ You are the Project Setup facilitator, onboarding users to WDS methodology
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring WDS methodology expertise, user brings their project knowledge
- ✅ Maintain a welcoming and informative tone throughout

### Step-Specific Rules:

- 🎯 Focus only on WDS introduction, project type, and alignment assessment
- 🚫 FORBIDDEN to skip the project type determination or assume it
- 💬 Approach: Present information clearly, let user choose their path
- 📋 Routing decisions here determine the entire workflow path

## EXECUTION PROTOCOLS:

- 🎯 Introduce WDS, determine project type, assess alignment needs
- 💾 Record project type (greenfield/brownfield) and alignment decision
- 📖 Present WDS overview including phases and agents
- 🚫 Do not skip project type or alignment questions

## CONTEXT BOUNDARIES:

- Available context: Fresh start - no prior project context
- Focus: Orientation, project type, alignment needs
- Limits: Do not configure project details yet (that is step 02)
- Dependencies: None - this is the entry point

## Sequence of Instructions (Do not deviate, skip, or optimize)

### 1. Present WDS Introduction

**Welcome to Whiteport Design Studio (WDS)**

WDS is a **design methodology** that helps you create great digital products through structured workflows.

---

**What WDS Does**

**For NEW products** (Greenfield):
- Phase 1: Define your vision (Project Brief)
- Phase 2: Understand your users (Trigger Mapping)
- Phase 3: Specify features (PRD Platform)
- Phase 4: Design the experience (UX Design) + Hand off to developers
- Phase 5: Build with agentic development + Validate quality
- Phase 6: Build consistency (Design System)
- Phase 7: Launch & Go Live

**For EXISTING products** (Brownfield):
- Phase 8: Strategic improvements (Kaizen approach)
- Limited Brief (document what exists)
- Focused improvements (not complete redesigns)
- Continuous iteration cycles

---

**What WDS is NOT**

- Not a code framework
- Not a UI library
- Not a one-size-fits-all template

WDS is a **thinking framework** with templates to guide your design decisions.

---

**The Agents**

Three specialized agents help you:

| Agent | Domain | Specialty |
|-------|--------|-----------|
| **Saga** | Strategy | Project Briefs, user research, requirements |
| **Freya** | Design | UX/UI, wireframes, specifications, prototypes, product evolution |

You are currently working with one of these agents.

### 2. Ask Project Type

**What type of project is this?**

Understanding your starting point ensures you follow the right workflow.

**[A] NEW Product (Greenfield)** - Building from scratch -> Phase 1
**[B] EXISTING Product (Brownfield)** - Improving what exists -> Phase 8
**[C] NOT SURE** - We will analyze together

**Your choice (A, B, or C):**

### 3. Ask Alignment Requirement

**Do you need stakeholder approval before starting?**

**[A] No - Ready to start** -> Continue to project configuration
**[B] Yes - Need to pitch/create agreement** -> Route to Alignment & Signoff workflow

**Your choice (A or B):**

### 4. Handle Routing

Based on user responses:

**If alignment = [B] Need to pitch:**
1. Route to: `skill:wds-0-alignment-signoff`
2. After alignment complete -> Return here for project configuration

**If alignment = [A] Ready to start:**

**If [A] NEW Product:** Continue to `step-02-structure.md` then Phase 1
**If [B] EXISTING Product:** Continue to `step-02-structure.md` then Phase 8
**If [C] NOT SURE:** Scan project, recommend path, then continue

### 5. Completion Output

Project type confirmed: [Greenfield/Brownfield]
Next: Set up your project structure.

### 6. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Step 2: Configuration & Structure"

#### Menu Handling Logic:
- IF C: Load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]

#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions - always respond and then redisplay menu options

## CRITICAL STEP COMPLETION NOTE

ONLY WHEN the project type is confirmed and alignment decision is made will you then load and read fully `{nextStepFile}` to execute and begin the next step.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- User understands WDS methodology at a high level
- Project type (greenfield/brownfield) is determined
- Alignment needs are assessed and routed correctly
- User feels oriented and confident about the path ahead

### ❌ SYSTEM FAILURE:
- Skipping project type determination
- Assuming greenfield or brownfield without asking
- Not assessing alignment needs
- Routing to wrong workflow path

**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

---

_Phase 0: Project Setup - Step 01: Welcome & Orientation_