whiteport-design-studio 0.1.0 → 0.2.0

package/src/workflows/1-project-brief/steps-v/step-01-brief-completeness.md

@@ -0,0 +1,122 @@
+---
+name: 'step-01-brief-completeness'
+description: 'Verify Product Brief contains all required sections'
+
+# File References
+nextStepFile: './step-02-vtc-consistency.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Validation Step 01: Brief Completeness
+
+## STEP GOAL:
+Verify the Product Brief contains all required sections and no section is left as a placeholder.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+- You are a Strategic Business Analyst validating Product Brief completeness
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
+- Maintain collaborative and strategic tone throughout
+
+### Step-Specific Rules:
+- Focus: Verify all required sections present and filled with substantive content
+- FORBIDDEN: Do not skip any required section check
+- Approach: Load brief, check sections by brief level, assess quality, report
+
+## EXECUTION PROTOCOLS:
+- Primary goal: Product Brief completeness verified
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: Product Brief and project config
+- Focus: Section completeness and quality
+- Limits: Validation only, not modification
+- Dependencies: Phase 1 creation steps completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load Product Brief
+
+Read `{output_folder}/A-Product-Brief/project-brief.md` and extract all sections.
+
+### 2. Required Sections (Complete Brief)
+
+- [ ] Project Vision — clear, specific, not generic
+- [ ] Market Positioning — target, need, category, benefit, differentiator
+- [ ] Business Model — revenue model defined
+- [ ] Target Users — at least one user profile with behavioral description
+- [ ] Success Criteria — at least 3 measurable metrics
+- [ ] Competitive Landscape — at least 2 competitors analyzed
+- [ ] Constraints — documented (even if "none identified")
+- [ ] Platform Strategy — platform decisions stated
+
+### 3. Required Sections (Simplified Brief)
+
+If `brief_level = simplified`, check:
+- [ ] Project summary present
+- [ ] Target audience identified
+- [ ] Key goals stated
+- [ ] Platform noted
+
+### 4. Section Quality
+
+For each section:
+- [ ] Contains substantive content (not just headings)
+- [ ] No TODO/placeholder markers remain
+- [ ] Content aligns with section purpose
+
+### 5. Report
+
+```
+## Brief Completeness Report
+
+**Brief level:** [complete/simplified]
+**Sections present:** [N]/[Total]
+**Quality issues:** [N]
+
+[List any missing or incomplete sections]
+```
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- All required sections checked
+- Section quality assessed
+- Completeness report generated
+- Missing or incomplete sections identified
+
+### FAILURE:
+- Skipped required section checks
+- Did not assess section quality
+- Left sections unverified
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-v/step-02-vtc-consistency.md

@@ -0,0 +1,123 @@
+---
+name: 'step-02-vtc-consistency'
+description: 'Verify Value Trigger Chain consistency and validity'
+
+# File References
+nextStepFile: './step-03-seo-strategy.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Validation Step 02: VTC Consistency
+
+## STEP GOAL:
+Verify the Value Trigger Chain(s) form a valid chain from business goals through personas to driving forces.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+- You are a Strategic Business Analyst validating VTC chain integrity
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
+- Maintain collaborative and strategic tone throughout
+
+### Step-Specific Rules:
+- Focus: VTC completeness, chain validity, cross-VTC consistency
+- FORBIDDEN: Do not skip chain validity checks
+- Approach: Locate VTCs, check completeness, validate chains, check cross-VTC consistency
+
+## EXECUTION PROTOCOLS:
+- Primary goal: VTC consistency verified
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: VTC files and Product Brief
+- Focus: Chain validity and consistency
+- Limits: Validation only, not modification
+- Dependencies: Step 01 completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Locate VTC Files
+
+Check for:
+- `{output_folder}/A-Product-Brief/vtc-primary.yaml` (Product Pitch VTC)
+- Any scenario-level VTCs in `{output_folder}/C-UX-Scenarios/`
+
+### 2. VTC Completeness
+
+For each VTC:
+- [ ] `businessGoal` — specific and measurable
+- [ ] `solution` — describes how we help the user
+- [ ] `user` — identifies who we're helping
+- [ ] `drivingForces.positive` — at least 2 entries
+- [ ] `drivingForces.negative` — at least 2 entries
+- [ ] `customerAwareness.start` — defined
+- [ ] `customerAwareness.end` — defined
+
+### 3. Chain Validity
+
+- [ ] Business goal in VTC matches a goal in the Product Brief
+- [ ] User in VTC matches a target user in the Product Brief
+- [ ] Driving forces are specific (not generic like "wants it to work")
+- [ ] Awareness journey makes logical sense (start ≠ end)
+
+### 4. Cross-VTC Consistency (if multiple)
+
+- [ ] No contradictory business goals across VTCs
+- [ ] Users are distinct or represent different contexts
+- [ ] Driving forces don't duplicate across VTCs without reason
+
+### 5. Report
+
+```
+## VTC Consistency Report
+
+**VTCs found:** [N]
+**All complete:** [Yes/No]
+**Chain issues:** [N]
+
+[List any broken chains or inconsistencies]
+```
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- All VTCs located and checked
+- Completeness verified for each VTC
+- Chain validity confirmed
+- Cross-VTC consistency checked (if multiple)
+- Consistency report generated
+
+### FAILURE:
+- Skipped chain validity checks
+- Missed VTC files
+- Did not check cross-VTC consistency
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-v/step-03-seo-strategy.md

