whiteport-design-studio 0.1.0

package/src/workflows/1-project-brief/alignment-signoff/service-agreement.template.md

@@ -0,0 +1,277 @@
+# Service Agreement
+
+**Project**: {{project_name}}  
+**Date**: {{date}}  
+**Client/Owner**: {{client_name}}  
+**Service Provider**: {{service_provider_name}}  
+**Contract Language**: {{contract_language}}  
+**Governing Law/Jurisdiction**: {{governing_jurisdiction}}
+
+---
+
+> **Agreement Philosophy**: This agreement is designed to be simple, fair, and clear - providing reliable terms that support a long-lasting working relationship between both parties.
+
+---
+
+## 1. Project Overview
+
+### The Realization
+
+{{realization}}
+
+### Recommended Solution
+
+{{recommended_solution}}
+
+---
+
+## 2. Scope of Services
+
+### The Path Forward
+
+{{path_forward}}
+
+### Deliverables
+
+Based on the path forward, the following deliverables will be provided:
+
+{{deliverables_list}}
+
+---
+
+## 3. Our Commitment
+
+{{our_commitment}}
+
+---
+
+### Payment Terms
+
+**Total Agreement Amount**: {{total_amount}}
+
+**Payment Structure**: {{payment_structure}}
+
+**Payment Schedule**:
+{{payment_schedule}}
+
+**Background**: Clear payment terms protect both parties and ensure fair compensation.
+
+**What it does**: Defines when and how payments will be made.
+
+**Purpose**: 
+- Ensures service provider receives fair compensation for work
+- Provides client with clear payment expectations
+- Protects both parties from payment disputes
+- For fixed-price agreements, upfront payment is fair since service provider assumes cost overrun risk
+
+**Payment Terms Details**:
+- **Payment Method**: {{payment_method}} (check, wire transfer, credit card, etc.)
+- **Payment Due Dates**: {{payment_due_dates}}
+- **Late Payment**: {{late_payment_terms}} (e.g., interest charges, work suspension)
+- **Payment Conditions**: {{payment_conditions}} (e.g., payment required before work begins, payment tied to deliverables)
+
+**For Fixed-Price Agreements**: 
+This is a fixed-price agreement, meaning the service provider commits to deliver specified work for the agreed price, regardless of actual costs. Since the service provider assumes the risk of cost overruns, upfront payment (50-100%) is standard and fair. This demonstrates client commitment and enables the service provider to deliver quality work without cash flow concerns.
+
+---
+
+## 4. Timeline
+
+{{timeline}}
+
+*Note: Timeline is based on the path forward outlined above and may be adjusted based on project requirements.*
+
+---
+
+## 5. Why It Matters
+
+{{why_it_matters}}
+
+---
+
+## 6. Expected Outcomes
+
+### The Value We'll Create
+
+{{value_we_create}}
+
+---
+
+## 7. Service Terms
+
+### Payment Terms
+
+{{payment_terms}}
+
+### Deliverable Acceptance
+
+Deliverables will be considered accepted upon:
+- Completion according to specifications
+- Review and approval by client
+- Any requested revisions completed
+
+### Intellectual Property
+
+All deliverables and work products will be owned by {{client_name}} upon full payment.
+
+---
+
+## 8. Risks and Considerations
+
+### Cost of Inaction
+
+{{cost_of_inaction}}
+
+---
+
+## 9. Confidentiality
+
+### Confidentiality Clause
+
+**Background**: This clause protects sensitive information shared during the project.
+
+**What it does**: Both parties agree to keep project information confidential.
+
+**Purpose**: Protects proprietary information, business strategies, trade secrets, and sensitive data.
+
+**Terms**:
+
+Both parties agree to:
+
+- Keep all project-related information confidential
+- Not disclose project details to third parties without written consent
+- Use confidential information solely for project purposes
+- Return or destroy confidential materials upon project completion or termination
+- Maintain confidentiality obligations even after project completion
+
+**Exceptions**:
+- Information already publicly known
+- Information independently developed
+- Information required by law to be disclosed
+
+**Duration**: Confidentiality obligations shall remain in effect for [X] years after project completion.
+
+---
+
+## 10. Not to Exceed Clause
+
+### Budget Cap
+
+**Background**: This clause sets a maximum budget limit.
+
+**What it does**: States that total costs will not exceed a specified amount without prior written approval.
+
+**Purpose**: 
+- Protects both parties from unexpected cost overruns
+- Ensures budget control
+- **Prevents scope creep** - Any work beyond the original scope requires approval and may affect the budget cap
+
+**Terms**:
+
+- Total project costs shall not exceed **{{not_to_exceed_amount}}** without prior written approval from {{client_name}}
+- Any work that would exceed this amount must be approved in advance
+- If additional work is needed, a change order must be signed before proceeding
+- This cap includes all fees, expenses, and costs related to the project
+
+**Change Orders and Scope Control**:
+- Any changes to scope that affect cost must be documented in a written change order
+- Change orders must be signed by both parties before work begins
+- Change orders may adjust the not-to-exceed amount if agreed upon
+- **Scope creep prevention**: Work outside the original scope (as defined in Section 2) requires a change order and approval before proceeding
+- This clause helps prevent gradual expansion of project scope without proper authorization
+
+---
+
+## 11. Terms and Conditions
+
+### Work Initiation
+
+**When work begins**: {{work_initiation_date_or_condition}}
+
+**Background**: This clause specifies exactly when the service provider is authorized to begin work.
+
+**What it does**: Defines the start date or conditions that must be met before work begins.
+
+**Purpose**: 
+- Prevents unauthorized work before agreement is fully executed
+- Establishes clear timeline expectations
+- Protects both parties by ensuring work only begins after proper authorization
+
+**Initiation conditions** (select applicable):
+- Upon full execution of this agreement (signatures from both parties)
+- On a specific date: {{specific_start_date}}
+- Upon receipt of initial payment/deposit
+- Upon written notice from {{client_name}}
+- Other: {{custom_initiation_condition}}
+
+### Project Initiation
+
+This project is initiated upon approval of the project pitch. Project initiation is considered complete upon stakeholder approval.
+
+### Changes and Modifications
+
+Any changes to scope, timeline, or investment must be agreed upon in writing by all parties.
+
+### Termination
+
+Either party may terminate this agreement with [X] days written notice. Upon termination, payment is due for work completed to date.
+
+### Dispute Resolution
+
+**Background**: Defines how conflicts will be resolved if they arise.
+
+**What it does**: Establishes the process for handling disagreements.
+
+**Purpose**: Provides a clear path for resolving disputes without costly litigation when possible.
+
+**Method**: {{dispute_resolution_method}} (mediation/arbitration/litigation)
+
+**Location**: {{dispute_resolution_location}}
+
+Any disputes arising from this agreement shall be resolved through {{dispute_resolution_method}} in {{dispute_resolution_location}}.
+
+---
+
+### Governing Law and Jurisdiction
+
+**Background**: Determines which laws apply and where legal proceedings would take place.
+
+**What it does**: Specifies the legal framework and court system that governs the agreement.
+
+**Purpose**: Provides legal clarity and predictability for both parties.
+
+**Governing Law**: This agreement shall be governed by and construed in accordance with the laws of {{governing_jurisdiction}}.
+
+**Jurisdiction**: Any legal proceedings arising from this agreement shall be subject to the exclusive jurisdiction of the courts of {{governing_jurisdiction}}.
+
+**Contract Language**: This agreement is executed in {{contract_language}}. In case of translation, the {{contract_language}} version shall prevail.
+
+---
+
+## 12. Approval
+
+**Client/Owner Approval**:
+
+Signature: _________________  
+Name: {{client_name}}  
+Date: _______________
+
+**Service Provider Approval**:
+
+Signature: _________________  
+Name: {{service_provider_name}}  
+Date: _______________
+
+---
+
+## Appendix
+
+### Reference Documents
+
+- Project Pitch: `docs/1-project-brief/pitch.md`
+- Project Brief: (To be created after agreement approval)
+
+---
+
+*This service agreement is based on the project pitch dated {{date}}.*
+

