whiteport-design-studio 0.1.0

package/src/workflows/6-design-deliveries/workflow.md

@@ -0,0 +1,67 @@
+# Phase 6: Design Deliveries Workflow
+
+**Package complete testable flows and hand off to development**
+
+---
+
+## Purpose
+
+Phase 6 is where you package complete testable flows and hand off to development.
+
+**This is an iterative phase** - you'll repeat it for each complete flow you design.
+
+---
+
+## Workflow Architecture
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation
+
+---
+
+## Phase 6 Micro-Steps
+
+```
+Phase 6.1: Detect Epic Completion
+    ↓ (Is flow complete and testable?)
+Phase 6.2: Create Design Delivery
+    ↓ (Package into DD-XXX.yaml)
+Phase 6.3: Create Test Scenario
+    ↓ (Define validation tests)
+Phase 6.4: Handoff Dialog
+    ↓ (20-30 min with BMad Architect)
+Phase 6.5: Hand Off to BMad
+    ↓ (Mark as in_development)
+Phase 6.6: Continue with Next Flow
+    ↓ (Return to Phase 4-5)
+```
+
+---
+
+## Execution
+
+Load and execute `steps/step-6.1-detect-completion.md` to begin the workflow.
+
+**Note:** Each step will guide you to the next step when ready.
+
+---
+
+## Templates
+
+- `templates/design-delivery.template.yaml`
+- `templates/test-scenario.template.yaml`
+
+---
+
+## Resources
+
+- `src/core/resources/wds/design-delivery-spec.md`
+- `src/core/resources/wds/handoff-protocol.md`
+- `src/core/resources/wds/integration-guide.md`
+
+---
+
+**Phase 6 is where design becomes development! Package, handoff, and keep moving!** 📦✨

package/src/workflows/7-testing/steps/step-7.1-receive-notification.md

