Initial implementation

This commit is contained in:
Renn F
2025-12-10 02:49:54 +01:00
parent 209aa346ab
commit 0c5dac4d16
118 changed files with 38912 additions and 2 deletions
+50
View File
@@ -0,0 +1,50 @@
# Initiatives
Initiatives are large, cross-cell efforts that span multiple tasks. They represent features or projects that require coordination between Backend, Frontend, and/or UX/UI cells.
## Directory Structure
```
initiatives/
├── README.md # This file
├── {initiative-slug}/
│ ├── README.md # Initiative overview
│ ├── requirements.md # Detailed requirements from Product Owner
│ ├── tasks.md # Task breakdown by cell
│ ├── timeline.md # Milestones and deadlines
│ ├── decisions.md # Cross-cell decisions
│ └── status.md # Current status (updated frequently)
```
## Initiative Lifecycle
```
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Proposed │────►│ Planning │────►│ Active │────►│ Completed │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
│ │
▼ ▼
┌──────────────┐ ┌──────────────┐
│ Blocked │ │ On Hold │
└──────────────┘ └──────────────┘
```
## Creating an Initiative
1. Product Owner or Main PM creates initiative directory
2. Fill in README.md with overview
3. Define requirements in requirements.md
4. Break down tasks by cell in tasks.md
5. Set timeline and milestones in timeline.md
6. Create individual tasks in `.tasks/active/`
7. Link tasks back to initiative
## Initiative Naming
`{descriptive-slug}` - Use kebab-case, max 40 characters
Examples:
- `user-preferences`
- `dashboard-redesign`
- `auth-system-overhaul`
- `mobile-app-v2`
+108
View File
@@ -0,0 +1,108 @@
# Initiative: {Name}
> **Created**: YYYY-MM-DD
> **Owner**: {Product Owner / Main PM}
> **Status**: {proposed / planning / active / blocked / on_hold / completed}
---
## Overview
{What is this initiative? Why does it matter? 2-3 paragraphs.}
## Goals
1. {Primary goal}
2. {Secondary goal}
3. {Tertiary goal}
## Success Metrics
| Metric | Current | Target | How Measured |
|--------|---------|--------|--------------|
| {metric} | {current} | {target} | {method} |
| {metric} | {current} | {target} | {method} |
## Scope
### In Scope
- {What's included}
- {What's included}
### Out of Scope
- {What's explicitly NOT included}
- {What's explicitly NOT included}
---
## Cells Involved
| Cell | Scope | Lead | Status |
|------|-------|------|--------|
| UX/UI | {brief scope} | UX-PM | {status} |
| Backend | {brief scope} | BE-PM | {status} |
| Frontend | {brief scope} | FE-PM | {status} |
## Task Summary
See [tasks.md](tasks.md) for full breakdown.
| Cell | Total Tasks | Completed | In Progress | Blocked |
|------|-------------|-----------|-------------|---------|
| UX/UI | 0 | 0 | 0 | 0 |
| Backend | 0 | 0 | 0 | 0 |
| Frontend | 0 | 0 | 0 | 0 |
---
## Timeline
See [timeline.md](timeline.md) for details.
| Milestone | Target | Actual | Status |
|-----------|--------|--------|--------|
| Design Complete | YYYY-MM-DD | - | pending |
| Backend API Ready | YYYY-MM-DD | - | pending |
| Frontend Complete | YYYY-MM-DD | - | pending |
| QA Complete | YYYY-MM-DD | - | pending |
| Launch | YYYY-MM-DD | - | pending |
---
## Current Status
**Last Updated**: YYYY-MM-DD
{2-3 sentences on current state}
### This Week
- {What happened}
- {What happened}
### Next Week
- {What's planned}
- {What's planned}
### Blockers
- {Current blockers or "None"}
### Risks
- {Active risks or "None identified"}
---
## Quick Links
- [Requirements](requirements.md)
- [Tasks](tasks.md)
- [Timeline](timeline.md)
- [Decisions](decisions.md)
- [Status Updates](status.md)
---
## Related
- **Depends on**: {initiative or "none"}
- **Blocks**: {initiative or "none"}
- **Related**: {initiative or "none"}
+101
View File
@@ -0,0 +1,101 @@
# Decisions: {Initiative Name}
Log of significant decisions made during this initiative.
> **Last Updated**: YYYY-MM-DD
---
## Decision Log
### DEC-001: {Decision Title}
**Date**: YYYY-MM-DD
**Decider**: {agent-id or role}
**Status**: {proposed / accepted / superseded / rejected}
#### Context
{What situation required a decision?}
#### Options Considered
**Option A: {Name}**
- Description: {what this option entails}
- Pros:
- {Pro 1}
- {Pro 2}
- Cons:
- {Con 1}
- {Con 2}
- Effort: {low / medium / high}
**Option B: {Name}**
- Description: {what this option entails}
- Pros:
- {Pro 1}
- {Pro 2}
- Cons:
- {Con 1}
- {Con 2}
- Effort: {low / medium / high}
#### Decision
**Chose Option {X}**: {Brief statement of decision}
#### Rationale
{Why this option was chosen}
#### Consequences
- {Consequence 1 - what this means going forward}
- {Consequence 2 - what needs to happen as a result}
- {Consequence 3 - what we're accepting/trading off}
#### Related
- Tasks affected: TASK-XXX, TASK-XXX
- Supersedes: DEC-XXX (if applicable)
---
### DEC-002: {Decision Title}
**Date**: YYYY-MM-DD
**Decider**: {agent-id or role}
**Status**: {proposed / accepted / superseded / rejected}
#### Context
{What situation required a decision?}
#### Options Considered
{...}
#### Decision
{...}
#### Rationale
{...}
#### Consequences
{...}
---
## Pending Decisions
| ID | Topic | Owner | Needed By | Blockers |
|----|-------|-------|-----------|----------|
| DEC-XXX | {topic} | {owner} | YYYY-MM-DD | {what it blocks} |
---
## Decision Index
| ID | Title | Date | Status | Quick Reference |
|----|-------|------|--------|-----------------|
| DEC-001 | {title} | YYYY-MM-DD | {status} | {one-line summary} |
| DEC-002 | {title} | YYYY-MM-DD | {status} | {one-line summary} |
---
## Notes
{Any additional context about decision-making process, stakeholders involved, etc.}
@@ -0,0 +1,149 @@
# Requirements: {Initiative Name}
> **Author**: Product Owner
> **Version**: 1.0
> **Last Updated**: YYYY-MM-DD
---
## Business Context
{Why is this initiative important? What business problem does it solve?}
## User Problem
{What user problem does this solve? Who are the users?}
### User Personas
**Persona 1: {Name}**
- Role: {description}
- Needs: {what they need}
- Pain Points: {current frustrations}
---
## Functional Requirements
### FR-1: {Requirement Title}
**Priority**: {must-have / should-have / nice-to-have}
**Description**: {Detailed description}
**Acceptance Criteria**:
- [ ] {Criterion 1}
- [ ] {Criterion 2}
- [ ] {Criterion 3}
**Notes**: {Additional context}
---
### FR-2: {Requirement Title}
**Priority**: {must-have / should-have / nice-to-have}
**Description**: {Detailed description}
**Acceptance Criteria**:
- [ ] {Criterion 1}
- [ ] {Criterion 2}
---
## Non-Functional Requirements
### Performance
- {Performance requirement}
### Security
- {Security requirement}
### Accessibility
- {Accessibility requirement}
### Compatibility
- {Browser/device compatibility}
---
## User Flows
### Flow 1: {Name}
```
[User Action] → [System Response] → [User Action] → [System Response]
```
**Steps**:
1. User {action}
2. System {response}
3. User {action}
4. System {response}
**Success State**: {what success looks like}
**Error States**:
- {Error scenario 1}: {handling}
- {Error scenario 2}: {handling}
---
## Data Requirements
### Data Entities
| Entity | Description | Source |
|--------|-------------|--------|
| {entity} | {description} | {where it comes from} |
### Data Rules
- {Rule 1}
- {Rule 2}
---
## Integration Requirements
### External Systems
| System | Integration Type | Purpose |
|--------|-----------------|---------|
| {system} | {API / webhook / etc.} | {purpose} |
---
## Constraints
- {Technical constraint}
- {Business constraint}
- {Timeline constraint}
- {Budget constraint}
---
## Assumptions
- {Assumption 1}
- {Assumption 2}
---
## Open Questions
- [ ] {Question 1}
- [ ] {Question 2}
---
## Appendix
### Wireframes/Mockups
{Links to design references}
### Reference Documents
{Links to related documents}
### Glossary
| Term | Definition |
|------|------------|
| {term} | {definition} |
+81
View File
@@ -0,0 +1,81 @@
# Status Updates: {Initiative Name}
Running log of status updates for stakeholder visibility.
---
## Latest Status
**Date**: YYYY-MM-DD
**Overall**: {on_track / at_risk / blocked / delayed} {emoji: 🟢 / 🟡 / 🔴}
**Progress**: X%
### Summary
{2-3 sentence summary of current state}
### Completed This Period
- {What was completed}
- {What was completed}
### In Progress
- {What's actively being worked on}
- {What's actively being worked on}
### Upcoming
- {What's next}
- {What's next}
### Blockers
- {Active blockers or "None"}
### Risks
- {Active risks or "None"}
### Decisions Needed
- {Decisions needed or "None"}
---
## Status History
### YYYY-MM-DD
**Status**: {status} {emoji}
**Progress**: X%
{Summary of status at this point}
- Completed: {items}
- Blockers: {items or "None"}
- Notes: {any notes}
---
### YYYY-MM-DD
**Status**: {status} {emoji}
**Progress**: X%
{Summary}
---
## Metrics Over Time
| Date | Progress | Tasks Done | Tasks Total | Blockers |
|------|----------|------------|-------------|----------|
| YYYY-MM-DD | X% | X | X | X |
| YYYY-MM-DD | X% | X | X | X |
---
## Communication Log
| Date | Type | Audience | Summary |
|------|------|----------|---------|
| YYYY-MM-DD | Status update | Board | Weekly update |
| YYYY-MM-DD | Escalation | CEO | Blocker escalation |
---
## Notes
{Additional status-related notes}
+140
View File
@@ -0,0 +1,140 @@
# Task Breakdown: {Initiative Name}
> **Last Updated**: YYYY-MM-DD
---
## Overview
| Cell | Total | Completed | In Progress | Blocked | Pending |
|------|-------|-----------|-------------|---------|---------|
| UX/UI | 0 | 0 | 0 | 0 | 0 |
| Backend | 0 | 0 | 0 | 0 | 0 |
| Frontend | 0 | 0 | 0 | 0 | 0 |
| **Total** | **0** | **0** | **0** | **0** | **0** |
---
## Dependency Graph
```
┌─────────────────┐
│ Requirements │
│ (Product) │
└────────┬────────┘
┌──────────────┼──────────────┐
│ │ │
▼ │ ▼
┌──────────┐ │ ┌──────────┐
│ UX/UI │ │ │ Backend │
│ Design │ │ │ API │
└────┬─────┘ │ └────┬─────┘
│ │ │
│ │ │
└───────┬────────┘ │
│ │
▼ │
┌──────────┐ │
│ Frontend │◄────────────────┘
│ UI │
└────┬─────┘
┌──────────┐
│ QA │
└────┬─────┘
┌──────────┐
│ Launch │
└──────────┘
```
---
## UX/UI Cell Tasks
| ID | Title | Type | Priority | Assigned | Status | Blocks |
|----|-------|------|----------|----------|--------|--------|
| TASK-XXX | {title} | design | P{n} | {agent} | {status} | TASK-XXX |
### Task Details
#### TASK-XXX: {Title}
- **Type**: Design
- **Priority**: P{n}
- **Assigned**: {agent}
- **Status**: {status}
- **Blocks**: {what this blocks}
- **Description**: {brief description}
- **Link**: [Task Record](../../active/TASK-XXX-slug/)
---
## Backend Cell Tasks
| ID | Title | Type | Priority | Assigned | Status | Blocks |
|----|-------|------|----------|----------|--------|--------|
| TASK-XXX | {title} | feature | P{n} | {agent} | {status} | TASK-XXX |
### Task Details
#### TASK-XXX: {Title}
- **Type**: Feature
- **Priority**: P{n}
- **Assigned**: {agent}
- **Status**: {status}
- **Blocked By**: {dependencies}
- **Blocks**: {what this blocks}
- **Description**: {brief description}
- **Link**: [Task Record](../../active/TASK-XXX-slug/)
---
## Frontend Cell Tasks
| ID | Title | Type | Priority | Assigned | Status | Blocked By |
|----|-------|------|----------|----------|--------|------------|
| TASK-XXX | {title} | feature | P{n} | {agent} | {status} | TASK-XXX, TASK-XXX |
### Task Details
#### TASK-XXX: {Title}
- **Type**: Feature
- **Priority**: P{n}
- **Assigned**: {agent}
- **Status**: {status}
- **Blocked By**: {UX design task, BE API task}
- **Description**: {brief description}
- **Link**: [Task Record](../../active/TASK-XXX-slug/)
---
## Documentation Tasks
| ID | Title | Cell | Priority | Assigned | Status |
|----|-------|------|----------|----------|--------|
| TASK-XXX | {title} | {cell} | P{n} | {agent} | {status} |
---
## Task Creation Checklist
When breaking down initiative into tasks:
- [ ] UX/UI design tasks identified
- [ ] Backend API tasks identified
- [ ] Frontend implementation tasks identified
- [ ] Documentation tasks identified
- [ ] Dependencies mapped
- [ ] Priorities assigned
- [ ] Tasks created in `.tasks/active/`
- [ ] Tasks linked back to this initiative
- [ ] Cell PMs notified
---
## Notes
{Additional notes on task breakdown, sequencing decisions, etc.}
+131
View File
@@ -0,0 +1,131 @@
# Timeline: {Initiative Name}
> **Last Updated**: YYYY-MM-DD
> **Overall Status**: {on_track / at_risk / delayed}
---
## Summary
| Metric | Value |
|--------|-------|
| **Start Date** | YYYY-MM-DD |
| **Target Completion** | YYYY-MM-DD |
| **Current Progress** | X% |
| **Days Remaining** | X days |
| **Status** | {on_track / at_risk / delayed} |
---
## Milestones
| # | Milestone | Target | Actual | Status | Notes |
|---|-----------|--------|--------|--------|-------|
| 1 | Requirements Finalized | YYYY-MM-DD | - | pending | |
| 2 | Design Complete | YYYY-MM-DD | - | pending | |
| 3 | Backend API Ready | YYYY-MM-DD | - | pending | |
| 4 | Frontend Integration | YYYY-MM-DD | - | pending | |
| 5 | QA Complete | YYYY-MM-DD | - | pending | |
| 6 | Documentation Complete | YYYY-MM-DD | - | pending | |
| 7 | Launch | YYYY-MM-DD | - | pending | |
---
## Gantt View
```
Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
------------|---|---|---|---|---|---|---|---|
Requirements| ██| | | | | | | |
UX Design | | ██| ██| | | | | |
Backend | | ██| ██| ██| | | | |
Frontend | | | | ██| ██| ██| | |
QA | | | | | | ██| ██| |
Docs | | | | | | | ██| |
Launch | | | | | | | | ██|
██ = Planned work
░░ = Buffer/contingency
▓▓ = Completed
```
---
## Weekly Schedule
### Week 1: {Date Range}
**Focus**: Requirements & Planning
| Day | Activity | Owner |
|-----|----------|-------|
| Mon | Requirements review | Product Owner |
| Tue | Technical planning | Main PM |
| Wed | Task breakdown | Main PM |
| Thu | Task assignment | Cell PMs |
| Fri | Kickoff | All |
---
### Week 2: {Date Range}
**Focus**: Design & Backend Start
| Day | Activity | Owner |
|-----|----------|-------|
| Mon | Design begins | UX-Dev |
| Tue | Backend planning | BE-Dev |
| Wed | {activity} | {owner} |
| Thu | {activity} | {owner} |
| Fri | Design review | UX-QA |
---
## Critical Path
The critical path is:
1. Requirements → Design → Frontend → QA → Launch
**Critical dependencies**:
- Frontend cannot start until design is complete
- Frontend cannot integrate until Backend API is ready
- QA cannot begin until Frontend is complete
**Parallel tracks**:
- Backend API can proceed in parallel with Design
- Documentation can proceed in parallel with QA
---
## Risk Assessment
| Risk | Probability | Impact | Mitigation | Status |
|------|-------------|--------|------------|--------|
| Design delays | Med | High | Start with wireframes | Watching |
| API complexity | Low | Med | Early technical spike | Mitigated |
| {risk} | {prob} | {impact} | {mitigation} | {status} |
---
## Buffer & Contingency
| Phase | Planned | Buffer | Total |
|-------|---------|--------|-------|
| Design | 5 days | 1 day | 6 days |
| Backend | 7 days | 2 days | 9 days |
| Frontend | 10 days | 2 days | 12 days |
| QA | 3 days | 1 day | 4 days |
**Total buffer**: X days
---
## Timeline Adjustments
| Date | Adjustment | Reason | Impact |
|------|------------|--------|--------|
| YYYY-MM-DD | {change} | {reason} | {impact} |
---
## Notes
{Additional timeline considerations, holidays, team availability, etc.}