whiteport-design-studio 0.1.0

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/09-explore-how-we-see-it-working.md

@@ -0,0 +1,29 @@
+# Substep 09: Explore How We See It Working
+
+**Purpose**: Help user articulate how they envision the solution working
+
+---
+
+## Instruction
+
+Explore how they see it working.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 3: How We See It Working)
+
+**Questions to explore**:
+- "How do you envision this working?"
+- "What's the general approach?"
+- "Walk me through how you see it addressing the realization"
+- "What's the core concept?"
+
+**Keep it brief** - High-level overview, not detailed specifications
+
+**Flexible language** - Works for software, processes, services, products, strategies
+
+---
+
+## Next Step
+
+After exploring how it works:
+→ `10-explore-paths-we-explored.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/10-explore-paths-we-explored.md

@@ -0,0 +1,28 @@
+# Substep 10: Explore Paths We Explored
+
+**Purpose**: Help user articulate alternative approaches they considered
+
+---
+
+## Instruction
+
+Explore paths they explored.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 4: Paths We Explored)
+
+**Questions to explore**:
+- "What other ways could we approach this?"
+- "Are there alternative paths?"
+- "What options have you considered?"
+
+**Keep it brief** - 2-3 paths explored briefly
+
+**If user only has one path**: That's fine - acknowledge it and move on
+
+---
+
+## Next Step
+
+After exploring paths:
+→ `11-explore-recommended-solution.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/11-explore-recommended-solution.md

@@ -0,0 +1,26 @@
+# Substep 11: Explore Recommended Solution
+
+**Purpose**: Help user articulate their preferred approach and why
+
+---
+
+## Instruction
+
+Explore the recommended solution.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 5: Recommended Solution)
+
+**Questions to explore**:
+- "Which approach do you prefer?"
+- "Why this one over the others?"
+- "What makes this the right solution?"
+
+**Keep it brief** - Preferred approach and key reasons
+
+---
+
+## Next Step
+
+After exploring recommended solution:
+→ `12-explore-path-forward.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/12-explore-path-forward.md

@@ -0,0 +1,38 @@
+# Substep 12: Explore The Path Forward
+
+**Purpose**: Help user articulate how the work will be done
+
+---
+
+## Instruction
+
+Explore the path forward.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 6: The Path Forward)
+
+**Purpose**: Explain how the work will be done practically - which WDS phases will be used and the workflow approach.
+
+**Questions to explore**:
+- "How do you envision the work being done?"
+- "Which WDS phases do you think we'll need?"
+- "What's the practical workflow you're thinking?"
+- "Will we need user research, or do you already know your users?"
+- "Do you need technical architecture planning, or is that already defined?"
+- "What level of design detail do you need?"
+- "How will this be handed off for implementation?"
+
+**Keep it brief** - High-level plan of the work approach
+
+**Help them think**: 
+- Which WDS phases apply (Trigger Mapping, Platform Requirements, UX Design, Design System, etc.)
+- Practical workflow (research → design → handoff, or skip research, etc.)
+- Level of detail needed
+- Handoff approach
+
+---
+
+## Next Step
+
+After exploring path forward:
+→ `13-explore-value-we-create.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/13-explore-value-we-create.md

