agentic-sdlc 1.0.0 → 1.5.0

package/.agent/rules/AUTO-LEARNING.md

@@ -0,0 +1,418 @@
+# 🧠 Automatic Knowledge Base Learning System
+
+## Purpose
+This system automatically captures and stores knowledge from every task, issue, and bug fix to build project intelligence over time.
+
+---
+
+## 🔄 Auto-Learning Triggers
+
+### Mandatory Knowledge Capture
+The following events **MUST** trigger automatic knowledge base entry creation:
+
+| Event | Trigger Condition | Auto-Create Entry |
+|-------|------------------|-------------------|
+| **Bug Fixed** | Any bug with priority medium+ | ✅ Yes |
+| **Multiple Attempts** | Task required 3+ attempts | ✅ Yes |
+| **Error Pattern** | Same error occurred 2+ times | ✅ Yes |
+| **Complex Feature** | Implementation took 4+ hours | ✅ Yes |
+| **Security Issue** | Any security vulnerability found | ✅ Yes |
+| **Performance Fix** | Performance optimization applied | ✅ Yes |
+| **Integration Issue** | Third-party integration problem | ✅ Yes |
+| **Platform Issue** | Platform-specific problem solved | ✅ Yes |
+| **Architecture Decision** | Major design decision made | ✅ Yes |
+| **Rollback Event** | Deployment rolled back | ✅ Yes |
+
+---
+
+## 📝 Auto-Learning Workflow
+
+### Step 1: Detection (Automatic)
+When any agent completes a task, they MUST check if it meets learning criteria:
+
+```markdown
+### Knowledge Base Check
+- [ ] Bug priority: [critical/high/medium/low]
+- [ ] Attempts required: [number]
+- [ ] Similar issues before: [yes/no]
+- [ ] Implementation complexity: [simple/moderate/complex]
+- [ ] Security impact: [yes/no]
+- [ ] Performance impact: [yes/no]
+
+**Auto-Learn Required:** [YES/NO]
+```
+
+### Step 2: Capture (Automatic)
+If auto-learn is required, immediately create knowledge entry:
+
+```markdown
+## Auto-Generated Knowledge Entry
+
+**Entry ID:** KB-[YYYY-MM-DD]-[###]-[auto-title]
+**Category:** [bugs/features/architecture/security/performance/platform]
+**Severity:** [critical/high/medium/low]
+**Auto-Generated:** Yes
+**Source:** [Task ID / Issue ID / Bug ID]
+
+### Problem
+[Auto-extracted from task description]
+
+### Context
+- Sprint: [N]
+- Component: [name]
+- Technology: [stack]
+- Platform: [web/mobile/desktop/cli]
+
+### Solution Applied
+[Auto-extracted from implementation]
+
+### Root Cause
+[To be filled by agent]
+
+### Prevention
+[To be filled by agent]
+
+### Tags
+#auto-learned #[category] #[technology] #[severity]
+```
+
+### Step 3: Index Update (Automatic)
+Automatically update `knowledge-base/index.md`:
+
+```markdown
+| KB-[date]-[###] | [Title] | [Category] | [Severity] | [Tags] | [Date] | Auto |
+```
+
+### Step 4: Cross-Reference (Automatic)
+Link to related entries:
+- Search for similar keywords
+- Link to related bugs/features
+- Update related entries with new insights
+
+---
+
+## 🎯 Role-Specific Auto-Learning
+
+### @DEV - Development Learning
+**Auto-capture when:**
+- Bug fixed (any priority)
+- Code refactoring completed
+- Performance optimization applied
+- Integration implemented
+
+**Knowledge Type:** Code patterns, bug fixes, optimizations
+
+### @DEVOPS - Infrastructure Learning
+**Auto-capture when:**
+- Deployment issue resolved
+- Configuration changed
+- Infrastructure scaled
+- Monitoring alert triggered
+
+**Knowledge Type:** Deployment patterns, infrastructure issues
+
+### @TESTER - Testing Learning
+**Auto-capture when:**
+- Test failure pattern identified
+- Edge case discovered
+- Test automation challenge solved
+- Regression bug found
+
+**Knowledge Type:** Test patterns, edge cases, regression patterns
+
+### @SECA - Security Learning
+**Auto-capture when:**
+- Security vulnerability found
+- Security scan issue resolved
+- Authentication/authorization issue fixed
+- Data protection measure implemented
+
+**Knowledge Type:** Security vulnerabilities, attack patterns, fixes
+
+### @SA - Architecture Learning
+**Auto-capture when:**
+- Architecture decision made
+- Design pattern applied
+- Scalability issue addressed
+- Technology choice made
+
+**Knowledge Type:** Architecture patterns, design decisions
+
+### @UIUX - Design Learning
+**Auto-capture when:**
+- UX issue identified and fixed
+- Accessibility improvement made
+- Design pattern applied
+- User feedback incorporated
+
+**Knowledge Type:** UX patterns, accessibility solutions
+
+---
+
+## 🤖 Automated Knowledge Entry Template
+
+Every agent MUST use this template for auto-learning:
+
+```markdown
+---
+id: KB-[YYYY-MM-DD]-[###]
+title: [Auto-Generated Title]
+category: [bugs/features/architecture/security/performance/platform]
+severity: [critical/high/medium/low]
+auto-generated: true
+source-task: [Task/Issue/Bug ID]
+sprint: [N]
+date: [YYYY-MM-DD]
+author: [@ROLE]
+tags: [#tag1, #tag2, #tag3]
+---
+
+# [Title]
+
+## 📋 Metadata
+- **Entry ID:** KB-[YYYY-MM-DD]-[###]
+- **Category:** [Category]
+- **Severity:** [Severity]
+- **Sprint:** [N]
+- **Date:** [YYYY-MM-DD]
+- **Author:** [@ROLE]
+- **Source:** [Task/Issue/Bug ID]
+- **Auto-Generated:** Yes
+
+## 🔍 Problem Description
+[Clear description of the problem encountered]
+
+## 🌍 Context
+- **Component:** [Component name]
+- **Technology:** [Tech stack]
+- **Platform:** [web/mobile/desktop/cli]
+- **Environment:** [dev/staging/production]
+- **Related Files:** [List of files]
+
+## 🚨 Symptoms
+- [Symptom 1]
+- [Symptom 2]
+- [Symptom 3]
+
+## 🔬 Root Cause Analysis
+[Detailed explanation of why the issue occurred]
+
+## ✅ Solution Applied
+[Step-by-step solution that worked]
+
+```code
+[Code snippets if applicable]
+```
+
+## 🛡️ Prevention Measures
+- [ ] [Prevention measure 1]
+- [ ] [Prevention measure 2]
+- [ ] [Prevention measure 3]
+
+## 📊 Impact Assessment
+- **Severity:** [critical/high/medium/low]
+- **Affected Users:** [number/percentage]
+- **Downtime:** [duration]
+- **Data Loss:** [yes/no]
+
+## 🔗 Related Entries
+- [KB-YYYY-MM-DD-###] - [Related entry title]
+- [KB-YYYY-MM-DD-###] - [Related entry title]
+
+## 📚 References
+- [Documentation link]
+- [Stack Overflow link]
+- [GitHub issue link]
+
+## 🏷️ Tags
+#auto-learned #[category] #[technology] #[severity] #sprint-[N]
+
+---
+*Auto-generated by @[ROLE] on [YYYY-MM-DD]*
+```
+
+---
+
+## 🔍 Auto-Search Before Starting
+
+Before starting ANY task, agents MUST:
+
+1. **Search Knowledge Base**
+   ```markdown
+   ### Knowledge Base Search
+   - Keywords: [list keywords]
+   - Category: [category]
+   - Technology: [tech]
+   - Results: [number] entries found
+   ```
+
+2. **Review Relevant Entries**
+   - Read top 3 most relevant entries
+   - Check for similar patterns
+   - Adapt solutions to current context
+
+3. **Document Search Results**
+   ```markdown
+   ### KB Search Results
+   - **KB-[date]-[###]:** [Title] - [Relevance: high/medium/low]
+   - **KB-[date]-[###]:** [Title] - [Relevance: high/medium/low]
+   - **Applicable Solutions:** [yes/no]
+   ```
+
+---
+
+## 📈 Learning Metrics
+
+Track these metrics in `knowledge-base/index.md`:
+
+| Metric | Description | Target |
+|--------|-------------|--------|
+| **Total Entries** | Number of KB entries | Growing |
+| **Auto-Generated** | Percentage auto-created | >80% |
+| **Reuse Rate** | Entries referenced in tasks | >50% |
+| **Resolution Time** | Average time to fix similar issues | Decreasing |
+| **Recurrence Rate** | Same issue occurring again | <10% |
+
+---
+
+## 🎯 Quality Standards for Auto-Learning
+
+Every auto-generated entry MUST include:
+
+- ✅ Clear problem description
+- ✅ Reproducible steps (if applicable)
+- ✅ Root cause analysis
+- ✅ Working solution with code
+- ✅ Prevention measures
+- ✅ Proper categorization
+- ✅ Relevant tags
+- ✅ Cross-references
+
+---
+
+## 🔄 Continuous Improvement
+
+### Weekly Review
+Every Friday, @REPORTER MUST:
+1. Review all auto-generated entries from the week
+2. Verify completeness and quality
+3. Add missing details
+4. Update cross-references
+5. Archive duplicates
+
+### Monthly Analysis
+Every month-end, @REPORTER MUST:
+1. Analyze learning metrics
+2. Identify knowledge gaps
+3. Consolidate similar entries
+4. Update index and categories
+5. Generate learning report
+
+### Quarterly Optimization
+Every quarter, @PM + @REPORTER MUST:
+1. Review entire knowledge base
+2. Archive outdated entries
+3. Refactor categories if needed
+4. Update templates
+5. Train team on new patterns
+
+---
+
+## 🚀 Integration with Workflow
+
+### In Development Log
+```markdown
+## Knowledge Base Integration
+- **KB Entries Created:** [number]
+- **KB Entries Referenced:** [number]
+- **New Patterns Learned:** [list]
+- **Prevention Measures Applied:** [list]
+```
+
+### In Test Report
+```markdown
+## Knowledge Base Integration
+- **Test Patterns Learned:** [list]
+- **Edge Cases Documented:** [number]
+- **Regression Patterns:** [list]
+```
+
+### In Phase Report
+```markdown
+## Knowledge Base Summary
+- **Total KB Entries:** [number]
+- **Categories:** [breakdown]
+- **Most Referenced:** [top 3]
+- **Learning Impact:** [description]
+```
+
+---
+
+## 🎓 Learning Categories
+
+### 1. Bug Patterns
+- Error messages and solutions
+- Common mistakes
+- Edge cases
+- Regression patterns
+
+### 2. Feature Patterns
+- Implementation approaches
+- Design patterns
+- Best practices
+- Anti-patterns to avoid
+
+### 3. Architecture Patterns
+- Design decisions
+- Scalability solutions
+- Technology choices
+- Integration patterns
+
+### 4. Security Patterns
+- Vulnerabilities and fixes
+- Security best practices
+- Attack patterns
+- Protection measures
+
+### 5. Performance Patterns
+- Optimization techniques
+- Bottleneck solutions
+- Caching strategies
+- Resource management
+
+### 6. Platform Patterns
+- Platform-specific issues
+- Cross-platform solutions
+- Device-specific problems
+- Browser compatibility
+
+---
+
+## 🔐 Access Control
+
+| Role | Create | Read | Update | Delete |
+|------|--------|------|--------|--------|
+| @DEV | ✅ | ✅ | ✅ | ❌ |
+| @DEVOPS | ✅ | ✅ | ✅ | ❌ |
+| @TESTER | ✅ | ✅ | ✅ | ❌ |
+| @SECA | ✅ | ✅ | ✅ | ❌ |
+| @SA | ✅ | ✅ | ✅ | ❌ |
+| @UIUX | ✅ | ✅ | ✅ | ❌ |
+| @REPORTER | ✅ | ✅ | ✅ | ✅ |
+| @PM | ❌ | ✅ | ❌ | ❌ |
+| @PO | ❌ | ✅ | ❌ | ❌ |
+
+---
+
+## 📞 Support
+
+If you need help with auto-learning:
+- **What to capture:** Tag @REPORTER
+- **How to document:** Use template above
+- **Where to store:** Check category structure
+- **Quality issues:** Tag @REPORTER for review
+
+---
+
+#auto-learning #knowledge-base #continuous-improvement #project-intelligence
+