@@ -0,0 +1,261 @@
+# Step 7.1: Receive Notification
+
+## Your Task
+
+BMad has notified you that a feature is complete and ready for designer validation.
+
+---
+
+## BMad Notification
+
+**You receive:**
+
+```
+BMad Developer: "Feature complete: DD-XXX [Flow Name]
+
+                 Implemented:
+                 ✓ All [number] scenarios
+                 ✓ All error states
+                 ✓ All edge cases
+                 ✓ Design system components
+
+                 Build: v0.1.0-beta.1
+                 Environment: Staging
+                 Device: [Platform details]
+
+                 Ready for designer validation.
+                 Test scenario: test-scenarios/TS-XXX.yaml
+
+                 Please validate and let me know if any issues."
+```
+
+---
+
+## Acknowledge Receipt
+
+**Respond promptly:**
+
+```
+WDS Designer: "Received! Starting validation testing for DD-XXX.
+
+               I'll run through test scenario TS-XXX and report
+               back within [timeframe].
+
+               Thanks for the notification!"
+```
+
+**Set expectations:**
+
+- Small flow: "Will complete testing today"
+- Medium flow: "Will complete testing within 2 days"
+- Large flow: "Will complete testing within 1 week"
+
+---
+
+## Verify Information
+
+**Check that you have all the details:**
+
+### Build Information
+
+- [ ] Build version number (e.g., v0.1.0-beta.1)
+- [ ] Environment (staging, test, etc.)
+- [ ] Access credentials (if needed)
+- [ ] Platform details (iOS, Android, web, etc.)
+
+### Test Scenario
+
+- [ ] Test scenario file exists: `test-scenarios/TS-XXX.yaml`
+- [ ] Test scenario matches this delivery
+- [ ] All test cases are defined
+
+### Design Artifacts
+
+- [ ] Design Delivery file: `deliveries/DD-XXX.yaml`
+- [ ] Scenario specifications: `C-Scenarios/`
+- [ ] Design system specs: `D-Design-System/`
+
+---
+
+## Missing Information?
+
+**If anything is missing, ask immediately:**
+
+```
+WDS Designer: "Quick question before I start testing:
+
+               - What's the staging URL?
+               - Do I need login credentials?
+               - Which device should I test on?
+
+               Thanks!"
+```
+
+**Don't start testing until you have everything!**
+
+---
+
+## Schedule Testing
+
+**Block time for testing:**
+
+### Small Flow (1-2 scenarios)
+
+- **Time needed:** 2-4 hours
+- **Schedule:** Same day or next day
+
+### Medium Flow (3-5 scenarios)
+
+- **Time needed:** 1-2 days
+- **Schedule:** Within 2 days
+
+### Large Flow (6+ scenarios)
+
+- **Time needed:** 3-5 days
+- **Schedule:** Within 1 week
+
+**Add buffer for:**
+
+- Finding issues
+- Creating issue tickets
+- Writing test report
+
+---
+
+## Set Up Tracking
+
+**Create testing session:**
+
+```markdown
+# Testing Session: DD-XXX
+
+**Delivery:** DD-XXX [Flow Name]
+**Build:** v0.1.0-beta.1
+**Started:** 2024-12-09 14:00
+**Tester:** [Your name]
+**Environment:** Staging
+**Device:** iPhone 14 Pro (iOS 17)
+
+**Status:** In Progress
+
+**Test Scenario:** test-scenarios/TS-XXX.yaml
+
+**Progress:**
+
+- [ ] Happy path tests
+- [ ] Error state tests
+- [ ] Edge case tests
+- [ ] Design system validation
+- [ ] Accessibility tests
+
+**Issues Found:** 0
+**Test Report:** test-reports/TR-XXX-2024-12-09.md
+```
+
+---
+
+## Communication
+
+**Keep BMad informed:**
+
+```
+WDS Designer: "Testing update for DD-XXX:
+
+               Started: Today 2pm
+               Progress: Running happy path tests
+               Expected completion: Tomorrow 5pm
+
+               Will notify you when complete!"
+```
+
+**If you find critical issues early:**
+
+```
+WDS Designer: "Quick heads up on DD-XXX:
+
+               Found critical issue in first test:
+               - Login button not working
+
+               Continuing testing to find all issues,
+               but wanted to give you early warning.
+
+               Full report coming tomorrow."
+```
+
+---
+
+## Next Step
+
+After acknowledging receipt and scheduling:
+
+```
+[C] Continue to step-7.2-prepare-testing.md
+```
+
+---
+
+## Success Metrics
+
+✅ Notification received from BMad
+✅ Receipt acknowledged promptly
+✅ All build information verified
+✅ Test scenario file confirmed
+✅ Design artifacts available
+✅ Testing time scheduled
+✅ Tracking set up
+
+---
+
+## Failure Modes
+
+❌ Not acknowledging notification
+❌ Starting testing without all information
+❌ Not scheduling dedicated testing time
+❌ No tracking set up
+❌ Not communicating timeline
+
+---
+
+## Tips
+
+### DO ✅
+
+**Respond quickly:**
+
+- Acknowledge within 24 hours
+- Set clear expectations
+- Schedule testing time
+
+**Verify everything:**
+
+- Build details
+- Access credentials
+- Test scenarios
+- Design artifacts
+
+**Communicate proactively:**
+
+- Keep BMad informed
+- Report early if critical issues
+- Set realistic timelines
+
+### DON'T ❌
+
+**Don't delay:**
+
+- Respond within 24 hours
+- Don't make BMad wait
+
+**Don't start unprepared:**
+
+- Verify you have everything
+- Don't waste time searching for files
+
+**Don't go silent:**
+
+- Keep BMad updated
+- Don't disappear during testing
+
+---
+
+**Remember:** BMad is waiting for your validation. Respond promptly and set clear expectations!

package/src/workflows/7-testing/steps/step-7.2-prepare-testing.md

