agentic-sdlc 1.0.0

package/.agent/rules/artifacts.md

@@ -0,0 +1,58 @@
+---
+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` |

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

@@ -0,0 +1,65 @@
+---
+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.

package/.agent/rules/global.md

@@ -0,0 +1,154 @@
+# TeamLifecycle Global Rules & Conventions
+(Version 1.4 – Strict IT SDLC Simulation for Google Antigravity)
+
+**Last Updated:** 2026-01-01  
+**Maintainer:** Project Team
+
+---
+
+## Purpose
+This document defines the mandatory rules, conventions, and lifecycle flow that EVERY agent in the TeamLifecycle workflow MUST follow without exception.  
+ It ensures strict compliance, full traceability, auto-communication, and professional software development process.
+
+---
+
+## Strict SDLC Flow (NO SKIPPING PHASES – EVER)
+
+```
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 1. Planning     │───▶│ 2. Plan Approval│───▶│ 3. Designing            │
+│    (PM)         │    │    (User)       │    │    (SA + UIUX + PO)     │
+└─────────────────┘    └─────────────────┘    └───────────┬─────────────┘
+                                                          │
+                                                          ▼
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 6. Testing      │◀───│ 5. Development  │◀───│ 4. Design Verification  │
+│    (TESTER)     │    │   (DEV + Ops)   │    │    (QA + SecA)          │
+└────────┬────────┘    └─────────────────┘    └─────────────────────────┘
+         │
+         ▼
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 7. Bug Fixing   │───▶│ 8. Deployment   │───▶│ 9. Reporting            │
+│   (DEV + Ops)   │    │    (DevOps)     │    │    (REPORTER)           │
+└─────────────────┘    └─────────────────┘    └───────────┬─────────────┘
+                                                          │
+                                                          ▼
+                       ┌─────────────────┐    ┌─────────────────────────┐
+                       │ ↩ Cycle Repeat  │◀───│ 10. Final Review        │
+                       │   (if rejected) │    │    (STAKEHOLDER)        │
+                       └─────────────────┘    └───────────┬─────────────┘
+                                                          │ ✅ Approved
+                                                          ▼
+                                              ┌─────────────────────────┐
+                                              │ 11. Completion          │
+                                              └─────────────────────────┘
+```
+
+### Phase Details:
+1. **Planning** (PM) – Gather requirements, create project plan
+2. **Plan Approval** (User) – Explicit user sign-off required
+3. **Designing** (SA + UIUX + PO in parallel) – Architecture, UI/UX, backlog prioritization
+4. **Design Verification** (QA + SecA in parallel) – Quality and security review
+5. **Development** (DEV + DevOps in parallel) – Implementation
+6. **Testing** (TESTER) – Functional, integration, E2E testing
+7. **Bug Fixing** (DEVs + DevOps) – Address identified issues
+8. **Deployment Prep** (DevOps) – CI/CD, staging, production readiness
+9. **Reporting & Documentation** (REPORTER) – Update CHANGELOG.md and create comprehensive reports
+10. **Final Review** (STAKEHOLDER) – Business approval
+11. **Repeat Cycle** (if needed) or **Completion**
+
+---
+
+## Cross-Role Dependencies
+
+(See Role Descriptions for specific handoffs)
+
+---
+
+## Specialized Rule Sets
+
+**You MUST refer to these additional rule files for specific domains:**
+
+1. **Artifacts & Naming:** `.agent/rules/artifacts.md`
+   - Covers: Naming conventions, folder structure, forbidden locations.
+2. **Git & Task Workflow:** `.agent/rules/git-workflow.md`
+   - Covers: Jira-style task tracking, atomic commits, Definition of Done.
+3. **Knowledge Base:** `.agent/rules/knowledge-base.md`
+   - Covers: When and how to create knowledge entries.
+
+---
+
+## Core Rules Every Agent MUST Obey
+
+### 1. Approval Gates
+Critical phases require explicit approval:
+| Gate | Approver | Artifact |
+|------|----------|----------|
+| Project Plan | User | Project-Plan-v*.md |
+| Design | QA + SecA | Design-Verification-Report, Security-Review-Report |
+| Final Delivery | STAKEHOLDER | Final-Approval-Report.md |
+
+### 2. Auto-Communication via @Tags
+Always use @role tags to notify next agents.
+- **Available roles:** @ORCHESTRATOR, @PM, @PO, @SA, @UIUX, @QA, @SECA, @DEV, @DEVOPS, @TESTER, @REPORTER, @STAKEHOLDER
+- Example: `### Next Step: @SA - Start designing` or `@TESTER - Please test`
+- **Orchestrator mode:** Add `--mode=full-auto` or `--mode=semi-auto` to enable automation
+
+### 3. No Scope Creep
+- No new features or changes outside approved Project Plan
+- Any change requires PM + PO to revise plan and get user re-approval
+
+### 4. Bug Priority Classification
+| Priority | Tag | Criteria |
+|----------|-----|----------|
+| **Critical** | `#fixbug-critical` | Breaks core functionality, data loss, security exploit |
+| **High** | `#fixbug-high` | Major feature broken, serious UX issue |
+| **Medium** | `#fixbug-medium` | Works but with wrong behavior or poor UX |
+| **Low** | `#fixbug-low` | Cosmetic, minor inconsistency |
+
+### 5. Cycle Repeat Triggers
+Handled by REPORTER or STAKEHOLDER when:
+- ❌ Unresolved critical/high bugs
+- ❌ Rejected design or security review
+- ❌ Stakeholder rejection
+- ❌ Incomplete requirements coverage
+
+**Action:** Tag `@PM` with reason → PM engages user → New plan version
+
+### 6. Transparency & Evidence
+- Use screenshots, recordings, or browser artifacts for proof
+- All agents must produce verifiable artifacts (logs, reports, diagrams)
+
+### 7. Global Handoff Template
+
+Use this at the end of **every artifact**:
+
+```markdown
+### Next Step:
+- [List of @tags and actions]
+- [Clear status: ready for next phase / awaiting approval / cycle repeat]
+
+#[appropriate-tags]
+```
+
+---
+
+## Final Note
+
+> ⚠️ **ALL AGENTS MUST STRICTLY ADHERE TO THESE RULES.**  
+> Any deviation will break the workflow.  
+> If unsure, tag `@PM` for clarification.
+
+#global-rules #reporting
+
+---
+
+## Changelog
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.4 | 2026-01-01 | Split large rules into artifacts.md, git-workflow.md, knowledge-base.md |
+| 1.3 | 2026-01-01 | Added Task Management & Atomic Git Commit Rules |
+| 1.2 | 2026-01-01 | Migrated to Native Agent structure (.agent/). Updated paths. |
+| 1.1 | 2025-12-23 | Added PO role, new tags (#product-owner, #backlog, #blocked, #hotfix, #rollback, #deployed-*), Definition of Done, Cross-Role Dependencies diagram, Incident/Hotfix workflow, Changelog |
+| 1.0 | Initial | Initial release with 10 roles and core SDLC flow |

package/.agent/rules/global.md.bak

@@ -0,0 +1,154 @@
+# TeamLifecycle Global Rules & Conventions
+(Version 1.4 – Strict IT SDLC Simulation for Google Antigravity)
+
+**Last Updated:** 2025-12-31  
+**Maintainer:** Project Team
+
+---
+
+## Purpose
+This document defines the mandatory rules, conventions, and lifecycle flow that EVERY agent in the TeamLifecycle workflow MUST follow without exception.  
+ It ensures strict compliance, full traceability, auto-communication, and professional software development process.
+
+---
+
+## Strict SDLC Flow (NO SKIPPING PHASES – EVER)
+
+```
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 1. Planning     │───▶│ 2. Plan Approval│───▶│ 3. Designing            │
+│    (PM)         │    │    (User)       │    │    (SA + UIUX + PO)     │
+└─────────────────┘    └─────────────────┘    └───────────┬─────────────┘
+                                                          │
+                                                          ▼
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 6. Testing      │◀───│ 5. Development  │◀───│ 4. Design Verification  │
+│    (TESTER)     │    │   (DEV + Ops)   │    │    (QA + SecA)          │
+└────────┬────────┘    └─────────────────┘    └─────────────────────────┘
+         │
+         ▼
+┌─────────────────┐    ┌─────────────────┐    ┌─────────────────────────┐
+│ 7. Bug Fixing   │───▶│ 8. Deployment   │───▶│ 9. Reporting            │
+│   (DEV + Ops)   │    │    (DevOps)     │    │    (REPORTER)           │
+└─────────────────┘    └─────────────────┘    └───────────┬─────────────┘
+                                                          │
+                                                          ▼
+                       ┌─────────────────┐    ┌─────────────────────────┐
+                       │ ↩ Cycle Repeat  │◀───│ 10. Final Review        │
+                       │   (if rejected) │    │    (STAKEHOLDER)        │
+                       └─────────────────┘    └───────────┬─────────────┘
+                                                          │ ✅ Approved
+                                                          ▼
+                                              ┌─────────────────────────┐
+                                              │ 11. Completion          │
+                                              └─────────────────────────┘
+```
+
+### Phase Details:
+1. **Planning** (PM) – Gather requirements, create project plan
+2. **Plan Approval** (User) – Explicit user sign-off required
+3. **Designing** (SA + UIUX + PO in parallel) – Architecture, UI/UX, backlog prioritization
+4. **Design Verification** (QA + SecA in parallel) – Quality and security review
+5. **Development** (DEV + DevOps in parallel) – Implementation
+6. **Testing** (TESTER) – Functional, integration, E2E testing
+7. **Bug Fixing** (DEVs + DevOps) – Address identified issues
+8. **Deployment Prep** (DevOps) – CI/CD, staging, production readiness
+9. **Reporting & Documentation** (REPORTER) – Update CHANGELOG.md and create comprehensive reports
+10. **Final Review** (STAKEHOLDER) – Business approval
+11. **Repeat Cycle** (if needed) or **Completion**
+
+---
+
+## Cross-Role Dependencies
+
+(See Role Descriptions for specific handoffs)
+
+---
+
+## Specialized Rule Sets
+
+**You MUST refer to these additional rule files for specific domains:**
+
+1. **Artifacts & Naming:** `d:\dev\template-intructions\.agent\rules\artifacts.md`
+   - Covers: Naming conventions, folder structure, forbidden locations.
+2. **Git & Task Workflow:** `d:\dev\template-intructions\.agent\rules\git-workflow.md`
+   - Covers: Jira-style task tracking, atomic commits, Definition of Done.
+3. **Knowledge Base:** `d:\dev\template-intructions\.agent\rules\knowledge-base.md`
+   - Covers: When and how to create knowledge entries.
+
+---
+
+## Core Rules Every Agent MUST Obey
+
+### 1. Approval Gates
+Critical phases require explicit approval:
+| Gate | Approver | Artifact |
+|------|----------|----------|
+| Project Plan | User | Project-Plan-v*.md |
+| Design | QA + SecA | Design-Verification-Report, Security-Review-Report |
+| Final Delivery | STAKEHOLDER | Final-Approval-Report.md |
+
+### 2. Auto-Communication via @Tags
+Always use @role tags to notify next agents.
+- **Available roles:** @ORCHESTRATOR, @PM, @PO, @SA, @UIUX, @QA, @SECA, @DEV, @DEVOPS, @TESTER, @REPORTER, @STAKEHOLDER
+- Example: `### Next Step: @SA - Start designing` or `@TESTER - Please test`
+- **Orchestrator mode:** Add `--mode=full-auto` or `--mode=semi-auto` to enable automation
+
+### 3. No Scope Creep
+- No new features or changes outside approved Project Plan
+- Any change requires PM + PO to revise plan and get user re-approval
+
+### 4. Bug Priority Classification
+| Priority | Tag | Criteria |
+|----------|-----|----------|
+| **Critical** | `#fixbug-critical` | Breaks core functionality, data loss, security exploit |
+| **High** | `#fixbug-high` | Major feature broken, serious UX issue |
+| **Medium** | `#fixbug-medium` | Works but with wrong behavior or poor UX |
+| **Low** | `#fixbug-low` | Cosmetic, minor inconsistency |
+
+### 5. Cycle Repeat Triggers
+Handled by REPORTER or STAKEHOLDER when:
+- ❌ Unresolved critical/high bugs
+- ❌ Rejected design or security review
+- ❌ Stakeholder rejection
+- ❌ Incomplete requirements coverage
+
+**Action:** Tag `@PM` with reason → PM engages user → New plan version
+
+### 6. Transparency & Evidence
+- Use screenshots, recordings, or browser artifacts for proof
+- All agents must produce verifiable artifacts (logs, reports, diagrams)
+
+### 7. Global Handoff Template
+
+Use this at the end of **every artifact**:
+
+```markdown
+### Next Step:
+- [List of @tags and actions]
+- [Clear status: ready for next phase / awaiting approval / cycle repeat]
+
+#[appropriate-tags]
+```
+
+---
+
+## Final Note
+
+> ⚠️ **ALL AGENTS MUST STRICTLY ADHERE TO THESE RULES.**  
+> Any deviation will break the workflow.  
+> If unsure, tag `@PM` for clarification.
+
+#global-rules #reporting
+
+---
+
+## Changelog
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.4 | 2025-12-31 | Split large rules into artifacts.md, git-workflow.md, knowledge-base.md |
+| 1.3 | 2025-12-31 | Added Task Management & Atomic Git Commit Rules |
+| 1.2 | 2025-12-31 | Migrated to Native Agent structure (.agent/). Updated paths. |
+| 1.1 | 2025-12-23 | Added PO role, new tags (#product-owner, #backlog, #blocked, #hotfix, #rollback, #deployed-*), Definition of Done, Cross-Role Dependencies diagram, Incident/Hotfix workflow, Changelog |
+| 1.0 | Initial | Initial release with 10 roles and core SDLC flow |

package/.agent/rules/knowledge-base.md

@@ -0,0 +1,45 @@
+---
+description: Knowledge Base System Rules
+---
+
+# Knowledge Base System Rules
+
+## Purpose
+The Knowledge Base stores lessons learned, bug patterns, difficult features, and solutions that required multiple attempts. This serves as project memory for future reference.
+
+## When to Create Entry
+Create a knowledge entry when:
+- Bug required 3+ attempts to fix
+- Feature implementation was particularly challenging
+- Solution was non-obvious or counter-intuitive
+- Issue is likely to recur in similar projects
+- Root cause analysis revealed important insights
+
+## Entry Naming
+**Format:** `KB-[YYYY-MM-DD]-[###]-[short-title].md`
+
+**Location:** `.agent/knowledge-base/[category]/[severity]/`
+
+## Categories
+| Category | Folder | Description |
+|----------|--------|-------------|
+| Bugs | `knowledge-base/bugs/[severity]/` | Bug patterns and fixes |
+| Features | `knowledge-base/features/[type]/` | Complex feature implementations |
+| Architecture | `knowledge-base/architecture/` | Architecture decisions |
+| Security | `knowledge-base/security/` | Security issues and solutions |
+| Performance | `knowledge-base/performance/` | Performance optimizations |
+| Platform | `knowledge-base/platform-specific/[platform]/` | Platform-specific issues |
+
+## Workflow
+1. **Create Entry:** Use `Knowledge-Entry-Template.md`
+2. **Document:** Include problem, root cause, solution, prevention
+3. **Tag:** Add appropriate tags for searchability
+4. **Update Index:** Add to `knowledge-base/index.md`
+5. **Notify:** Tag @REPORTER for review
+
+## Search Before Starting
+Before implementing complex features or fixing bugs:
+1. Check `knowledge-base/index.md`
+2. Search by keywords, technology, or error messages
+3. Review similar entries
+4. Adapt solutions to current context

package/.agent/templates/Design-Verification-Report-Template.md

@@ -0,0 +1,67 @@
+# Design Verification Report - Version [X]
+
+## Document Info
+| Field | Value |
+|-------|-------|
+| Version | [X.0] |
+| Date | [YYYY-MM-DD] |
+| Author | @QA |
+| Status | Pass / Fail / Conditional Pass |
+
+---
+
+## 1. Documents Reviewed
+| Document | Version | Date Reviewed |
+|----------|---------|---------------|
+| Backend-Design-Spec | v[X] | [Date] |
+| UIUX-Design-Spec | v[X] | [Date] |
+| Project-Plan | v[X] | [Date] |
+
+## 2. Verification Summary
+| Category | Status | Issues |
+|----------|--------|--------|
+| Completeness | ✅/⚠️/❌ | [Count] |
+| Consistency | ✅/⚠️/❌ | [Count] |
+| Testability | ✅/⚠️/❌ | [Count] |
+| Requirements Coverage | ✅/⚠️/❌ | [Count] |
+
+## 3. Detailed Findings
+
+### 3.1 Completeness
+| ID | Finding | Severity | Status |
+|----|---------|----------|--------|
+| QA-001 | [Finding description] | High/Med/Low | Open/Resolved |
+
+### 3.2 Consistency
+| ID | Finding | Severity | Status |
+|----|---------|----------|--------|
+| QA-002 | [Finding description] | High/Med/Low | Open/Resolved |
+
+### 3.3 Testability
+| ID | Finding | Severity | Status |
+|----|---------|----------|--------|
+| QA-003 | [Finding description] | High/Med/Low | Open/Resolved |
+
+## 4. Requirements Traceability
+| Requirement | Design Reference | Covered |
+|-------------|------------------|---------|
+| [REQ-001] | Backend-Design 3.1 | ✅/❌ |
+| [REQ-002] | UIUX-Design 3.2 | ✅/❌ |
+
+## 5. Recommendations
+1. [Recommendation 1]
+2. [Recommendation 2]
+
+## 6. Verdict
+☐ **PASS** - Design approved for development
+☐ **CONDITIONAL PASS** - Proceed with noted conditions
+☐ **FAIL** - Design requires revision before development
+
+---
+
+### Next Step:
+- @SA @UIUX - Address findings (if any)
+- @DEV - Begin development (if approved)
+- @SECA - Complete security review
+
+#verify-design

package/.agent/templates/DevOps-Plan-Template.md

@@ -0,0 +1,90 @@
+# DevOps Plan and Log - Version [X]
+
+## Document Info
+| Field | Value |
+|-------|-------|
+| Version | [X.0] |
+| Date | [YYYY-MM-DD] |
+| Author | @DEVOPS |
+| Status | Draft / Active |
+
+---
+
+## 1. Infrastructure Overview
+
+```
+┌─────────────────────────────────────────────────────────┐
+│                    Production                            │
+│  ┌──────────┐    ┌──────────┐    ┌──────────┐          │
+│  │   CDN    │───▶│   App    │───▶│    DB    │          │
+│  └──────────┘    └──────────┘    └──────────┘          │
+└─────────────────────────────────────────────────────────┘
+```
+
+## 2. Environments
+| Environment | URL | Purpose |
+|-------------|-----|---------|
+| Development | localhost:5173 | Local development |
+| Staging | [staging-url] | Pre-production testing |
+| Production | [prod-url] | Live environment |
+
+## 3. CI/CD Pipeline
+
+```
+┌────────┐    ┌────────┐    ┌────────┐    ┌────────┐
+│  Push  │───▶│  Build │───▶│  Test  │───▶│ Deploy │
+└────────┘    └────────┘    └────────┘    └────────┘
+```
+
+### Pipeline Stages
+| Stage | Tool | Duration | Status |
+|-------|------|----------|--------|
+| Build | [Tool] | ~[X]min | ✅/❌ |
+| Test | [Tool] | ~[X]min | ✅/❌ |
+| Deploy Staging | [Tool] | ~[X]min | ✅/❌ |
+| Deploy Prod | [Tool] | ~[X]min | ✅/❌ |
+
+## 4. Deployment Checklist
+
+### Pre-Deployment
+- [ ] All tests passing
+- [ ] Security review approved
+- [ ] Environment variables configured
+- [ ] Database migrations ready
+- [ ] Rollback plan documented
+
+### Post-Deployment
+- [ ] Health check passing
+- [ ] Smoke tests completed
+- [ ] Monitoring alerts active
+- [ ] Documentation updated
+
+## 5. Environment Variables
+| Variable | Staging | Production | Notes |
+|----------|---------|------------|-------|
+| [VAR_NAME] | [Value] | [Value] | [Notes] |
+
+## 6. Monitoring & Alerts
+| Metric | Threshold | Alert Channel |
+|--------|-----------|---------------|
+| Error Rate | > 1% | [Slack/Email] |
+| Response Time | > 2s | [Slack/Email] |
+| Uptime | < 99.9% | [Slack/Email] |
+
+## 7. Deployment Log
+
+### [Date] - v[X.X.X]
+| Field | Value |
+|-------|-------|
+| Environment | Staging / Production |
+| Status | ✅ Success / ❌ Failed |
+| Duration | [X minutes] |
+| Changes | [Brief description] |
+
+---
+
+### Next Step:
+- @TESTER - Staging environment ready for testing
+- @REPORTER - Deployment documentation complete
+
+#devops #deployed-staging

package/.agent/templates/Development-Log-Template.md

@@ -0,0 +1,51 @@
+# Development Log & Sprint Board - Version [X]
+
+## Document Info
+| Field | Value |
+|-------|-------|
+| Version | [X.0] |
+| Date | [YYYY-MM-DD] |
+| Author | @DEV |
+| Sprint | [Sprint #] |
+
+---
+
+## 1. Sprint Board (Jira-Style)
+
+| ID | Task Description | Assignee | Status | Commit Hash |
+|----|------------------|----------|--------|-------------|
+| T-001 | [Implement Login Page] | @DEV1 | ✅ Done | `a1b2c3d` |
+| T-002 | [Design Database Schema] | @SA | ✅ Done | `d4e5f6g` |
+| T-003 | [Setup API Routes] | @DEV2 | 🔄 In Progress | - |
+| T-004 | [Unit Tests for Auth] | @DEV1 | 📝 Todo | - |
+
+---
+
+## 2. Detailed Implementation Notes
+
+### [T-001] Implement Login Page
+**Status:** ✅ Done
+**Commit:** `a1b2c3d`
+**Notes:**
+- Used template from UIUX spec
+- Validated input fields with Zod
+
+### [T-003] Setup API Routes
+**Status:** 🔄 In Progress
+**Notes:**
+- Currently debugging middleware issue
+
+---
+
+## 3. Blockers & Issues
+| ID | Description | Status | Action |
+|----|-------------|--------|--------|
+| BLK-001 | [Blocker description] | Open/Resolved | @[ROLE] to assist |
+
+---
+
+### Next Step:
+- @TESTER - Items ready for testing: [T-001, T-002]
+- @DEVOPS - Ready for staging deployment
+
+#development