package/src/workflows/1-project-brief/alignment-signoff/signoff.template.md

@@ -0,0 +1,188 @@
+# Project Signoff Document
+
+**Project**: {{project_name}}  
+**Date**: {{date}}  
+**Department/Team**: {{department_name}}  
+**Project Owner**: {{project_owner}}  
+**Document Language**: {{contract_language}}  
+**Governing Jurisdiction**: {{governing_jurisdiction}} (if applicable)
+
+---
+
+> **Document Philosophy**: This signoff document is designed to be simple, fair, and clear - providing reliable terms that support successful project execution and clear accountability.
+
+---
+
+## 1. Project Overview
+
+### The Realization
+
+{{realization}}
+
+### Recommended Solution
+
+{{recommended_solution}}
+
+---
+
+## 2. Goals and Success Metrics
+
+### What We're Trying to Accomplish
+
+{{goals}}
+
+### Success Metrics
+
+{{success_metrics}}
+
+### How We'll Measure Success
+
+{{measurement_approach}}
+
+### Key Performance Indicators (KPIs)
+
+{{kpis}}
+
+---
+
+## 3. Budget and Resources
+
+### Budget Allocation
+
+**Total Budget**: {{total_budget}}
+
+**Budget Breakdown** (if applicable):
+{{budget_breakdown}}
+
+### Resources Needed
+
+{{resources_needed}}
+
+### Not-to-Exceed Budget Cap
+
+{{not_to_exceed_budget}}
+
+---
+
+## 4. Ownership and Responsibility
+
+### Project Owner
+
+{{project_owner}}
+
+### Process Owner
+
+{{process_owner}}
+
+### Key Stakeholders
+
+{{key_stakeholders}}
+
+### Decision-Making Authority
+
+{{decision_making_authority}}
+
+---
+
+## 5. Approval and Sign-Off
+
+### Who Needs to Approve
+
+{{approvers_list}}
+
+### Approval Stages
+
+{{approval_stages}}
+
+### Sign-Off Process
+
+{{signoff_process}}
+
+### Timeline for Approval
+
+{{approval_timeline}}
+
+---
+
+## 6. Timeline and Milestones
+
+### Key Milestones
+
+{{key_milestones}}
+
+### Delivery Dates
+
+{{delivery_dates}}
+
+### Critical Deadlines
+
+{{critical_deadlines}}
+
+---
+
+## 7. Optional Sections
+
+### Risks and Considerations (Optional)
+
+{{risks_and_considerations}}
+
+### Confidentiality (Optional)
+
+{{confidentiality_requirements}}
+
+### The Path Forward (Optional - High-Level Overview)
+
+{{path_forward_high_level}}
+
+---
+
+## 8. Approval and Signoff
+
+This document serves as formal approval to proceed with the project as outlined above.
+
+**Stakeholder Signoffs**:
+
+**Project Sponsor**:
+
+Name: _________________  
+Signature: _________________  
+Date: _______________
+
+**Budget Approver**:
+
+Name: _________________  
+Signature: _________________  
+Date: _______________
+
+**Project Owner**:
+
+Name: {{project_owner}}  
+Signature: _________________  
+Date: _______________
+
+---
+
+## 9. Next Steps
+
+Upon signoff:
+1. Proceed to full Project Brief development
+2. Execute work plan as outlined above
+3. Deliverables will be provided according to the agreed timeline
+
+### Changes and Modifications
+
+Any changes to scope, timeline, or investment must be agreed upon by all signatories.
+
+---
+
+## Appendix
+
+### Reference Documents
+
+- Project Pitch: `docs/1-project-brief/pitch.md`
+- Project Brief: (To be created after signoff)
+
+---
+
+*This signoff document is based on the project pitch dated {{date}}.*
+