@@ -0,0 +1,399 @@
+# Step 7.2: Prepare for Testing
+
+## Your Task
+
+Gather all materials and set up your testing environment before starting validation.
+
+---
+
+## Before You Start
+
+**Ensure you have:**
+
+- ✅ Completed step 7.1 (notification received)
+- ✅ Testing time scheduled
+- ✅ Build information verified
+
+---
+
+## Gather Materials
+
+### Test Scenario
+
+**Load test scenario file:**
+
+- File: `test-scenarios/TS-XXX.yaml`
+- Review all test cases
+- Understand success criteria
+- Note any special setup needed
+
+**Print or display:**
+
+- Have test scenario visible while testing
+- Check off tests as you complete them
+- Take notes on deviations
+
+---
+
+### Design Delivery
+
+**Load Design Delivery file:**
+
+- File: `deliveries/DD-XXX.yaml`
+- Review user value and success criteria
+- Review acceptance criteria
+- Understand what "done" looks like
+
+---
+
+### Scenario Specifications
+
+**Load all scenario specs:**
+
+- Directory: `C-Scenarios/`
+- Review each scenario specification
+- Note design details
+- Understand expected behavior
+
+**Example:**
+
+```
+C-Scenarios/
+├── 01-welcome/Frontend/specifications.md
+├── 02-login/Frontend/specifications.md
+├── 03-signup/Frontend/specifications.md
+└── 04-family-setup/Frontend/specifications.md
+```
+
+---
+
+### Design System Specs
+
+**Load design system specs:**
+
+- Directory: `D-Design-System/`
+- Review component specifications
+- Review design tokens
+- Note exact colors, sizes, spacing
+
+**Example:**
+
+```
+D-Design-System/
+├── 02-Foundation/
+│   ├── Colors/tokens.json
+│   ├── Typography/tokens.json
+│   └── Spacing/tokens.json
+└── 03-Atomic-Components/
+    ├── Buttons/Button-Primary.md
+    ├── Inputs/Input-Text.md
+    └── Cards/Card-Default.md
+```
+
+---
+
+## Set Up Environment
+
+### Access the Build
+
+**Staging environment:**
+
+- URL: [Staging URL]
+- Credentials: [Username/Password]
+- Platform: [iOS/Android/Web]
+
+**Install build (if needed):**
+
+```bash
+# iOS TestFlight
+- Open TestFlight app
+- Install build v0.1.0-beta.1
+
+# Android
+- Download APK from [URL]
+- Install on device
+
+# Web
+- Navigate to [Staging URL]
+- Clear cache first
+```
+
+---
+
+### Prepare Test Devices
+
+**Primary device:**
+
+- [ ] Device charged (>80%)
+- [ ] Connected to WiFi
+- [ ] Screen recording enabled
+- [ ] Screenshot tools ready
+
+**Secondary device (if needed):**
+
+- [ ] Different platform (iOS vs Android)
+- [ ] Different screen size
+- [ ] Different OS version
+
+---
+
+### Set Up Tools
+
+**Screen recording:**
+
+- [ ] QuickTime (Mac)
+- [ ] Built-in screen recorder (iOS/Android)
+- [ ] OBS Studio (Desktop)
+
+**Screenshot tools:**
+
+- [ ] Native screenshot (Command+Shift+4)
+- [ ] Annotate screenshots (Preview, Skitch)
+
+**Note-taking:**
+
+- [ ] Markdown editor open
+- [ ] Test tracking document ready
+- [ ] Issue template ready
+
+**Accessibility tools:**
+
+- [ ] VoiceOver (iOS) or TalkBack (Android)
+- [ ] Color contrast checker
+- [ ] Zoom/magnification
+
+---
+
+## Prepare Test Data
+
+**Create test accounts:**
+
+```
+Test User 1:
+- Email: test1@example.com
+- Password: TestPass123!
+- Purpose: Happy path testing
+
+Test User 2:
+- Email: test2@example.com
+- Password: TestPass123!
+- Purpose: Error state testing
+
+Test User 3:
+- Email: existing@example.com
+- Password: TestPass123!
+- Purpose: "Email already exists" error
+```
+
+**Prepare test data:**
+
+- [ ] Valid emails
+- [ ] Invalid emails (for error testing)
+- [ ] Strong passwords
+- [ ] Weak passwords (for validation testing)
+- [ ] Special characters
+- [ ] Edge case data (very long names, etc.)
+
+---
+
+## Create Testing Workspace
+
+**File structure:**
+
+```
+testing/DD-XXX/
+├── screenshots/
+│   ├── HP-001-step-1.png
+│   ├── HP-001-step-2.png
+│   └── ISS-001-button-color.png
+├── screen-recordings/
+│   ├── happy-path-full-flow.mov
+│   └── error-state-email-exists.mov
+├── notes.md
+└── issues-found.md
+```
+
+**Create directories:**
+
+```bash
+mkdir -p testing/DD-XXX/screenshots
+mkdir -p testing/DD-XXX/screen-recordings
+touch testing/DD-XXX/notes.md
+touch testing/DD-XXX/issues-found.md
+```
+
+---
+
+## Review Test Plan
+
+**Understand what you're testing:**
+
+### Happy Path Tests
+
+- [ ] [Number] tests defined
+- [ ] Understand each test flow
+- [ ] Know expected results
+
+### Error State Tests
+
+- [ ] [Number] tests defined
+- [ ] Understand error scenarios
+- [ ] Know expected error messages
+
+### Edge Case Tests
+
+- [ ] [Number] tests defined
+- [ ] Understand unusual scenarios
+- [ ] Know expected behavior
+
+### Design System Validation
+
+- [ ] [Number] components to check
+- [ ] Know exact specifications
+- [ ] Have design tokens ready
+
+### Accessibility Tests
+
+- [ ] Screen reader testing
+- [ ] Color contrast checking
+- [ ] Touch target verification
+
+---
+
+## Time Estimate
+
+**Calculate testing time:**
+
+```
+Happy Path Tests: [number] tests × 5 min = [time]
+Error State Tests: [number] tests × 3 min = [time]
+Edge Case Tests: [number] tests × 5 min = [time]
+Design System: [number] components × 10 min = [time]
+Accessibility: 30 min
+Documentation: 1 hour
+
+Total: [time]
+Buffer (20%): [time]
+
+Estimated Total: [time]
+```
+
+---
+
+## Final Checklist
+
+**Before starting testing:**
+
+- [ ] Test scenario loaded and reviewed
+- [ ] Design Delivery loaded and reviewed
+- [ ] All scenario specs loaded
+- [ ] Design system specs loaded
+- [ ] Build accessible and working
+- [ ] Test devices ready
+- [ ] Tools set up (recording, screenshots, notes)
+- [ ] Test data prepared
+- [ ] Workspace created
+- [ ] Time blocked on calendar
+- [ ] BMad notified you're starting
+
+---
+
+## Start Testing
+
+**When ready:**
+
+```
+WDS Designer → BMad Developer
+
+"Starting validation testing for DD-XXX now.
+
+Environment: Staging
+Device: iPhone 14 Pro (iOS 17)
+Test Scenario: TS-XXX.yaml
+
+Will report back with results by [date/time].
+
+Thanks!"
+```
+
+---
+
+## Next Step
+
+After preparation is complete:
+
+```
+[C] Continue to step-7.3-run-tests.md
+```
+
+---
+
+## Success Metrics
+
+✅ All materials gathered
+✅ Environment set up and accessible
+✅ Test devices ready
+✅ Tools configured
+✅ Test data prepared
+✅ Workspace created
+✅ Test plan reviewed
+✅ Time estimated
+✅ BMad notified
+
+---
+
+## Failure Modes
+
+❌ Starting testing without materials
+❌ Can't access staging environment
+❌ Test devices not ready
+❌ No screen recording capability
+❌ No test data prepared
+❌ No time estimate
+❌ Not notifying BMad
+
+---
+
+## Tips
+
+### DO ✅
+
+**Be thorough:**
+
+- Gather everything before starting
+- Don't interrupt testing to find files
+
+**Be organized:**
+
+- Create workspace structure
+- Name files clearly
+- Take notes as you go
+
+**Be realistic:**
+
+- Estimate time accurately
+- Add buffer for issues
+- Block calendar time
+
+### DON'T ❌
+
+**Don't rush:**
+
+- Take time to prepare properly
+- Don't skip setup steps
+
+**Don't improvise:**
+
+- Follow test scenario
+- Use prepared test data
+- Stick to the plan
+
+**Don't forget tools:**
+
+- Screen recording is critical
+- Screenshots document issues
+- Notes capture details
+
+---
+
+**Remember:** Good preparation = efficient testing. Take time to set up properly!