diff --git a/src/modules/wds/course/deliverables/design-delivery-prd.md b/src/modules/wds/course/deliverables/design-delivery-prd.md index 9cbd960f..27f92457 100644 --- a/src/modules/wds/course/deliverables/design-delivery-prd.md +++ b/src/modules/wds/course/deliverables/design-delivery-prd.md @@ -1,9 +1,17 @@ -# Deliverable 07: Design Delivery PRD +# Deliverable: Design Delivery PRD **Package everything developers need - turn specs into buildable epics and stories** --- +## About WDS & the Design Delivery PRD + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Design Delivery PRD** is the final bridge between design and development. Idunn the Technical Architect takes your page specifications and design system and organizes them into developer-ready epics, stories, and implementation sequences. This is where your design work transforms into actionable development tasks. + +--- + ## What Is This Deliverable? The Design Delivery PRD organizes your page specifications and design system into developer-ready documentation: @@ -14,12 +22,30 @@ The Design Delivery PRD organizes your page specifications and design system int - Implementation sequence - Links back to page specifications -**Created by:** Idunn the WDS Technical Architect Agent +**Created by:** Idunn the Technical Architect **When:** Phase 7 - After page specs and design system are complete **Format:** PRD document with epics, stories, and implementation guide --- +## Why This Matters + +**Without a Design Delivery PRD:** +- ❌ Developers start coding without full context +- ❌ Implementation order is inefficient +- ❌ Design intent gets lost in translation +- ❌ "What did you mean?" meetings daily +- ❌ Specifications sit unused + +**With a Design Delivery PRD:** +- ✅ Clear implementation roadmap +- ✅ Developers understand the full picture +- ✅ Efficient build sequence +- ✅ Specifications become actionable tasks +- ✅ Reduced rework and confusion + +--- + ## What's Included ### 1. Implementation Strategy @@ -61,12 +87,72 @@ For each story: --- +## The Dialog with Your Technical Partner: Idunn the Technical Architect + +**The Process (2-3 hours):** + +Idunn the Technical Architect helps you organize for development: + +``` +Idunn the Technical Architect: "Let's package this for development. I've analyzed + your 8 page specifications. I see 3 major epics." + +You: "What are they?" + +Idunn the Technical Architect: "Epic 1: User Authentication & Profile. + Epic 2: Project Dashboard. + Epic 3: Task Management. Sound right?" + +You: "Perfect! Which should we build first?" + +Idunn the Technical Architect: "Authentication is foundational - everything depends on it. + Dashboard next, then Task Management. I'll create stories..." + +You: "How many stories total?" + +Idunn the Technical Architect: "15 stories across the 3 epics. Each links directly to + your page specifications with Object IDs." +``` + +As you work together, Idunn the Technical Architect creates: +- ✅ Epic breakdown +- ✅ User stories with acceptance criteria +- ✅ Implementation sequence +- ✅ Component mapping +- ✅ Handoff documentation + +Then you review together: + +``` +Idunn the Technical Architect: "Here's your Design Delivery PRD. Ready for development?" + +You: "Move the profile settings story to phase 2 - not critical for MVP." + +Idunn the Technical Architect: "Moved to Epic 4: Post-MVP Enhancements. ✅ PRD is ready." +``` + +**Result:** Design Delivery PRD ready for development team handoff + +--- + ## Example *(Example coming soon)* --- +## Agent Activation + +To start creating your Design Delivery PRD: + +``` +@idunn Let's create a Design Delivery PRD to hand off to development. +``` + +Idunn the Technical Architect will analyze your specifications and guide the organization process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 10: Design Delivery](../module-10-design-delivery/tutorial-10.md) @@ -75,24 +161,13 @@ For each story: --- -## Why This Matters +## Getting Started with WDS -Without a Design Delivery PRD: -- Developers start coding without full context -- Implementation order is inefficient -- Design intent gets lost in translation -- "What did you mean?" meetings daily -- Specifications sit unused +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With a Design Delivery PRD: -- Clear implementation roadmap -- Developers understand the full picture -- Efficient build sequence -- Specifications become actionable tasks -- Reduced rework and confusion +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Component Library & Design Tokens](design-system.md) **Next Steps:** Hand off to development! (Testing handled by BMM workflows) - diff --git a/src/modules/wds/course/deliverables/design-system.md b/src/modules/wds/course/deliverables/design-system.md index 146544f9..6e6354bf 100644 --- a/src/modules/wds/course/deliverables/design-system.md +++ b/src/modules/wds/course/deliverables/design-system.md @@ -1,9 +1,17 @@ -# Deliverable 06: Component Library & Design Tokens +# Deliverable: Component Library & Design Tokens **Extract reusable patterns - scale your design efficiently across the entire product** --- +## About WDS & the Design System + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Design System** is where consistency becomes effortless. After specifying your initial pages, Freyja the UX Designer helps you identify reusable patterns and extract them into a structured component library. This becomes the foundation for rapid, consistent design and development. + +--- + ## What Is This Deliverable? The Design System documents all reusable components, patterns, and design tokens: @@ -13,12 +21,30 @@ The Design System documents all reusable components, patterns, and design tokens - Accessibility guidelines - Component usage rules -**Created by:** Freyja the WDS UX Designer Agent (extraction from page specs) +**Created by:** Freyja the UX Designer (extraction from page specs) **When:** Phase 6 - After initial page specifications are complete **Format:** Structured component library documentation --- +## Why This Matters + +**Without a Design System:** +- ❌ Every page/screen designed from scratch +- ❌ Inconsistent UI across product +- ❌ Developers reinvent components repeatedly +- ❌ No single source of truth +- ❌ Design debt accumulates fast + +**With a Design System:** +- ✅ Rapid design and development +- ✅ Consistent user experience +- ✅ Easier maintenance and updates +- ✅ Onboarding new designers/developers faster +- ✅ Scalable design operations + +--- + ## What's Included ### 1. Design Tokens @@ -56,12 +82,72 @@ For each component: --- +## The Dialog with Your Design Partner: Freyja the UX Designer + +**The Process (2-3 hours):** + +Freyja the UX Designer helps you extract patterns from your page specs: + +``` +Freyja the UX Designer: "I've analyzed your page specifications. I found 8 button + variants across 5 pages. Let's standardize them." + +You: "Yes! Primary, secondary, and text buttons are intentional. + The others are inconsistent." + +Freyja the UX Designer: "Perfect! I'll document those 3 as your button system. + What about colors?" + +You: "Brand blue #2563EB for primary actions, gray for secondary, + red for destructive actions." + +Freyja the UX Designer: "Got it. I see you're using 3 different card components. + Are those variants of one pattern or separate components?" + +You: "They're all the same - just different content inside." + +Freyja the UX Designer: "Excellent - I'll document one card component with content slots..." +``` + +As you work together, Freyja the UX Designer creates: +- ✅ Design token system +- ✅ Component specifications +- ✅ Usage guidelines +- ✅ Accessibility standards +- ✅ Pattern library + +Then you review together: + +``` +Freyja the UX Designer: "Here's your Design System. Does this cover your needs?" + +You: "Add a 'ghost button' variant for low-emphasis actions." + +Freyja the UX Designer: "Added COMP_BUTTON_GHOST to button variants. ✅ System is complete." +``` + +**Result:** Design System saved to `/docs/5-design-system/` + +--- + ## Example *(Example coming soon)* --- +## Agent Activation + +To start creating your Design System: + +``` +@freyja Let's extract a Design System from my page specifications. +``` + +Freyja the UX Designer will analyze your existing specs and guide the extraction process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 09: Design System](../module-09-design-system/tutorial-09.md) @@ -70,24 +156,13 @@ For each component: --- -## Why This Matters +## Getting Started with WDS -Without a Design System: -- Every page/screen designed from scratch -- Inconsistent UI across product -- Developers reinvent components repeatedly -- No single source of truth -- Design debt accumulates fast +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With a Design System: -- Rapid design and development -- Consistent user experience -- Easier maintenance and updates -- Onboarding new designers/developers faster -- Scalable design operations +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Page Specifications & Prototypes](page-specifications.md) **Next Deliverable:** [Design Delivery PRD](design-delivery-prd.md) - diff --git a/src/modules/wds/course/deliverables/page-specifications.md b/src/modules/wds/course/deliverables/page-specifications.md index 8d0b8dcd..904f54dd 100644 --- a/src/modules/wds/course/deliverables/page-specifications.md +++ b/src/modules/wds/course/deliverables/page-specifications.md @@ -1,9 +1,17 @@ -# Deliverable 05: Page Specifications & Prototypes +# Deliverable: Page Specifications & Prototypes **Turn sketches into complete specs - capture WHAT it looks like AND WHY you designed it that way** --- +## About WDS & Page Specifications + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**Page Specifications** are where your design thinking becomes implementation-ready. Instead of handing off a Figma file with vague annotations, you create detailed specs that capture content, structure, strategy, and rationale—specifications that developers AND AI agents can execute with precision. + +--- + ## What Is This Deliverable? Page Specifications are detailed documentation for each page/screen in your product: @@ -13,12 +21,29 @@ Page Specifications are detailed documentation for each page/screen in your prod - Strategic rationale for design decisions - Interactive prototypes (optional) -**Created by:** Freyja the WDS UX Designer Agent +**Created by:** Freyja the UX Designer **When:** Phase 5 - After Platform PRD (or in parallel) **Format:** Markdown specifications + sketches/prototypes --- +## Why This Matters + +**Without Detailed Specifications:** +- ❌ Developers guess at your intent +- ❌ Content gets "lorem ipsum" treatment +- ❌ Design decisions lost in handoff +- ❌ Endless "what did you mean?" meetings + +**With Page Specifications:** +- ✅ Preserves design intent from concept to code +- ✅ Developers understand the WHY, not just the WHAT +- ✅ Content is strategic, not placeholder +- ✅ Specifications become AI-ready super-prompts +- ✅ Reduces implementation errors and rework + +--- + ## What's Included ### For Each Page: @@ -50,12 +75,71 @@ Page Specifications are detailed documentation for each page/screen in your prod --- +## The Dialog with Your Design Partner: Freyja the UX Designer + +**The Process (iterative, per page):** + +Freyja the UX Designer helps you specify each page with precision: + +``` +Freyja the UX Designer: "I see you've uploaded a sketch. Let me analyze it... + This looks like a dashboard homepage. Is that right?" + +You: "Yes! It's the first thing users see after login." + +Freyja the UX Designer: "Perfect. What's the user's situation when they arrive here?" + +You: "They just logged in - they want to see their project status at a glance." + +Freyja the UX Designer: "Got it. I can see three sections in your sketch: + header navigation, project cards, and quick actions. + Let me identify the components..." + +You: "The project cards need to show status, deadline, and team members." + +Freyja the UX Designer: "Excellent detail! Let me document that with Object IDs..." +``` + +As you work together, Freyja the UX Designer creates: +- ✅ Complete navigation structure +- ✅ Page overview with context +- ✅ Section breakdown with Object IDs +- ✅ Content with language tags +- ✅ Component specifications +- ✅ Object Registry + +Then you review together: + +``` +Freyja the UX Designer: "Here's your page specification. Does this capture your vision?" + +You: "Add a filter dropdown to the quick actions section." + +Freyja the UX Designer: "Added COMP_FILTER_001 to quick actions. ✅ Spec is complete." +``` + +**Result:** Page specification saved to `/docs/4-scenarios/[page-name]/` + +--- + ## Example See the [WDS Presentation Project - Page Specification](../../examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md) --- +## Agent Activation + +To start creating Page Specifications: + +``` +@freyja I have a sketch for [Page Name] - let's create the specification. +``` + +Or simply upload a sketch image to any agent, and they'll recognize it and activate Freyja automatically. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 08: Initialize Scenario](../module-08-initialize-scenario/tutorial-08.md) @@ -68,23 +152,13 @@ See the [WDS Presentation Project - Page Specification](../../examples/WDS-Prese --- -## Why This Matters +## Getting Started with WDS -Without Detailed Specifications: -- Developers guess at your intent -- Content gets "lorem ipsum" treatment -- Design decisions lost in handoff -- Endless "what did you mean?" meetings +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With Page Specifications: -- Preserves design intent from concept to code -- Developers understand the WHY, not just the WHAT -- Content is strategic, not placeholder -- Specifications become AI-ready super-prompts -- Reduces implementation errors and rework +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Platform PRD & Architecture](platform-prd.md) **Next Deliverable:** [Component Library & Design Tokens](design-system.md) - diff --git a/src/modules/wds/course/deliverables/platform-prd.md b/src/modules/wds/course/deliverables/platform-prd.md index 4256d651..2540ec59 100644 --- a/src/modules/wds/course/deliverables/platform-prd.md +++ b/src/modules/wds/course/deliverables/platform-prd.md @@ -1,9 +1,17 @@ -# Deliverable 04: Platform PRD & Architecture +# Deliverable: Platform PRD & Architecture **Define the technical foundation - bridge design vision with technical reality** --- +## About WDS & the Platform PRD + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Platform PRD** ensures your design vision is technically feasible. Idunn the Technical Architect helps you define the technical foundation before UX design begins, preventing costly rework when beautiful designs meet harsh technical reality. + +--- + ## What Is This Deliverable? The Platform PRD (Product Requirements Document) defines the technical architecture and infrastructure decisions: @@ -13,12 +21,28 @@ The Platform PRD (Product Requirements Document) defines the technical architect - Security and performance requirements - Technical constraints and decisions -**Created by:** Idunn the WDS Technical Architect Agent +**Created by:** Idunn the Technical Architect **When:** Phase 4 - After Trigger Map, before UX design (or in parallel) **Format:** Structured PRD document + architecture diagrams --- +## Why This Matters + +**Without Platform Architecture:** +- ❌ Designers create UX that's technically impossible +- ❌ Developers make inconsistent tech decisions +- ❌ Costly rework when design meets reality +- ❌ Security and performance as afterthoughts + +**With Platform Architecture:** +- ✅ Realistic design constraints from day one +- ✅ Technical decisions documented and justified +- ✅ Developers aligned on approach +- ✅ Foundation for sustainable growth + +--- + ## What's Included ### 1. System Architecture @@ -58,12 +82,71 @@ The Platform PRD (Product Requirements Document) defines the technical architect --- +## The Dialog with Your Technical Partner: Idunn the Technical Architect + +**The Process (1-2 hours):** + +Idunn the Technical Architect helps you define technical boundaries: + +``` +Idunn the Technical Architect: "Let's establish the foundation. What platform + are you targeting?" + +You: "WordPress site with custom blocks for the design system." + +Idunn the Technical Architect: "Smart choice - familiar editing, structured output. + Any third-party integrations?" + +You: "Newsletter signup (Mailchimp), analytics (Google Analytics)." + +Idunn the Technical Architect: "Got it. What about user authentication?" + +You: "No login needed - it's a marketing site." + +Idunn the Technical Architect: "Perfect - that simplifies architecture significantly. + Let me document this..." +``` + +As you discuss, Idunn the Technical Architect creates: +- ✅ Technology stack decisions +- ✅ Data model (if needed) +- ✅ Integration requirements +- ✅ Performance targets +- ✅ Security considerations +- ✅ Technical constraints for design + +Then you review together: + +``` +Idunn the Technical Architect: "Here's your Platform PRD. Does this match your needs?" + +You: "Add mobile-first responsive requirement." + +Idunn the Technical Architect: "Added to technical requirements. ✅ PRD is ready." +``` + +**Result:** Platform PRD ready to guide UX design and development + +--- + ## Example *(Example coming soon)* --- +## Agent Activation + +To start creating your Platform PRD: + +``` +@idunn I need to create a Platform PRD for [Your Project Name]. +``` + +Idunn the Technical Architect will begin the conversation and guide you through the process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 06: Platform Architecture](../module-06-platform-architecture/tutorial-06.md) @@ -72,22 +155,13 @@ The Platform PRD (Product Requirements Document) defines the technical architect --- -## Why This Matters +## Getting Started with WDS -Without Platform Architecture: -- Designers create UX that's technically impossible -- Developers make inconsistent tech decisions -- Costly rework when design meets reality -- Security and performance as afterthoughts +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With Platform Architecture: -- Realistic design constraints from day one -- Technical decisions documented and justified -- Developers aligned on approach -- Foundation for sustainable growth +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Trigger Map & Personas](trigger-map.md) **Next Deliverable:** [Page Specifications & Prototypes](page-specifications.md) - diff --git a/src/modules/wds/course/deliverables/project-pitch.md b/src/modules/wds/course/deliverables/project-pitch.md index 41d37b7a..6a53849e 100644 --- a/src/modules/wds/course/deliverables/project-pitch.md +++ b/src/modules/wds/course/deliverables/project-pitch.md @@ -4,6 +4,14 @@ --- +## About WDS & the Project Pitch + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Project Pitch** is where it all begins. Before any design work starts, you need stakeholder buy-in. This deliverable helps you articulate your vision in business language that decision-makers understand, demonstrating clear ROI and strategic value. + +--- + ## What Is This Deliverable? The Project Pitch is your persuasive document that: @@ -12,12 +20,28 @@ The Project Pitch is your persuasive document that: - Shows you've thought through the approach - Convinces decision-makers to say "yes" -**Created by:** Saga the WDS Analyst Agent +**Created by:** Saga the Analyst **When:** Phase 1 (Module 03) - Before you have formal commitment **Format:** Markdown document, often converted to PDF/presentation --- +## Why This Matters + +**Without a compelling pitch:** +- ❌ Decision-makers don't understand the value +- ❌ Projects get stuck in "let me think about it" limbo +- ❌ You can't articulate ROI clearly +- ❌ Stakeholders dismiss it as "nice to have" + +**With a strong pitch:** +- ✅ Clear business case for investment +- ✅ Stakeholders excited about the vision +- ✅ Decision happens quickly (yes or no) +- ✅ Foundation for alignment on goals + +--- + ## What's Included - **Project Overview:** Clear statement of what you're building and why @@ -30,12 +54,69 @@ The Project Pitch is your persuasive document that: --- +## The Dialog with Your Thinking Partner: Saga the Analyst + +**The Process (30-45 minutes):** + +Saga the Analyst helps you craft a compelling pitch: + +``` +Saga the Analyst: "Let's build your pitch. What's the core problem you're solving?" + +You: "Our sales team wastes 10 hours a week on manual reporting." + +Saga the Analyst: "Excellent. So if we automate that, what's the ROI?" + +You: "10 hours × 5 reps × $50/hour × 52 weeks = $130K/year saved." + +Saga the Analyst: "Perfect! That's your business value. Now, what's the vision + beyond cost savings?" + +You: "Sales reps focus on selling, not spreadsheets. Happier team, + better results." + +Saga the Analyst: "Beautiful. Let me capture that..." +``` + +As you talk, Saga the Analyst creates: +- ✅ Clear problem statement +- ✅ Quantified business value +- ✅ Compelling vision +- ✅ Investment breakdown +- ✅ Success metrics + +Then you review together: + +``` +Saga the Analyst: "Here's your pitch. Does this sell the vision?" + +You: "Yes! But add that competitors are ahead of us on automation." + +Saga the Analyst: "Added to competitive context. ✅ Pitch is ready." +``` + +**Result:** Project Pitch saved and ready for stakeholder presentation + +--- + ## Example See the [WDS Presentation Project - Pitch](#) *(Coming soon)* --- +## Agent Activation + +To start creating your Project Pitch: + +``` +@saga I need to create a Project Pitch for [Your Project Name]. +``` + +Saga the Analyst will begin the conversation and guide you through the process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 03: Alignment & Signoff](../module-03-alignment-signoff/tutorial-03.md) @@ -44,21 +125,12 @@ See the [WDS Presentation Project - Pitch](#) *(Coming soon)* --- -## Why This Matters +## Getting Started with WDS -Without a compelling pitch: -- Decision-makers don't understand the value -- Projects get stuck in "let me think about it" limbo -- You can't articulate ROI clearly -- Stakeholders dismiss it as "nice to have" +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With a strong pitch: -- Clear business case for investment -- Stakeholders excited about the vision -- Decision happens quickly (yes or no) -- Foundation for alignment on goals +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Next Deliverable:** [Service Agreement](service-agreement.md) - Formalize the commitment (after pitch is accepted) - diff --git a/src/modules/wds/course/deliverables/service-agreement.md b/src/modules/wds/course/deliverables/service-agreement.md index 3e613a71..d919f4b2 100644 --- a/src/modules/wds/course/deliverables/service-agreement.md +++ b/src/modules/wds/course/deliverables/service-agreement.md @@ -4,6 +4,14 @@ --- +## About WDS & the Service Agreement + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Service Agreement** formalizes the commitment you secured with your Project Pitch. It protects both parties, defines clear scope, and establishes the foundation for a healthy working relationship. + +--- + ## What Is This Deliverable? The Service Agreement is your formal contract that: @@ -12,12 +20,29 @@ The Service Agreement is your formal contract that: - Protects both parties with terms and conditions - Provides legal foundation for the project -**Created by:** Saga the WDS Analyst Agent +**Created by:** Saga the Analyst **When:** Phase 1 (Module 03) - After pitch is accepted, before work begins **Format:** Markdown document converted to contract/PDF format --- +## Why This Matters + +**Without a formal agreement:** +- ❌ Scope creep becomes unmanageable +- ❌ Payment becomes contentious ("that's not what I meant") +- ❌ No protection if client stops paying +- ❌ Unclear who owns the final work + +**With a service agreement:** +- ✅ Protected scope and budget +- ✅ Clear payment terms +- ✅ Legal recourse if needed +- ✅ Professional credibility +- ✅ Foundation for healthy client relationships + +--- + ## What's Included - **Scope of Work:** What's included (and what's explicitly not) @@ -32,12 +57,71 @@ The Service Agreement is your formal contract that: --- +## The Dialog with Your Thinking Partner: Saga the Analyst + +**The Process (30-45 minutes):** + +Saga the Analyst helps you formalize the agreement: + +``` +Saga the Analyst: "Let's protect this project with a solid agreement. + What exactly is in scope?" + +You: "Landing page redesign, mobile responsive, 5 pages total." + +Saga the Analyst: "Good. What's explicitly OUT of scope?" + +You: "No backend work, no e-commerce, no third-party integrations." + +Saga the Analyst: "Perfect - that clarity prevents scope creep. + Now, what are your deliverables?" + +You: "Page specifications, design system, WordPress-ready content, + interactive prototype." + +Saga the Analyst: "Great! What's your timeline and payment structure?" +``` + +As you talk, Saga the Analyst creates: +- ✅ Clear scope boundaries +- ✅ Specific deliverables list +- ✅ Milestone timeline +- ✅ Payment terms +- ✅ Change order process +- ✅ IP ownership terms + +Then you review together: + +``` +Saga the Analyst: "Here's your Service Agreement. Does this protect you?" + +You: "Add a 50% deposit requirement before work starts." + +Saga the Analyst: "Added to payment terms. ✅ Agreement is ready." +``` + +**Result:** Service Agreement ready for client signature + +--- + ## Example See the [WDS Presentation Project - Service Agreement](#) *(Coming soon)* --- +## Agent Activation + +To start creating your Service Agreement: + +``` +@saga I need to create a Service Agreement for [Your Project Name]. +``` + +Saga the Analyst will begin the conversation and guide you through the process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 03: Alignment & Signoff](../module-03-alignment-signoff/tutorial-03.md) @@ -46,23 +130,13 @@ See the [WDS Presentation Project - Service Agreement](#) *(Coming soon)* --- -## Why This Matters +## Getting Started with WDS -Without a formal agreement: -- Scope creep becomes unmanageable -- Payment becomes contentious ("that's not what I meant") -- No protection if client stops paying -- Unclear who owns the final work +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With a service agreement: -- Protected scope and budget -- Clear payment terms -- Legal recourse if needed -- Professional credibility -- Foundation for healthy client relationships +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Project Pitch](project-pitch.md) - Get stakeholder buy-in first **Next Deliverable:** [Product Brief](product-brief.md) - Define what you're actually building - diff --git a/src/modules/wds/course/deliverables/trigger-map.md b/src/modules/wds/course/deliverables/trigger-map.md index b7cce295..4a9e058c 100644 --- a/src/modules/wds/course/deliverables/trigger-map.md +++ b/src/modules/wds/course/deliverables/trigger-map.md @@ -1,9 +1,17 @@ -# Deliverable 03: Trigger Map & Personas +# Deliverable: Trigger Map & Personas **Connect business goals to user psychology - design with insight, not guesswork** --- +## About WDS & the Trigger Map + +**WDS (Whiteport Design Studio)** is an AI agent framework module within the BMAD Method that transforms how designers work. Instead of creating documentation that gets lost in translation, your design work becomes **powerful prompts** that guide AI agents and development teams with precision and intent. + +**The Trigger Map** bridges strategy and design. It connects what your business wants to achieve with what motivates (and frustrates) your users. This becomes the psychological foundation for every design decision you make. + +--- + ## What Is This Deliverable? The Trigger Map is a strategic framework that connects: @@ -12,12 +20,28 @@ The Trigger Map is a strategic framework that connects: - **Personas:** Detailed profiles of key user groups - **Feature Priorities:** Which features move the needle on both -**Created by:** Cascade the WDS Strategist Agent +**Created by:** Cascade the Strategist **When:** Phase 3 - After Product Brief, before design begins **Format:** Visual map + detailed persona documents --- +## Why This Matters + +**Without Trigger Mapping:** +- ❌ You guess at user needs based on assumptions +- ❌ Features get prioritized by "coolness" not impact +- ❌ Design feels generic and disconnected +- ❌ No psychological foundation for UX decisions + +**With Trigger Mapping:** +- ✅ Design decisions grounded in user psychology +- ✅ Clear feature prioritization based on impact +- ✅ Personas with depth (not demographic stereotypes) +- ✅ Connection between what users need and what business wants + +--- + ## What's Included ### 1. Business Goals @@ -51,12 +75,71 @@ Detailed profiles for each key user group: --- +## The Dialog with Your Strategy Partner: Cascade the Strategist + +**The Process (2-3 hours across multiple sessions):** + +Cascade the Strategist guides you through mapping the psychology: + +``` +Cascade the Strategist: "Let's map the driving forces. Who's your primary user?" + +You: "Freelance designers managing client projects." + +Cascade the Strategist: "Perfect. What keeps them up at night? What are they afraid of?" + +You: "Missing deadlines, looking unprofessional, losing clients because + of poor communication." + +Cascade the Strategist: "Strong negative forces. Now, what do they aspire to?" + +You: "Being seen as organized and reliable. Growing their business. + Working with better clients." + +Cascade the Strategist: "Excellent! Now, which features address those fears + AND enable those aspirations?" +``` + +As you work together, Cascade the Strategist creates: +- ✅ Business goal hierarchy +- ✅ Detailed personas with psychology +- ✅ Positive/negative driving forces +- ✅ Feature impact matrix +- ✅ Strategic insights + +Then you review together: + +``` +Cascade the Strategist: "Here's your Trigger Map. Does this capture the psychology?" + +You: "Yes! But automated reminders should be higher priority - + it hits fear of missing deadlines." + +Cascade the Strategist: "Updated! ✅ Trigger Map is complete." +``` + +**Result:** Trigger Map saved to `/docs/2-trigger-map/` + +--- + ## Example See the [WDS Presentation Project - Trigger Map](../../examples/WDS-Presentation/docs/2-trigger-map/) --- +## Agent Activation + +To start creating your Trigger Map: + +``` +@cascade I need to create a Trigger Map for [Your Project Name]. +``` + +Cascade the Strategist will begin the conversation and guide you through the process. + +--- + ## How to Create This **Hands-on Tutorial:** [Module 04: Trigger Mapping](../module-04-map-triggers-outcomes/tutorial-04.md) @@ -65,22 +148,13 @@ See the [WDS Presentation Project - Trigger Map](../../examples/WDS-Presentation --- -## Why This Matters +## Getting Started with WDS -Without Trigger Mapping: -- You guess at user needs based on assumptions -- Features get prioritized by "coolness" not impact -- Design feels generic and disconnected -- No psychological foundation for UX decisions +New to WDS? Install the complete AI agent framework to unlock all capabilities: -With Trigger Mapping: -- Design decisions grounded in user psychology -- Clear feature prioritization based on impact -- Personas with depth (not demographic stereotypes) -- Connection between what users need and what business wants +👉 **[Install WDS & Get Started](../../getting-started/getting-started-overview.md)** --- **Previous Deliverable:** [Product Brief](product-brief.md) **Next Deliverable:** [Platform PRD & Architecture](platform-prd.md) - diff --git a/src/modules/wds/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md b/src/modules/wds/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md index 38ba7da3..a89d6f42 100644 --- a/src/modules/wds/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md +++ b/src/modules/wds/examples/WDS-Presentation/docs/4-scenarios/1.1-wds-presentation/1.1-wds-presentation.md @@ -104,8 +104,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Win Client Buy-In" - **Description (EN):** "Present your vision in business language that stakeholders understand. Get everyone aligned on goals, budget, and commitment before you start. Stop projects from dying in "maybe" meetings. Saga helps you articulate value and create professional agreements." - - **Output (EN):** "→ Pitch & Service Agreement" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/project-pitch.md` + - **Output (EN):** "→ [Project Pitch](../../../course/deliverables/project-pitch.md) & [Service Agreement](../../../course/deliverables/service-agreement.md)" #### Phase 2: Define Your Project **OBJECT ID**: `wds-capability-phase-2` @@ -114,8 +113,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Define Your Project" - **Description (EN):** "Get crystal clear on what you're building, who it's for, and why it matters. Create a strategic foundation that guides every design decision. No more scope creep or confused teams. This brief becomes your north star when things get messy." - - **Output (EN):** "→ Product Brief" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/product-brief.md` + - **Output (EN):** "→ [Product Brief](../../../course/deliverables/product-brief.md)" #### Phase 3: Map Business Goals to User Needs **OBJECT ID**: `wds-capability-phase-3` @@ -124,8 +122,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Map Business Goals to User Needs" - **Description (EN):** "Connect what the business wants to what users actually need. Identify the emotional triggers and pain points that make your design work. Stop guessing and start designing with psychological insight. Cascade helps you create personas grounded in real driving forces." - - **Output (EN):** "→ Trigger Map & Personas" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/trigger-map.md` + - **Output (EN):** "→ [Trigger Map & Personas](../../../course/deliverables/trigger-map.md)" #### Phase 4: Architect the Platform **OBJECT ID**: `wds-capability-phase-4` @@ -134,8 +131,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Architect the Platform" - **Description (EN):** "Define the technical foundation, data structure, and system architecture. Make smart decisions about what to build and how it fits together. Bridge the gap between design vision and technical reality. Idunn helps you think through the platform without getting lost in code." - - **Output (EN):** "→ Platform PRD & Architecture" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/platform-prd.md` + - **Output (EN):** "→ [Platform PRD & Architecture](../../../course/deliverables/platform-prd.md)" #### Phase 5: Design the Experience **OBJECT ID**: `wds-capability-phase-5` @@ -144,8 +140,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Design the Experience" - **Description (EN):** "Turn sketches into complete specifications with interactive prototypes. Capture not just WHAT it looks like, but WHY you designed it that way. Preserve your design intent from concept to code. Freyja helps you create specifications that developers actually understand and respect." - - **Output (EN):** "→ Page Specs & Prototypes" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/page-specifications.md` + - **Output (EN):** "→ [Page Specifications & Prototypes](../../../course/deliverables/page-specifications.md)" #### Phase 6: Build Your Design System **OBJECT ID**: `wds-capability-phase-6` @@ -154,8 +149,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Build Your Design System" - **Description (EN):** "Extract reusable components, patterns, and design tokens from your pages. Create consistency across your entire product without starting from scratch every time. Scale your design decisions efficiently. Stop reinventing buttons and start building systems." - - **Output (EN):** "→ Component Library & Tokens" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/design-system.md` + - **Output (EN):** "→ [Component Library & Design Tokens](../../../course/deliverables/design-system.md)" #### Phase 7: Hand Off to Developers **OBJECT ID**: `wds-capability-phase-7` @@ -164,8 +158,7 @@ The WDS Presentation page serves as the primary entry point for designers discov - **Content:** - **Title (EN):** "Hand Off to Developers" - **Description (EN):** "Package everything developers need in organized PRD documents with epics and stories. No more "what did you mean by this?" meetings. No more guesswork or lost design intent. Idunn creates implementation guides that turn your specs into buildable tasks." - - **Output (EN):** "→ Design Delivery PRD" -- **Link**: `https://github.com/whiteport/wds/tree/main/src/modules/wds/course/deliverables/design-delivery-prd.md` + - **Output (EN):** "→ [Design Delivery PRD](../../../course/deliverables/design-delivery-prd.md)" ---