initial commit
This commit is contained in:
@@ -0,0 +1,122 @@
|
||||
---
|
||||
name: 'step-01-brief-completeness'
|
||||
description: 'Verify Product Brief contains all required sections'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-02-trigger-map-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: 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.
|
||||
@@ -0,0 +1,123 @@
|
||||
---
|
||||
name: 'step-02-trigger-map-consistency'
|
||||
description: 'Verify Trigger Map consistency and validity'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-03-seo-strategy.md'
|
||||
workflowFile: '../workflow.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Validation Step 02: Trigger Map Consistency
|
||||
|
||||
## STEP GOAL:
|
||||
Verify the Trigger Map(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 Trigger Map 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: Trigger Map completeness, chain validity, cross-Trigger Map consistency
|
||||
- FORBIDDEN: Do not skip chain validity checks
|
||||
- Approach: Locate Trigger Maps, check completeness, validate chains, check cross-Trigger Map consistency
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- Primary goal: Trigger Map consistency verified
|
||||
- Save/document outputs appropriately
|
||||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Trigger Map 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 Trigger Map Files
|
||||
|
||||
Check for:
|
||||
- `{output_folder}/B-Trigger-Map/00-trigger-map.md` (Trigger Map hub document)
|
||||
- Persona documents in `{output_folder}/B-Trigger-Map/`
|
||||
|
||||
### 2. Trigger Map Completeness
|
||||
|
||||
For each Trigger Map:
|
||||
- [ ] `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 Trigger Map matches a goal in the Product Brief
|
||||
- [ ] User in Trigger Map 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-Trigger Map Consistency (if multiple)
|
||||
|
||||
- [ ] No contradictory business goals across Trigger Maps
|
||||
- [ ] Users are distinct or represent different contexts
|
||||
- [ ] Driving forces don't duplicate across Trigger Maps without reason
|
||||
|
||||
### 5. Report
|
||||
|
||||
```
|
||||
## Trigger Map Consistency Report
|
||||
|
||||
**Trigger Maps 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: 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 Trigger Maps located and checked
|
||||
- Completeness verified for each Trigger Map
|
||||
- Chain validity confirmed
|
||||
- Cross-Trigger Map consistency checked (if multiple)
|
||||
- Consistency report generated
|
||||
|
||||
### FAILURE:
|
||||
- Skipped chain validity checks
|
||||
- Missed Trigger Map files
|
||||
- Did not check cross-Trigger Map consistency
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -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 Trigger Map
|
||||
- [ ] 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: 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.
|
||||
@@ -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: 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.
|
||||
@@ -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: 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.
|
||||
@@ -0,0 +1,154 @@
|
||||
---
|
||||
name: 'step-06-platform-requirements'
|
||||
description: 'Verify platform requirements and compile final validation report'
|
||||
|
||||
# File References
|
||||
workflowFile: '../workflow.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Validation Step 06: Platform Requirements
|
||||
|
||||
## STEP GOAL:
|
||||
Verify technical platform requirements are specified and consistent with project scope, then compile the final validation report.
|
||||
|
||||
## 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 completing the final validation of Phase 1
|
||||
- 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: Tech stack, integrations, contact strategy, multilingual, final validation report
|
||||
- FORBIDDEN: Do not skip compiling the final validation report across all 6 steps
|
||||
- Approach: Check prerequisites, validate platform sections, compile final report, save
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- Primary goal: Platform requirements validated and final validation report compiled
|
||||
- Save/document outputs appropriately
|
||||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Platform Requirements document, all previous validation results
|
||||
- Focus: Platform validation and final report compilation
|
||||
- Limits: Validation only, not modification
|
||||
- Dependencies: Steps 01-05 completed
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 0. Prerequisites
|
||||
|
||||
Check if Platform Requirements document exists at `{output_folder}/A-Product-Brief/`. If not, note as "Platform Requirements not defined" and skip to final report.
|
||||
|
||||
### 1. Tech Stack
|
||||
|
||||
- [ ] CMS/framework specified
|
||||
- [ ] Hosting approach noted
|
||||
- [ ] Technical constraints documented
|
||||
|
||||
### 2. Integrations
|
||||
|
||||
- [ ] Third-party integrations listed
|
||||
- [ ] Each integration has purpose documented
|
||||
- [ ] No conflicting integration choices
|
||||
|
||||
### 3. Contact Strategy
|
||||
|
||||
- [ ] Contact form requirements documented
|
||||
- [ ] Communication channels specified (email, chat, phone)
|
||||
|
||||
### 4. Multilingual (if applicable)
|
||||
|
||||
- [ ] Language switching approach defined
|
||||
- [ ] URL structure for languages specified
|
||||
- [ ] Translation workflow noted
|
||||
|
||||
### 5. Platform Report
|
||||
|
||||
```
|
||||
## Platform Requirements Report
|
||||
|
||||
**Status:** [Defined / Not defined]
|
||||
**Tech stack:** [Specified / Not specified]
|
||||
**Integrations:** [N]
|
||||
**Multilingual:** [Yes/No/N/A]
|
||||
**Issues:** [N]
|
||||
|
||||
[List any unresolved technical decisions]
|
||||
```
|
||||
|
||||
### 6. Final Validation Report
|
||||
|
||||
Compile results from all 6 validation steps:
|
||||
|
||||
```
|
||||
## Phase 1 Validation Report
|
||||
|
||||
**Project:** {project_name}
|
||||
**Date:** [date]
|
||||
**Brief level:** [complete/simplified]
|
||||
|
||||
### Results Summary
|
||||
| Check | Status | Issues |
|
||||
|-------|--------|--------|
|
||||
| Brief Completeness | pass/warn/fail | [summary] |
|
||||
| Trigger Map Consistency | pass/warn/fail | [summary] |
|
||||
| SEO Strategy | pass/warn/fail | [summary] |
|
||||
| Content & Language | pass/warn/fail | [summary] |
|
||||
| Visual Direction | pass/warn/fail | [summary] |
|
||||
| Platform Requirements | pass/warn/fail | [summary] |
|
||||
|
||||
### Critical Issues (must fix)
|
||||
[list or "None"]
|
||||
|
||||
### Warnings (should fix)
|
||||
[list or "None"]
|
||||
|
||||
### Recommendations
|
||||
[list or "All clear"]
|
||||
```
|
||||
|
||||
Save report to `{output_folder}/A-Product-Brief/validation-report.md`
|
||||
|
||||
### N. Present MENU OPTIONS
|
||||
Display: "**Select an Option:** [M] Return to workflow menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- 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
|
||||
This is the FINAL step of the Phase 1 Validation workflow. Validation is complete.
|
||||
|
||||
---
|
||||
|
||||
## SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### SUCCESS:
|
||||
- Prerequisites checked
|
||||
- Platform requirements validated
|
||||
- Final validation report compiled across all 6 steps
|
||||
- Report saved to output folder
|
||||
- User informed of validation results
|
||||
|
||||
### FAILURE:
|
||||
- Skipped prerequisite check
|
||||
- Did not compile final validation report
|
||||
- Left platform sections unverified
|
||||
- Did not save report
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user