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:
@@ -0,0 +1,111 @@
|
||||
---
|
||||
name: 'step-27-platform-init'
|
||||
description: 'Initialize platform requirements capture'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-28-tech-stack.md'
|
||||
workflowFile: '../workflow.md'
|
||||
activityWorkflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 27: Initialize Platform Requirements
|
||||
|
||||
## STEP GOAL:
|
||||
Welcome user and set context for capturing platform decisions.
|
||||
|
||||
## 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 documenting technical decisions that constrain UX design and development
|
||||
- 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: Initialize platform requirements, assess technical knowledge, capture existing decisions
|
||||
- FORBIDDEN: Do not use overly technical language without assessing user's technical level
|
||||
- Approach: Welcome, contextualize, assess technical knowledge, capture existing decisions
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- Primary goal: Platform requirements document initialized, technical level assessed
|
||||
- Save/document outputs appropriately
|
||||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Product Brief, Content & Language, Visual Direction
|
||||
- Focus: Platform requirements initialization
|
||||
- Limits: Not making technical decisions yet - setting context
|
||||
- Dependencies: Steps 1-26 completed
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Create Output File
|
||||
- Create `platform-requirements.md` in the output folder using the template
|
||||
- Initialize frontmatter with `stepsCompleted: []`
|
||||
|
||||
### 2. Welcome and Contextualize
|
||||
- "Now let's document the technical platform decisions. These will define what's possible in UX design and what developers need to know."
|
||||
- Reference the Product Brief if available for context
|
||||
|
||||
### 3. Assess Technical Knowledge
|
||||
- Ask: "How familiar are you with the technical aspects? This helps me know how much to explain."
|
||||
- Options: [A] Very technical, [B] Some knowledge, [C] Not technical at all
|
||||
- Adjust language accordingly in subsequent steps
|
||||
|
||||
### 4. Confirm Existing Decisions
|
||||
- Ask: "Are there any technical decisions already made? (hosting provider, CMS, framework, etc.)"
|
||||
- If yes, capture these first
|
||||
- If no, proceed to exploration
|
||||
|
||||
### 5. Design Log Update
|
||||
After completing this step, update the design log:
|
||||
|
||||
```markdown
|
||||
### Step 27: Platform Init
|
||||
**Q:** Technical familiarity? Existing decisions?
|
||||
**A:** [User responses - summarized]
|
||||
**Documented in:** platform-requirements.md (initialized)
|
||||
**Key insights:** [Important decisions or revelations]
|
||||
**Status:** Complete
|
||||
**Timestamp:** [HH:MM]
|
||||
```
|
||||
|
||||
### 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:
|
||||
- Output file created and initialized
|
||||
- Technical knowledge level assessed
|
||||
- Existing decisions captured
|
||||
- User confirmed readiness
|
||||
|
||||
### FAILURE:
|
||||
- Skipped technical knowledge assessment
|
||||
- Used overly technical language for non-technical user
|
||||
- Did not create output file before proceeding
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user