48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
# 📝 Planning Standards (The "Blueprint" Protocol)
|
|
|
|
**Audience:** Lead Agents (Arthur, Gus, Harvey).
|
|
**Objective:** Measure twice, cut once.
|
|
|
|
> [!CRITICAL]
|
|
> **The Planning Mandate:**
|
|
> "A task without a plan is just a bug waiting to happen. Follow the Template."
|
|
|
|
## 1. 🧠 Context Minimalism
|
|
|
|
* **Rule:** Do NOT read the entire codebase.
|
|
* **Limit:** Read Top 3-5 relevant files only.
|
|
* **Compliance:** You **MUST** read `docs/manual_desenvolvimento/` if creating new components.
|
|
|
|
## 2. 📄 The Implementation Plan Template
|
|
|
|
Every `implementation_plan.md` must follow this structure EXACTLY:
|
|
|
|
```markdown
|
|
# [Goal Summary]
|
|
|
|
## User Review Required (Risk Analysis)
|
|
> [!IMPORTANT]
|
|
> Mention breaking changes here.
|
|
|
|
## Proposed Changes
|
|
### [Component Name]
|
|
#### [NEW/MODIFY] [Filename]
|
|
- Rationale
|
|
- Error Handling Strategy
|
|
|
|
## Verification Plan
|
|
### Automated
|
|
- `npm test`
|
|
- `python validate.py`
|
|
|
|
### Visual
|
|
- "Open browser to localhost:8080 and check X"
|
|
```
|
|
|
|
## 3. 🛡️ The Plan Validator
|
|
|
|
Before executing, run this mental check:
|
|
- [ ] Did I verify `project_map.md` to avoid duplicating files?
|
|
- [ ] Is every "Proposed Change" linked to a real file path?
|
|
- [ ] Did I include a Verification Step for *each* change?
|