package/src/workflows/1-project-brief/alignment-signoff/steps-c/step-01-start.md

@@ -0,0 +1,81 @@
+# Step 1: Start Alignment & Signoff
+
+## Purpose
+
+Begin creating an alignment document to get stakeholders aligned and secure commitment before starting the project.
+
+---
+
+## Context for Agent
+
+You are helping the user create an alignment document (pitch) that presents their idea in the best possible light. This is a **collaborative process** - you're working together to make their idea shine, not to criticize or challenge it.
+
+**Important**: Don't be surprised if their ideas grow and improve as you go through the process. That's natural and good!
+
+**Your Role**: You can handle the full experience - from understanding their situation to creating the alignment document and securing signoff. You're here to:
+- **Clarify their situation** - Are they a consultant? Manager? Founder? Doing it themselves?
+- **Help them understand** - Do they need alignment & signoff, or can they go straight to Project Brief?
+- **Guide through alignment & signoff** - Once we know they need alignment, help them create it efficiently
+
+**Your Style**: Professional, direct, and efficient. You're nice but you play no games - you're here to get things done. If they need emotional support, they can go to Mimir. You focus on clarity and results.
+
+**Purpose of alignment & signoff**: You're building something that makes the world a better place, and you need others involved. This alignment document helps you get alignment on:
+- **The Idea** - What are we building?
+- **Why** - Why should it be done?
+- **What** - What does it contain?
+- **How** - How will it be executed?
+- **Budget** - What resources are needed?
+- **Commitment** - What are we willing to commit?
+
+**Workflow**: 
+1. **Understand their situation** - Ask clarifying questions
+2. **Determine if alignment & signoff is needed** - Do they need alignment, or can they proceed directly?
+3. Create and refine the alignment document (we can iterate and negotiate)
+4. Share with stakeholders for review and feedback
+5. Update the alignment document until everyone is on board
+6. Once accepted and everyone is aligned
+7. Generate signoff document (contract/service agreement/signoff) to secure commitment
+8. Then proceed to the full Project Brief workflow
+
+**Key Principle**: WDS helps with alignment - we'll work together to get everyone on the same page. Negotiation and iteration are welcome during the alignment phase. Once everyone accepts, we'll formalize the commitment with a signoff document.
+
+---
+
+## Opening Framing
+
+**First, understand their situation** (if not already clear):
+
+Before diving into the pitch, help them clarify their situation:
+
+"I'd like to understand your situation first. This will help me guide you efficiently.
+
+**Are you:**
+- A consultant proposing a solution to a client?
+- A business owner hiring consultants/suppliers to build software?
+- A manager or employee seeking approval for an internal project?
+- Or doing this yourself and don't need stakeholder alignment?
+
+Let's get clear on what you need so we can move forward."
+
+**If they need alignment & signoff** (consultant, business owner, manager/employee):
+
+"Good. We're going to work together to create an alignment document that presents your idea clearly and gets stakeholders aligned.
+
+This alignment document will help you get alignment on your idea, why it matters, what it contains, how it will be executed, the budget needed, and the commitment required. We can iterate until everyone is on board. Once they accept it, we'll create a signoff document to secure the commitment, then proceed to the full Project Brief.
+
+You can start anywhere - with something you've realized needs attention, or with a solution you have in mind. I'll guide us through the important questions in whatever order makes sense for your thinking."
+
+**If they're doing it themselves** (don't need alignment & signoff):
+
+"That's great! If you have full autonomy and don't need stakeholder alignment, you can skip alignment & signoff and go straight to the Project Brief workflow. Would you like me to help you start the Project Brief instead?"
+
+---
+
+## Next Step
+
+After the opening framing, proceed to:
+→ `step-01.5-extract-communications.md` (Optional - extract info from communications)
+
+Then continue to:
+→ `step-02-explore-sections.md`
+

