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>
This commit is contained in:
138
_bmad/wds/workflows/4-ux-design/steps-p/step-09-generate-spec.md
Normal file
138
_bmad/wds/workflows/4-ux-design/steps-p/step-09-generate-spec.md
Normal file
@@ -0,0 +1,138 @@
|
||||
---
|
||||
name: 'step-09-generate-spec'
|
||||
description: 'Compile all gathered information into the complete page specification document'
|
||||
|
||||
# File References
|
||||
workflowFile: '../workflow.md'
|
||||
activityWorkflowFile: '../workflow-specify.md'
|
||||
---
|
||||
|
||||
# Step 9: Generate Specification Document
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Compile all gathered information from steps 1-8 into the complete page specification document using the specification template.
|
||||
|
||||
## 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 Freya, a creative and thoughtful UX designer collaborating with the user
|
||||
- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
|
||||
- ✅ Maintain creative and thoughtful tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on compiling all data into the specification template
|
||||
- 🚫 FORBIDDEN to skip any data section from previous steps
|
||||
- 💬 Approach: Generate, then present summary for confirmation
|
||||
- 📋 This is the final step in the Specify activity — the last step in the chain
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Generate complete specification using the page-specification template
|
||||
- 💾 Save specification to the correct output location
|
||||
- 📖 Reference all data from steps 1-8
|
||||
- 🚫 FORBIDDEN to generate with missing data sections
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All data from steps 1-8
|
||||
- Focus: Compilation and document generation
|
||||
- Limits: Use the template — do not invent new formats
|
||||
- Dependencies: All previous steps must be complete
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Generate Specification
|
||||
|
||||
<output>**Excellent! We've gathered everything we need.**
|
||||
|
||||
Now I'll compile it all into your complete page specification.</output>
|
||||
|
||||
<action>Generate specification document using template at `templates/page-specification.template.md`
|
||||
|
||||
Fill in all sections with data collected:
|
||||
|
||||
- page_basics (from step 01)
|
||||
- layout_sections (from step 02)
|
||||
- components with object_ids (from step 03)
|
||||
- multilingual_content (from step 04)
|
||||
- interaction_behaviors (from step 05)
|
||||
- page_states and component_states (from step 06)
|
||||
- validation_rules and error_messages (from step 07)
|
||||
- spacing_objects and typography_tokens (from step 08)
|
||||
</action>
|
||||
|
||||
<action>Save complete specification to:
|
||||
`{output_folder}/C-UX-Scenarios/{scenario}/{page}/{page}.md`
|
||||
</action>
|
||||
|
||||
<output>**Complete specification generated!**
|
||||
|
||||
**Saved to:** `C-UX-Scenarios/{scenario}/{page}/{page}.md`
|
||||
|
||||
**What we documented:**
|
||||
|
||||
- Page basics and routing
|
||||
- {{section_count}} layout sections
|
||||
- {{component_count}} components with Object IDs
|
||||
- Content in {{language_count}} languages
|
||||
- {{interaction_count}} interaction behaviors
|
||||
- {{state_count}} total states (page + component)
|
||||
- {{validation_count}} validation rules
|
||||
- {{error_count}} error messages
|
||||
- {{spacing_count}} spacing objects
|
||||
- {{typography_count}} typography tokens
|
||||
|
||||
**Your specification is development-ready!**</output>
|
||||
|
||||
### 2. Update Design Log
|
||||
|
||||
<action>Append a row with status `specified` to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
|
||||
|
||||
```
|
||||
| [Scenario slug] | [NN.X] | [Page name] | specified | [YYYY-MM-DD] |
|
||||
```
|
||||
|
||||
Do NOT skip this. The design log drives the adaptive dashboard.</action>
|
||||
|
||||
### 3. Return to Calling Step
|
||||
|
||||
This step is called from either step-01-exploration.md (Discuss) or workflow-suggest.md (Suggest). After updating the design log, return control to the calling workflow's transition logic — the calling step determines what comes next.
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
The specification must be generated, saved, AND the design log updated before this step is complete. This is the last step in the Specify activity.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Specification generated using the template
|
||||
- All data sections from steps 1-8 included
|
||||
- Document saved to correct output location
|
||||
- Summary presented to user with metrics
|
||||
- Specification is development-ready
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Missing data sections in the generated specification
|
||||
- Not using the specification template
|
||||
- Not saving to the correct location
|
||||
- Generating with incomplete data
|
||||
- Not presenting summary to user
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user