@@ -0,0 +1,40 @@
+# Substep 13: Explore The Value We'll Create
+
+**Purpose**: Help user articulate what happens if we DO build this
+
+---
+
+## Instruction
+
+Explore the value we'll create.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 7: The Value We'll Create)
+
+**Questions to explore**:
+- "What's our ambition? What are we striving to accomplish?"
+- "What happens if we DO build this?"
+- "What benefits would we see?"
+- "What outcomes are we expecting?"
+- "How will we measure success?"
+- "What metrics will tell us we're succeeding?"
+- "What's the value we'd create?"
+
+**Best Practice: Frame as Positive Assumption with Success Metrics**
+
+**Help them articulate**:
+- **Our Ambition**: What we're confidently striving to accomplish (enthusiastic, positive)
+- **Success Metrics**: How we'll measure success (specific, measurable)
+- **What Success Looks Like**: Clear outcomes (tangible results)
+- **Monitoring Approach**: How we'll track these metrics (brief)
+
+**Keep it brief** - Key benefits, outcomes, and success metrics
+
+**Help them think**: Positive assumption ("We're confident this will work") + clear success metrics ("Here's how we'll measure it") = enthusiastic and scientific
+
+---
+
+## Next Step
+
+After exploring value we'll create:
+→ `14-explore-cost-of-inaction.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/14-explore-cost-of-inaction.md

@@ -0,0 +1,37 @@
+# Substep 14: Explore Cost of Inaction
+
+**Purpose**: Help user articulate what happens if we DON'T build this
+
+---
+
+## Instruction
+
+Explore cost of inaction.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 8: Cost of Inaction)
+
+**Questions to explore**:
+- "What happens if we DON'T build this?"
+- "What are the risks of not acting?"
+- "What opportunities would we miss?"
+- "What's the cost of doing nothing?"
+- "What gets worse if we don't act?"
+- "What do we lose by waiting?"
+
+**Keep it brief** - Key consequences of not building
+
+**Can include**: 
+- Financial cost (lost revenue, increased costs)
+- Opportunity cost (missed opportunities)
+- Competitive risk (competitors gaining advantage)
+- Operational impact (inefficiency, problems getting worse)
+
+**Help them think**: Make the case for why we can't afford NOT to do this
+
+---
+
+## Next Step
+
+After exploring cost of inaction:
+→ `15-explore-our-commitment.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/15-explore-our-commitment.md

@@ -0,0 +1,33 @@
+# Substep 15: Explore Our Commitment
+
+**Purpose**: Help user articulate resources needed and potential risks
+
+---
+
+## Instruction
+
+Explore our commitment.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 9: Our Commitment)
+
+**Questions to explore**:
+- "What resources are we committing?"
+- "What's the time commitment?"
+- "What budget or team are we committing?"
+- "What dependencies exist?"
+- "What potential risks or drawbacks should we consider?"
+- "What challenges might we face?"
+
+**Keep it brief** - High-level commitment and potential risks
+
+**Don't force precision** - Rough estimates are fine at this stage
+
+**Help them think**: Time, money, people, technology - what are we committing to make this happen? What risks or challenges should we acknowledge?
+
+---
+
+## Next Step
+
+After exploring our commitment:
+→ `16-explore-summary.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/02-explore-sections/16-explore-summary.md

@@ -0,0 +1,26 @@
+# Substep 16: Explore Summary
+
+**Purpose**: Help user create a summary of key points
+
+---
+
+## Instruction
+
+Explore the summary.
+
+**Reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/section-guide.md` (Section 10: Summary)
+
+**Questions to explore**:
+- "What are the key points?"
+- "What should stakeholders remember?"
+- "What's the main takeaway?"
+
+**Keep it brief** - Summary of key points (let readers draw their own conclusion)
+
+---
+
+## Next Step
+
+After exploring all sections:
+→ `../03-synthesize-present/17-reflect-back.md`
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/03-synthesize-present/17-reflect-back.md

@@ -0,0 +1,33 @@
+# Substep 17: Reflect Back What You've Captured
+
+**Purpose**: Reflect back understanding before synthesizing
+
+---
+
+## Instruction
+
+**After covering all sections** (in whatever order made sense):
+
+Reflect back what you've captured:
+
+"I've explored [list sections covered] with you. Let me reflect back what I understand:
+
+- **The Realization**: [summarize their realization]
+- **Why It Matters**: [summarize why it matters and who we help]
+- **How We See It Working**: [summarize solution approach]
+- **Recommended Solution**: [summarize preferred approach]
+- **The Path Forward**: [summarize work approach]
+- **The Value We'll Create**: [summarize value and success metrics]
+- **Cost of Inaction**: [summarize consequences]
+- **Our Commitment**: [summarize resources and risks]
+- **Summary**: [summarize key points]
+
+Does this capture what you want in your alignment document? Anything you'd like to adjust or clarify?"
+
+---
+
+## Next Step
+
+After reflecting back and confirming:
+→ `18-synthesize-document.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/03-synthesize-present/18-synthesize-document.md

@@ -0,0 +1,41 @@
+# Substep 18: Synthesize Alignment Document
+
+**Purpose**: Create the alignment document from all explored sections
+
+---
+
+## Instruction
+
+**After confirming understanding**:
+
+Help crystallize into a clear, compelling narrative using framework thinking:
+- **Realization → Why It Matters → How We See It Working → Value We'll Create**
+- **Realization → Agitate (Cost of Inaction) → Solve (Solution) → Commitment**
+
+**Framework check**: Does the alignment document flow logically?
+- Realization is clear and evidence-backed
+- Why it matters and who we help is understood
+- Solution addresses the realization
+- Commitment is reasonable and risks acknowledged
+- Cost of inaction makes the case
+- Value we'll create justifies the commitment
+
+**Create Alignment Document**
+
+**Output file**: `docs/1-project-brief/pitch.md` (deliverable name: "pitch")
+
+**Format**: Clear, brief, readable in 2-3 minutes
+
+**Structure**: Use the 10-section structure covered in the exploration
+
+**Template reference**: `src/modules/wds/workflows/1-project-brief/alignment-signoff/pitch.template.md`
+
+**Ask**: "Does this present your idea in the best light?"
+
+---
+
+## Next Step
+
+After creating the alignment document:
+→ `18.5-create-vtc.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/03-synthesize-present/18.5-create-vtc.md