@@ -0,0 +1,117 @@
+---
+name: 'step-03-seo-strategy'
+description: 'Verify keyword map completeness and page assignments'
+
+# File References
+nextStepFile: './step-04-content-language.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Validation Step 03: SEO Strategy
+
+## STEP GOAL:
+Verify the keyword map is complete and page assignments are actionable for downstream phases.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+- You are a Strategic Business Analyst validating SEO strategy completeness
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
+- Maintain collaborative and strategic tone throughout
+
+### Step-Specific Rules:
+- Focus: Keyword map completeness, page assignments, cross-phase readiness
+- FORBIDDEN: Do not skip prerequisite check for SEO content existence
+- Approach: Check prerequisites, validate keywords, verify page assignments, assess cross-phase readiness
+
+## EXECUTION PROTOCOLS:
+- Primary goal: SEO strategy validated for downstream phases
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: Content & Language document, Product Brief
+- Focus: SEO keyword strategy validation
+- Limits: Validation only, not modification
+- Dependencies: Step 02 completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 0. Prerequisites
+
+Check if SEO/keyword content exists in the Content & Language document. If not, note as "SEO not defined" and skip to next step.
+
+### 1. Keyword Map Completeness
+
+- [ ] Primary keywords defined (at least 3)
+- [ ] Each keyword has search intent classification (informational/navigational/transactional)
+- [ ] Keywords are relevant to business goals in Product Brief
+- [ ] Long-tail variants included where appropriate
+
+### 2. Page Assignments
+
+- [ ] Each primary keyword mapped to at least one intended page
+- [ ] No two pages target the exact same primary keyword
+- [ ] Page assignments are realistic given project scope
+
+### 3. Cross-Phase Readiness
+
+- [ ] Keyword map is in a format Phase 3 (Scenarios) can reference
+- [ ] SEO priorities align with user priorities from VTC
+- [ ] Content structure supports keyword targeting
+
+### 4. Report
+
+```
+## SEO Strategy Report
+
+**SEO status:** [Defined / Not defined]
+**Primary keywords:** [N]
+**Page assignments:** [N]
+**Issues:** [N]
+
+[List any gaps or conflicts in SEO strategy]
+```
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- Prerequisites checked
+- Keyword map completeness verified
+- Page assignments validated
+- Cross-phase readiness assessed
+- SEO strategy report generated
+
+### FAILURE:
+- Skipped prerequisite check
+- Did not verify page assignments
+- Left keyword quality unchecked
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-v/step-04-content-language.md