package/.agent/rules/ai-enforcement.md

@@ -0,0 +1,11 @@
+## ⚠️ AI AGENT ENFORCEMENT (MANDATORY)
+> **CRITICAL:** AI agents (Gemini, Claude, Cursor, etc.) MUST follow these rules BEFORE starting any task.
+### Pre-Task Requirements
+1. **Read Workflow File First** - When user types /command, READ .agent/workflows/[command].md before any action
+2. **Activate Appropriate Roles** - Check the Role Activation Matrix in GEMINI.md
+3. **Follow State Machine** - Run python tools/brain/brain_cli.py status to check current state  
+4. **Search Knowledge Base** - Before implementing, search .agent/knowledge-base/INDEX.md
+5. **Document Learnings** - After task completion, consider KB entry if solution was non-obvious
+### Violation = System Failure
+If an AI agent implements without following workflows, the brain system is NOT being used.
+---

package/.agent/rules/artifacts.md

@@ -1,58 +1,77 @@
----
-description: Artifact and Naming Conventions
----
-
-# Artifact & Naming Conventions
-
-## Artifact Naming Convention
-Use versioned names attached to the current Sprint:
-| Artifact | Owner |
-|----------|-------|
-| `Project-Plan-Sprint-[N]-v*.md` | PM |
-| `Product-Backlog-Sprint-[N]-v*.md` | PO |
-| `UIUX-Design-Spec-Sprint-[N]-v*.md` | UIUX |
-| `System-Design-Spec-Sprint-[N]-v*.md` | SA |
-| `Design-Verification-Report-Sprint-[N]-v*.md` | QA |
-| `Security-Review-Report-Sprint-[N]-v*.md` | SecA |
-| `Development-Log-Sprint-[N]-v*.md` | DEV |
-| `DevOps-Plan-and-Log-Sprint-[N]-v*.md` | DevOps |
-| `Test-Report-Sprint-[N]-v*.md` | TESTER |
-| `Phase-Report-Sprint-[N]-v*.md` | REPORTER |
-| `Master-Documentation.md` | REPORTER |
-| `Final-Project-Report.md` | REPORTER |
-| `Final-Approval-Report.md` | STAKEHOLDER |
-
-## ⚠️ CRITICAL LOCATION RULE
-ALL project artifacts MUST be created in the project workspace with organized structure based on **Sprint**:
-
-**Base Directory:** `docs/sprints/sprint-[N]/`
-
-| Category | Folder Path | Content Example | Owner |
-|----------|-------------|-----------------|-------|
-| Plans | `docs/sprints/sprint-[N]/plans/` | `Project-Plan-Sprint-[N]-v*.md`, `Product-Backlog-Sprint-[N]-v*.md` | PM, PO |
-| Designs | `docs/sprints/sprint-[N]/designs/` | `System-Design-Spec-Sprint-[N]-v*.md`, `UIUX-Design-Spec-Sprint-[N]-v*.md` | SA, UIUX |
-| Reviews | `docs/sprints/sprint-[N]/reviews/` | `Design-Verification-Report-Sprint-[N]-v*.md`, `Security-Review-Report-Sprint-[N]-v*.md` | QA, SecA |
-| Logs | `docs/sprints/sprint-[N]/logs/` | `Development-Log-Sprint-[N]-v*.md`, `DevOps-Plan-and-Log-Sprint-[N]-v*.md` | DEV, DevOps |
-| Tests | `docs/sprints/sprint-[N]/tests/` | `Test-Report-Sprint-[N]-v*.md` | TESTER |
-| Reports | `docs/sprints/sprint-[N]/reports/` | `Phase-Report-Sprint-[N]-v*.md` | REPORTER |
-| Global | `docs/global/reports/` | `Final-Project-Report.md`, `Final-Approval-Report.md` | REPORTER, STAKEHOLDER |
-| Global | `docs/global/` | `Master-Documentation.md` | REPORTER |
-
-**FORBIDDEN:** `.agent/` directory (reserved for instructions only)
-
-## Mandatory Documentation Tags
-Every action must be tagged with appropriate hashtags:
-
-| Category | Tags |
-|----------|------|
-| **Planning** | `#planning`, `#product-owner`, `#backlog` |
-| **Design** | `#designing`, `#uiux-design` |
-| **Verification** | `#verify-design`, `#security-review` |
-| **Development** | `#development`, `#devops` |
-| **Testing** | `#testing` |
-| **Bug Fixes** | `#fixbug-critical`, `#fixbug-high`, `#fixbug-medium`, `#fixbug-low` |
-| **Status** | `#blocked`, `#hotfix`, `#rollback` |
-| **Deployment** | `#deployed-staging`, `#deployed-production` |
-| **Research** | `#searching` |
-| **Reporting** | `#reporting`, `#stakeholder-review` |
-| **Knowledge** | `#knowledge-base`, `#lessons-learned` |
+---
+description: Artifact and Naming Conventions
+---
+# Artifact & Naming Conventions
+## ⚠️ DOCUMENTATION LOCATION RULE (PROJECT-SPECIFIC)
+Documentation MUST be located within each project's directory, NOT in the root docs/ folder (except for global guides).
+### Correct Structure
+`
+root/
+├── docs/ (Global System Docs ONLY)
+│   ├── ARCHITECTURE.md
+│   └── BRAIN-GUIDE.md
+│
+└── projects/
+    └── [project-name]/
+        └── docs/ (Project Specific Docs)
+            └── sprints/
+                └── sprint-[N]/
+                    ├── plans/
+                    ├── requirements/
+                    ├── designs/
+                    └── logs/
+`
+## Artifact Naming Convention
+Use versioned names attached to the current Sprint:
+| Artifact | Owner |
+|----------|-------|
+| Project-Plan-Sprint-[N]-v*.md | PM |
+| Product-Backlog-Sprint-[N]-v*.md | PO |
+| UIUX-Design-Spec-Sprint-[N]-v*.md | UIUX |
+| System-Design-Spec-Sprint-[N]-v*.md | SA |
+| Design-Verification-Report-Sprint-[N]-v*.md | QA |
+| Security-Review-Report-Sprint-[N]-v*.md | SecA |
+| Development-Log-Sprint-[N]-v*.md | DEV |
+| DevOps-Plan-and-Log-Sprint-[N]-v*.md | DevOps |
+| Test-Report-Sprint-[N]-v*.md | TESTER |
+| Phase-Report-Sprint-[N]-v*.md | REPORTER |
+| Master-Documentation.md | REPORTER |
+| Final-Project-Report.md | REPORTER |
+| Final-Approval-Report.md | STAKEHOLDER |
+## ⚠️ CRITICAL LOCATION RULE (SPRINT FOLDERS)
+ALL project artifacts MUST be created in the **PROJECT'S** workspace with organized structure based on **Sprint**:
+**Base Directory:** projects/[project-name]/docs/sprints/sprint-[N]/
+| Category | Folder Path | Content Example | Owner |
+|----------|-------------|-----------------|-------|
+| Plans | .../plans/ | Project-Plan-Sprint-[N]-v*.md, Product-Backlog-Sprint-[N]-v*.md | PM, PO |
+| Designs | .../designs/ | System-Design-Spec-Sprint-[N]-v*.md, UIUX-Design-Spec-Sprint-[N]-v*.md | SA, UIUX |
+| Reviews | .../reviews/ | Design-Verification-Report-Sprint-[N]-v*.md, Security-Review-Report-Sprint-[N]-v*.md | QA, SecA |
+| Logs | .../logs/ | Development-Log-Sprint-[N]-v*.md, DevOps-Plan-and-Log-Sprint-[N]-v*.md | DEV, DevOps |
+| Tests | .../tests/ | Test-Report-Sprint-[N]-v*.md | TESTER |
+| Reports | .../reports/ | Phase-Report-Sprint-[N]-v*.md | REPORTER |
+| Global | .../global/reports/ | Final-Project-Report.md, Final-Approval-Report.md | REPORTER, STAKEHOLDER |
+| Global | projects/[project-name]/docs/global/ | Master-Documentation.md | REPORTER |
+**FORBIDDEN LOCATIONS:**
+- .agent/ directory (reserved for instructions only)
+- Global docs/ folder for project-specific artifacts.
+## ⚠️ CHANGELOG RULE
+**CRITICAL:** Do NOT create or update CHANGELOG.md in the project root.
+- CHANGELOG.md exists ONLY as a template in .agent/templates/
+- All project changes are documented in sprint-specific reports
+- Use Phase-Report-Sprint-[N]-v*.md for sprint summaries
+- Use Final-Project-Report.md for overall project changelog
+## Mandatory Documentation Tags
+Every action must be tagged with appropriate hashtags:
+| Category | Tags |
+|----------|------|
+| **Planning** | #planning, #product-owner, #backlog |
+| **Design** | #designing, #uiux-design |
+| **Verification** | #verify-design, #security-review |
+| **Development** | #development, #devops |
+| **Testing** | #testing |
+| **Bug Fixes** | #fixbug-critical, #fixbug-high, #fixbug-medium, #fixbug-low |
+| **Status** | #blocked, #hotfix, #rollback |
+| **Deployment** | #deployed-staging, #deployed-production |
+| **Research** | #searching |
+| **Reporting** | #reporting, #stakeholder-review |
+| **Knowledge** | #knowledge-base, #lessons-learned |