package/src/workflows/1-project-brief/alignment-signoff/steps-c/step-01.5-extract-communications.md

@@ -0,0 +1,78 @@
+# Step 1.5: Extract Information from Communications and Documents (Optional)
+
+## Purpose
+
+Gather existing context from client/stakeholder communications, emails, chats, and documents to inform the pitch.
+
+---
+
+## Instruction
+
+**Ask the user** if they have any relevant communications or documents:
+
+"Do you have any email threads, chat conversations, documents, or other materials from clients or stakeholders about this project? 
+
+If you do, I can extract key information from them - things like:
+- Realizations or observations they've mentioned
+- Requirements they've discussed
+- Concerns or questions they've raised
+- Context about the project
+- Existing documentation or specifications
+
+This can help us create a more informed pitch. You can paste the content here, share the communications, or upload documents, and I'll extract the relevant information."
+
+---
+
+## If User Provides Communications or Documents
+
+**What to extract**:
+- **Realizations mentioned** - What have stakeholders realized or observed?
+- **Requirements discussed** - What do they need or want?
+- **Concerns raised** - What are their worries or questions?
+- **Context** - Background information about the project
+- **Stakeholder perspectives** - Different viewpoints or needs
+- **Timeline or urgency** - Any deadlines or timing mentioned
+- **Budget or constraints** - Any resource limitations discussed
+- **Existing specifications** - Any requirements or specs already documented
+- **Previous discussions** - Key points from past conversations
+
+**How to extract**:
+1. Read through the communications carefully
+2. Identify key themes and information
+3. Extract relevant details that inform the pitch sections
+4. Note any contradictions or different perspectives
+5. Summarize findings: "From these communications, I'm seeing..."
+
+**Use extracted information**:
+- Inform The Realization section (what realizations or observations are mentioned)
+- Inform Why It Matters (who is experiencing issues and why it matters)
+- Inform Our Commitment (any budget/resource discussions)
+- Inform Cost of Inaction (any urgency or consequences mentioned)
+- Add context throughout the pitch
+
+**Don't**:
+- Copy entire communications or documents verbatim
+- Include personal or irrelevant details
+- Overwhelm with too much detail
+- Use information that's clearly outdated
+- Include sensitive information that shouldn't be in the pitch
+
+---
+
+## If User Doesn't Have Communications or Documents
+
+**That's fine** - Simply acknowledge and move on:
+
+"No problem! We'll work with what you know. Let's start exploring the project together."
+
+Then proceed to exploring sections.
+
+---
+
+## Next Step
+
+After extracting information (or if user doesn't have communications), proceed to:
+→ `step-02-explore-sections.md`
+
+**Note**: Use the extracted information to inform your questions as you explore each section.
+