Files

Cassel 647cbec54f docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-19 13:29:03 -04:00

3.7 KiB

Raw Blame History

name, description, web_bundle

name	description	web_bundle
scenarios	Create UX scenario outlines from Trigger Map through structured micro-steps	true

Phase 3: UX Scenarios

Goal: Transform the Trigger Map into concrete UX scenario outlines — linear sunshine paths that expose all pages for design scrutiny.

Your Role: UX Scenario Facilitator collaborating with the project owner — you ASK, the user DECIDES. You bring scenario thinking and user journey expertise. Work together as equals.

WORKFLOW ARCHITECTURE

This uses step-file architecture for disciplined execution:

Core Principles

Micro-file Design: Each step is a self-contained instruction file
Just-In-Time Loading: Only current step file is in memory
Sequential Enforcement: Steps must be completed in order
User Checkpoints: Steps 02 and 04 require user approval before proceeding
Quality Validation: Step 07 validates all scenarios against rubric

Step Processing Rules

READ COMPLETELY: Always read entire step file before taking any action
FOLLOW SEQUENCE: Execute all sections in order, never deviate
LOAD NEXT: When directed, load, read entire file, then execute next step
CHECKPOINT: When a step says "wait for user", do NOT auto-proceed

Critical Rules (NO EXCEPTIONS)

NEVER load multiple step files simultaneously
ALWAYS read entire step file before execution
NEVER skip steps or optimize the sequence
ALWAYS follow the exact instructions in step file

Prerequisites

Phase 1: Product Brief (required)
Phase 2: Trigger Map (required)

Steps

#	File	Purpose
01	Load Context	Read all prerequisite artifacts, detect project state
02	Analyze Scope	Determine site type, pages, scale strategy (user checkpoint)
03	Build Strategic Context	Extract strategic context from Trigger Map
04	Suggest Scenarios	Present scenario plan for approval (user checkpoint)
05	Outline Scenario	Detail ONE scenario (loops for each)
06	Generate Overview	Create 00-ux-scenarios.md index file
07	Quality Review	Self-review against rubric
08	Update Design Log	Document phase completion in project log
09	Handover	Complete Phase 3, prepare Phase 4

INITIALIZATION

1. Configuration Loading

Load and read full config from {project-root}/_bmad/wds/config.yaml and resolve:

project_name, output_folder, user_name, communication_language, document_output_language

2. Design Log

Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.

3. Mode Determination

Check invocation:

"validate" / -v → Load and execute ./workflow-validate.md
Default (create) → Continue to step 3

4. First Step

Load and execute ./steps-c/step-01-load-context.md to begin.

REFERENCE CONTENT

Location	Purpose
`data/quality-checklist.md`	Scenario quality checklist
`data/scenario-outline-template.md`	Scenario outline template
`data/validation-standards.md`	Validation standards

OUTPUT

{output_folder}/C-UX-Scenarios/00-ux-scenarios.md — Scenario index with coverage matrix
{output_folder}/C-UX-Scenarios/NN-[scenario-name]/NN-[scenario-name].md — Individual scenario outlines

AFTER COMPLETION

Update design log
Suggest next action or proceed to Phase 4: UX Design

3.7 KiB Raw Blame History