package/.agent/rules/git-workflow.md

@@ -1,65 +1,25 @@
----
-description: Unified Git and Task Workflow
----
-
-# Git & Task Management Workflow
-
-**Requirement:** All tasks must be tracked with Jira-like precision and committed atomically.
-
-## A. Task Board Logic
-- All `Product-Backlog` items (User Stories) must be broken down into **Tasks** in the `Development-Log`.
-- **Status Columns:** `Todo` | `In Progress` | `Review` | `Done`.
-- **Assignal:** Every task must have an owner (e.g., `@DEV`, `@SA`).
-- **Tracing:** Every completed task must link to a **Git Commit Hash**.
-
-## B. Atomic Commit Rule
-- ⚠️ **DO NOT** commit all changes at once at the end of a sprint.
-- **Workflow:**
-  1. Pick a task from `Development-Log` (Mark as `In Progress`)
-  2. Implement the code
-  3. Verify locally
-  4. **COMMIT IMMEDIATELY:** `git commit -m "[Task-ID] <Description>"`
-  5. Update `Development-Log` (Mark as `Done` and add Commit Hash)
-- This ensures a clean, traceable history and prevents "big bang" integration issues.
-
-## C. Definition of Done (DoD)
-A feature/task is "Done" when ALL of the following are true:
-
-### For Development Tasks:
-- [ ] Code implemented according to approved design specs
-- [ ] Code follows project coding standards
-- [ ] Local testing passed
-- [ ] Evidence captured (screenshots/logs)
-- [ ] Tagged with `#development`
-- [ ] **Git Commit created and linked in Log**
-- [ ] Handoff to TESTER completed
-
-### For Testing:
-- [ ] All test cases executed
-- [ ] No critical/high bugs open
-- [ ] Evidence documented in Test-Report
-- [ ] Tagged with `#testing`
-
-### For Deployment:
-- [ ] CI/CD pipeline passing
-- [ ] Staging environment verified
-- [ ] Security checklist completed
-- [ ] Tagged with `#deployed-staging` or `#deployed-production`
-
-### For Project Completion:
-- [ ] All Must-Have features verified
-- [ ] STAKEHOLDER approved
-- [ ] Final documentation complete
-- [ ] User notified
-
-## D. Automated Changelog Updates
-- **Requirement:** Every commit MUST be followed by an update to CHANGELOG.md.
-- **Format:**
-  ```markdown
-  - [YYYY-MM-DD] [Commit-Hash] [Type]: [Description] (@Author)
-  ```
-- **Types:** Feature, Fix, Refactor, Docs, Chore, Test.
-
-## E. Release Summary Generation
-- **Requirement:** After a feature is marked as 'Done' in the board or a 'Release' is triggered, the @REPORTER or @DEV MUST update the CHANGELOG.md with a summary of the version release.
-- **Action:** Consolidate all atomic commits into a cohesive release entry.
+---
+description: Unified Git and Task Workflow (Branching, Committing, Merging)
+---
+# Git & Task Management Workflow
+**Requirement:** All tasks and artifacts must follow the **Branch-Based Workflow**.
+## A. Branching Strategy (MANDATORY)
+❌ **NEVER** commit directly to main or master.
+### Branch Naming Convention
+| Type | Prefix | Use Case |
+|------|--------|----------|
+| **Planning** | plan/ | Project plans, product backlogs |
+| **Design** | design/ | Architecture schematics, UI specs |
+| **Feature** | eat/ | New functionality |
+| **Fix** | ix/ | Bug fixes |
+| **Docs** | docs/ | General documentation |
+**Format:** prefix/TASK-ID-short-name (e.g., plan/SPRINT-2-setup)
+### Workflow
+1. **Start:** git checkout -b prefix/TASK-ID-name from main.
+2. **Work:** Create artifacts or code.
+3. **Push:** git push -u origin prefix/TASK-ID-name.
+4. **Docs-as-Code:** Treat documentation exactly like code.
+## B. Definition of Done (DoD)
+1. Branch created.
+2. Artifacts implemented.
+3. Pull Request created & merged.