Step 1: UX Design Workflow Initialization

MANDATORY EXECUTION RULES (READ FIRST):

🛑 NEVER generate content without user input
📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
📋 YOU ARE A UX FACILITATOR, not a content generator
💬 FOCUS on initialization and setup only - don't look ahead to future steps
🚪 DETECT existing workflow state and handle continuation properly
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config {communication_language}

EXECUTION PROTOCOLS:

🎯 Show your analysis before taking any action
💾 Initialize document and update frontmatter
📖 Set up frontmatter stepsCompleted: [1] before loading next step
🚫 FORBIDDEN to load next step until setup is complete

CONTEXT BOUNDARIES:

Variables from workflow.md are available in memory
Previous context = what's in output document + frontmatter
Don't assume knowledge from other steps
Input document discovery happens in this step

YOUR TASK:

Initialize the UX design workflow by detecting continuation state and setting up the design specification document.

INITIALIZATION SEQUENCE:

1. Check for Existing Workflow

First, check if the output document already exists:

Look for file at {planning_artifacts}/*ux-design-specification*.md
If exists, read the complete file including frontmatter
If not exists, this is a fresh workflow

2. Handle Continuation (If Document Exists)

If the document exists and has frontmatter with stepsCompleted:

STOP here and load ./step-01b-continue.md immediately
Do not proceed with any initialization tasks
Let step-01b handle the continuation logic

3. Fresh Workflow Setup (If No Document)

If no document exists or no stepsCompleted in frontmatter:

A. Input Document Discovery

Discover and load context documents using smart discovery. Documents can be in the following locations:

{planning_artifacts}/**
{output_folder}/**
{product_knowledge}/**
docs/**

Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for *foo*.md and not found, also search for a folder called foo/index.md (which indicates sharded content)

Try to discover the following:

Product Brief (*brief*.md)
Research Documents (*prd*.md)
Project Documentation (generally multiple documents might be found for this in the {product_knowledge} or docs folder.)
Project Context (**/project-context.md)

Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules

Loading Rules:

Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
index.md is a guide to what's relevant whenever available
Track all successfully loaded files in frontmatter inputDocuments array

B. Create Initial Document

Copy the template from {installed_path}/ux-design-template.md to {planning_artifacts}/ux-design-specification.md Initialize frontmatter in the template.

C. Complete Initialization and Report

Complete setup and report to user:

Document Setup:

Created: {planning_artifacts}/ux-design-specification.md from template
Initialized frontmatter with workflow state

Input Documents Discovered: Report what was found: "Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.

Documents Found:

PRD: {number of PRD files loaded or "None found"}
Product brief: {number of brief files loaded or "None found"}
Other context: {number of other files loaded or "None found"}

Files loaded: {list of specific file names or "No additional documents found"}

Do you have any other documents you'd like me to include, or shall we continue to the next step?

[C] Continue to UX discovery"

NEXT STEP:

After user selects [C] to continue, ensure the file {planning_artifacts}/ux-design-specification.md has been created and saved, and then load ./step-02-discovery.md to begin the UX discovery phase.

Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!

SUCCESS METRICS:

✅ Existing workflow detected and handed off to step-01b correctly ✅ Fresh workflow initialized with template and frontmatter ✅ Input documents discovered and loaded using sharded-first logic ✅ All discovered files tracked in frontmatter inputDocuments ✅ User confirmed document setup and can proceed

FAILURE MODES:

❌ Proceeding with fresh initialization when existing workflow exists ❌ Not updating frontmatter with discovered input documents ❌ Creating document without proper template ❌ Not checking sharded folders first before whole files ❌ Not reporting what documents were found to user

❌ CRITICAL: Reading only partial step file - leads to incomplete understanding and poor decisions ❌ CRITICAL: Proceeding with 'C' without fully reading and understanding the next step file ❌ CRITICAL: Making decisions without complete understanding of step requirements and protocols

step-01-init.md 5.6 KB Историја Датотека