@@ -0,0 +1,124 @@
+---
+name: 'step-04-content-language'
+description: 'Verify tone, personality, and content guidelines are coherent'
+
+# File References
+nextStepFile: './step-05-visual-direction.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Validation Step 04: Content & Language
+
+## STEP GOAL:
+Verify tone, personality, and content guidelines are coherent and actionable.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+- You are a Strategic Business Analyst validating content and language coherence
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
+- Maintain collaborative and strategic tone throughout
+
+### Step-Specific Rules:
+- Focus: Brand personality, tone of voice, language strategy, content guidelines
+- FORBIDDEN: Do not skip prerequisite check for Content & Language document existence
+- Approach: Check prerequisites, validate personality, tone, language, guidelines, report
+
+## EXECUTION PROTOCOLS:
+- Primary goal: Content & Language coherence verified
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: Content & Language document, Product Brief
+- Focus: Content strategy validation
+- Limits: Validation only, not modification
+- Dependencies: Step 03 completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 0. Prerequisites
+
+Check if Content & Language document exists at `{output_folder}/A-Product-Brief/`. If not, note as "Content & Language not defined" and skip to next step.
+
+### 1. Brand Personality
+
+- [ ] Personality traits defined (at least 3)
+- [ ] Traits are specific (not just "professional" or "friendly")
+- [ ] Traits align with target user expectations from Product Brief
+
+### 2. Tone of Voice
+
+- [ ] Tone attributes defined with before/after examples
+- [ ] Tone is consistent with personality traits
+- [ ] Tone adapts to context (e.g., error messages vs. marketing)
+
+### 3. Language Strategy
+
+- [ ] Primary language specified
+- [ ] Additional languages listed (if multilingual)
+- [ ] Formality level defined (du/ni, you/thou, etc.)
+
+### 4. Content Guidelines
+
+- [ ] Writing style guidelines present
+- [ ] Content structure patterns documented (if applicable)
+- [ ] Alignment with SEO keyword strategy (if SEO defined)
+
+### 5. Report
+
+```
+## Content & Language Report
+
+**Status:** [Defined / Not defined]
+**Personality traits:** [N]
+**Tone examples:** [N]
+**Languages:** [N]
+**Issues:** [N]
+
+[List any inconsistencies or gaps]
+```
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- Prerequisites checked
+- Brand personality validated
+- Tone of voice coherence verified
+- Language strategy confirmed
+- Content guidelines assessed
+- Content & Language report generated
+
+### FAILURE:
+- Skipped prerequisite check
+- Did not verify tone coherence
+- Left personality traits unvalidated
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-v/step-05-visual-direction.md

@@ -0,0 +1,124 @@
+---
+name: 'step-05-visual-direction'
+description: 'Verify visual direction is documented for Phase 4'
+
+# File References
+nextStepFile: './step-06-platform-requirements.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Validation Step 05: Visual Direction
+
+## STEP GOAL:
+Verify visual direction is documented with enough detail for Phase 4 (UX Design).
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+- You are a Strategic Business Analyst validating visual direction completeness
+- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
+- Maintain collaborative and strategic tone throughout
+
+### Step-Specific Rules:
+- Focus: Brand assets, visual references, design style, imagery direction
+- FORBIDDEN: Do not skip prerequisite check for Visual Direction document existence
+- Approach: Check prerequisites, validate brand assets, references, style, imagery, report
+
+## EXECUTION PROTOCOLS:
+- Primary goal: Visual direction validated for Phase 4
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: Visual Direction document, Product Brief
+- Focus: Visual design readiness validation
+- Limits: Validation only, not modification
+- Dependencies: Step 04 completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 0. Prerequisites
+
+Check if Visual Direction document exists at `{output_folder}/A-Product-Brief/`. If not, note as "Visual Direction not defined" and skip to next step.
+
+### 1. Brand Assets
+
+- [ ] Existing brand assets documented (or "no existing brand" noted)
+- [ ] Logo usage guidelines (if applicable)
+- [ ] Color palette defined or referenced
+
+### 2. Visual References
+
+- [ ] At least 2 reference sites documented
+- [ ] What to take from each reference is specified (not just "I like this site")
+- [ ] References are relevant to project type
+
+### 3. Design Style
+
+- [ ] Design style described (modern, minimal, bold, etc.)
+- [ ] Layout preferences documented
+- [ ] Effect preferences documented (animations, transitions)
+
+### 4. Imagery Direction
+
+- [ ] Photography style defined (if using photos)
+- [ ] Illustration style defined (if using illustrations)
+- [ ] Image sourcing strategy noted
+
+### 5. Report
+
+```
+## Visual Direction Report
+
+**Status:** [Defined / Not defined]
+**References:** [N]
+**Style documented:** [Yes/No]
+**Imagery direction:** [Yes/No]
+**Issues:** [N]
+
+[List any gaps that would block Phase 4]
+```
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- Prerequisites checked
+- Brand assets documented or absence noted
+- Visual references validated
+- Design style completeness verified
+- Imagery direction assessed
+- Visual direction report generated
+
+### FAILURE:
+- Skipped prerequisite check
+- Did not verify reference quality
+- Left design style unvalidated
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.