@@ -0,0 +1,76 @@
+# Substep 18.5: Create Value Trigger Chain
+
+**Purpose**: Create a simplified VTC to strengthen the pitch with strategic clarity
+
+---
+
+## Instruction
+
+**After creating the alignment document**:
+
+"Before we present this for approval, let's create a Value Trigger Chain (VTC) to add strategic clarity to your pitch.
+
+A VTC is a simplified strategic summary that captures:
+- **Business Goal** - What measurable outcome you want
+- **Solution** - What you're building
+- **User** - Who the primary user is
+- **Driving Forces** - What motivates them (positive + negative)
+- **Customer Awareness** - Where they start and where you move them
+
+This takes about 20-30 minutes and gives stakeholders a clear, strategic view of the project. It will be added to your pitch document.
+
+Shall we create the VTC now?"
+
+---
+
+## If User Agrees
+
+Load and execute the VTC Workshop Router:
+`../../../shared/vtc-workshop/vtc-workshop-router.md`
+
+**Note:** At pitch stage, there's typically NO Trigger Map yet, so router will likely send you to the **Creation Workshop**.
+
+### Leverage Pitch Context
+
+**Important:** You have extensive context from the pitch sections! Use it:
+
+- **Business Goal:** From "Value We'll Create" and "Why It Matters"
+- **Solution:** From "Recommended Solution"
+- **User:** From "Why It Matters" (who we help)
+- **Driving Forces:** Infer from "Why It Matters" and "Cost of Inaction"
+- **Customer Awareness:** Infer from "The Realization" and solution approach
+
+**Don't start from zero** - use the strategic work already completed.
+
+### Save VTC
+
+VTC should be saved to:
+`docs/1-project-brief/vtc-primary.yaml`
+
+### Add VTC to Pitch
+
+After VTC is created, add it to the pitch document using the template placeholders.
+
+---
+
+## If User Declines
+
+**If user says:** "Let's skip the VTC for now"
+
+**Response:**
+> "No problem! You can create a VTC later using:
+> `src/modules/wds/workflows/shared/vtc-workshop/vtc-workshop-router.md`
+> 
+> However, I recommend creating it before presenting to stakeholders. It takes 30 minutes and provides powerful strategic clarity that helps secure buy-in.
+> 
+> You can also add it after stakeholder feedback if needed."
+
+Then proceed to next step.
+
+---
+
+## Next Step
+
+After VTC is created (or declined):
+→ `19-present-for-approval.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/03-synthesize-present/19-present-for-approval.md

@@ -0,0 +1,44 @@
+# Substep 19: Present Alignment Document for Approval
+
+**Purpose**: Present the alignment document and guide next steps
+
+---
+
+## Instruction
+
+**Present the alignment document for review and approval**:
+
+"I've created your alignment document at `docs/1-project-brief/pitch.md`. 
+
+This alignment document is ready to share with your stakeholders. It's designed to be clear, brief, and compelling - readable in just 2-3 minutes.
+
+**Next steps**:
+1. Share the alignment document with stakeholders for review
+2. Gather their feedback - we can negotiate and make changes
+3. Update the alignment document until everyone is on board
+4. Once the alignment document is accepted and everyone is aligned on the idea, why, what, how, budget, and commitment
+5. **After acceptance**, I'll generate the signoff document (contract/service agreement/signoff) to secure the commitment
+6. Then we'll proceed to create the full Project Brief
+
+**Remember**: The alignment phase is collaborative - we can negotiate and iterate until everyone is on the same page. The signoff document comes after acceptance to formalize the commitment. WDS has your back - we'll help you get alignment and secure commitment before starting the work!
+
+Would you like to:
+- Review the alignment document together and make any adjustments before sharing?
+- Proceed to share it with stakeholders for feedback?
+- Make changes based on stakeholder feedback?
+- Or something else?"
+
+---
+
+## Decision Point
+
+**If user wants to make changes**:
+- Update the alignment document
+- Return to this step after changes
+
+**If alignment document is accepted**:
+→ `../04-generate-signoff/20-offer-signoff-document.md`
+
+**If user wants to skip signoff**:
+→ Proceed to Project Brief workflow
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/04-generate-signoff/20-offer-signoff-document.md

@@ -0,0 +1,38 @@
+# Substep 20: Offer to Generate Signoff Document
+
+**Purpose**: Offer to create signoff document after alignment acceptance
+
+---
+
+## Instruction
+
+**After the alignment document is accepted by stakeholders**, offer to create a signoff document:
+
+"Great! The alignment document has been accepted and everyone is aligned on the idea, why, what, how, budget, and commitment. 
+
+Now let's secure this commitment with a signoff document. This will formalize what everyone has agreed to and ensure everyone stays committed to making this project happen.
+
+**What type of document do you need?**
+
+1. **Project Contract** - If you're a consultant and the client has approved the alignment document
+2. **Service Agreement** - If you're a founder/owner and suppliers have approved the alignment document
+3. **Project Signoff Document** - If this is an internal company project and stakeholders have approved
+   - *Note: If you have an existing company signoff document format, you can upload it and I'll adapt it to match your company's format*
+4. **Skip** - If you don't need a formal document right now
+
+Which applies to your situation?
+
+**Remember**: WDS helps with alignment - the alignment document got everyone on the same page, and this signoff document secures the commitment before we start building something that makes the world a better place!"
+
+---
+
+## Decision Point
+
+**If user chooses "Skip"**:
+- Acknowledge: "No problem! The alignment document is ready to share. You can always generate a signoff document later if needed."
+- Proceed to Project Brief workflow
+
+**If user chooses document type**:
+→ `21-determine-business-model.md` (same folder - for external contracts)
+→ `../06-build-signoff-internal/34-build-internal-signoff.md` (for internal signoff)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/04-generate-signoff/21-determine-business-model.md

@@ -0,0 +1,50 @@
+# Substep 21: Determine Business Model
+
+**Purpose**: Determine how the service will be paid for (for external contracts)
+
+---
+
+## Instruction
+
+**Before building contract sections**, determine the business model:
+
+"First, let's determine the business model - how will this service be paid for? This helps us structure the contract correctly.
+
+**What business model fits this project?**
+
+1. **Fixed-Price Project** - Set price for a defined scope of work
+   - Best for: Projects with clear deliverables and scope
+   - Includes: Not-to-exceed clause, upfront payment recommended
+   - Example: "$50,000 for complete website redesign with 5 pages"
+
+2. **Hourly/Time-Based** - Pay for actual time worked
+   - Best for: Ongoing work, uncertain scope, flexible requirements
+   - Includes: Hourly rate, time tracking, optional not-to-exceed cap
+   - Example: "$150/hour, estimated 200 hours"
+
+3. **Retainer** - Monthly commitment with minimum hours
+   - Best for: Ongoing support, regular availability needed
+   - Includes: Monthly retainer amount, minimum hours, availability expectations, hourly rate for overage
+   - Example: "$5,000/month retainer for 20 hours minimum, $200/hour for additional hours"
+
+4. **Hybrid** - Combination of models (e.g., retainer + project work)
+   - Best for: Complex arrangements with multiple work types
+   - Includes: Multiple payment structures combined
+
+Which model fits your situation?"
+
+---
+
+## After User Selects Business Model
+
+**Confirm understanding**: "So you've chosen [model]. This means [brief explanation of what this means for the contract]."
+
+**Note the selection**: This will determine which sections we include and how we configure payment terms, not-to-exceed, availability, etc.
+
+---
+
+## Next Step
+
+After determining business model:
+→ `../05-build-contract/22-build-section-01-project-overview.md`
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/05-build-contract/22-build-section-01-project-overview.md

@@ -0,0 +1,29 @@
+# Substep 22: Build Section 1 - Project Overview
+
+**Purpose**: Build the Project Overview section of the contract
+
+---
+
+## Instruction
+
+**Section 1: Project Overview**
+
+**Background**: Establishes what the project is about
+
+**What it does**: Defines the realization and solution from the alignment document
+
+**Purpose**: Sets clear expectations and context
+
+**Content**: Pull from alignment document (pitch):
+- **The Realization**: {{realization}}
+- **Recommended Solution**: {{recommended_solution}}
+
+**Explain to user**: "This section establishes what the project is about. I'll pull the realization and recommended solution from your alignment document."
+
+---
+
+## Next Step
+
+After building Project Overview:
+→ `23-build-section-02-business-model.md` (same folder)
+

package/src/workflows/1-project-brief/alignment-signoff/substeps/05-build-contract/23-build-section-02-business-model.md

@@ -0,0 +1,66 @@
+# Substep 23: Build Section 2 - Business Model
+
+**Purpose**: Build the Business Model section based on user's selection
+
+---
+
+## Instruction
+
+**Section 2: Business Model**
+
+**Background**: Defines how the service will be paid for - critical foundation for all payment terms
+
+**What it does**: Explains the selected business model and its terms
+
+**Purpose**: Sets clear expectations about payment structure, prevents misunderstandings
+
+**Content**: Based on user's selection from micro-21
+
+**For each business model, include**:
+
+**If Fixed-Price Project**:
+- Model name: "Fixed-Price Project"
+- Description: "This contract uses a fixed-price model. The contractor commits to deliver the specified scope of work for the agreed price, regardless of actual time or costs incurred."
+- Key terms:
+  - Total project price: {{total_amount}}
+  - Price includes: All work within the defined scope
+  - Price does NOT include: Work outside the original scope (requires change order)
+  - Payment structure: {{payment_structure}} (e.g., 50% upfront, 50% on completion)
+  - Not-to-exceed: Applies (see Section 10)
+
+**If Hourly/Time-Based**:
+- Model name: "Hourly/Time-Based"
+- Description: "This contract uses an hourly billing model. The client pays for actual time worked at the agreed hourly rate."
+- Key terms:
+  - Hourly rate: {{hourly_rate}}
+  - Estimated hours: {{estimated_hours}} (if applicable)
+  - Estimated total: {{estimated_total}} (hourly_rate × estimated_hours)
+  - Time tracking: {{time_tracking_method}} (e.g., detailed timesheets, time tracking software)
+  - Billing frequency: {{billing_frequency}} (e.g., weekly, bi-weekly, monthly)
+  - Not-to-exceed: {{not_to_exceed_applies}} (optional cap - see Section 10 if applicable)
+
+**If Retainer**:
+- Model name: "Monthly Retainer"
+- Description: "This contract uses a retainer model. The client pays a fixed monthly amount for a minimum number of hours, with additional hours billed at the overage rate."
+- Key terms:
+  - Monthly retainer amount: {{monthly_retainer_amount}}
+  - Minimum hours per month: {{minimum_hours_per_month}}
+  - Effective hourly rate: {{effective_hourly_rate}} (retainer ÷ minimum hours)
+  - Overage hourly rate: {{overage_hourly_rate}} (for hours beyond minimum)
+  - Availability: {{availability_expectations}} (e.g., "Available during business hours, 2-3 day response time")
+  - Retainer period: {{retainer_period}} (e.g., "Monthly, renewable")
+  - Hour rollover: {{hour_rollover_policy}} (e.g., "Unused hours expire at month end" or "Up to X hours can roll over")
+  - Billing: Retainer due {{retainer_due_date}} (e.g., "on the 1st of each month")
+
+**If Hybrid**:
+- Model name: "Hybrid Model"
+- Description: "This contract combines multiple payment structures."
+- Key terms: Combine terms from each component
+
+---
+
+## Next Step
+
+After building Business Model section:
+→ `24-build-section-03-scope-of-work.md` (same folder)
+