4.2 KiB
4.2 KiB
Active Context
Current work focus, recent changes, and immediate priorities
Current Sprint/Iteration
Sprint: [Name/Number]
Duration: [Start Date] - [End Date]
Theme: [Main focus of this sprint]
Status: [On Track/At Risk/Blocked]
Active Work Items
In Progress
| Item | Type | Assignee | Status | Notes |
|---|---|---|---|---|
| [ID: Title] | Story/Bug/Task | [Who] | [% complete] | [Current state] |
| [ID: Title] | Story/Bug/Task | [Who] | [% complete] | [Blockers] |
Up Next (Priority Order)
-
[ID: Title] - [Brief description]
- Dependencies: [What needs to complete first]
- Estimate: [Size/effort]
-
[ID: Title] - [Brief description]
- Ready to start: [Yes/No - why]
Recently Completed
| Item | Completed | Key Changes |
|---|---|---|
| [ID: Title] | [Date] | [What was done] |
| [ID: Title] | [Date] | [Impact/changes] |
Recent Decisions
Decision 1: [Title]
- Date: [When decided]
- Context: [Why needed]
- Choice: [What was decided]
- Impact: [What changes]
- ADR: [Link if documented]
Decision 2: [Title]
- Date: [When decided]
- Choice: [What was decided]
- Rationale: [Key reasoning]
Current Technical Focus
Active Development Areas
- Module/Component: [What's being worked on]
- Changes: [What's changing]
- Approach: [How we're doing it]
- Progress: [Current state]
Refactoring/Tech Debt
- Area: [What's being improved]
- Reason: [Why now]
- Scope: [What's included]
- Status: [Progress]
Important Patterns & Preferences
Coding Patterns
-
Pattern 1: [Description]
- Example: [Where to see it]
- When to use: [Guidance]
-
Pattern 2: [Description]
- Rationale: [Why this way]
Team Preferences
- Code Style: [Key preferences beyond standards]
- PR Process: [How we handle reviews]
- Communication: [How we coordinate]
- Documentation: [What we document when]
Recent Learnings & Insights
Technical Discoveries
-
Learning: [What we learned]
- Context: [How we discovered it]
- Application: [How it affects our approach]
-
Insight: [What we realized]
- Impact: [What changes as a result]
Process Improvements
- What Changed: [Process adjustment]
- Why: [Problem it solves]
- Result: [Impact so far]
Open Questions & Investigations
Technical Questions
-
Question: [What we need to figure out]
- Context: [Why it matters]
- Options: [Possible approaches]
- Timeline: [When we need answers]
-
Investigation: [What we're researching]
- Purpose: [Why we're looking into it]
- Progress: [What we've found so far]
Product Questions
- Clarification Needed: [What's unclear]
- Impact: [What's blocked]
- Who to ask: [Stakeholder]
Blockers & Risks
Current Blockers
| Blocker | Impact | Owner | ETA |
|---|---|---|---|
| [Description] | [What can't proceed] | [Who's resolving] | [Expected resolution] |
Active Risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| [Description] | High/Med/Low | High/Med/Low | [What we're doing] |
Environment & Tool Updates
Recent Changes
- Tool/Version Update: [What changed]
- Date: [When]
- Impact: [How it affects development]
- Action: [What developers need to do]
Pending Updates
- Planned Change: [What will change]
- Timeline: [When]
- Preparation: [What to do beforehand]
Next Session Priorities
Immediate Next Steps
- [Specific task to tackle first]
- [Second priority if first is blocked]
- [Third priority or investigation]
Context for Next Session
- Where we left off: [Current state]
- Key files: [Important files to review]
- Gotchas: [Things to remember]
- Dependencies: [What to check first]
Communication Log
Recent Important Messages
- Date: [Message summary or decision]
- Date: [Key communication]
Pending Communications
- Need to inform: [Who about what]
- Awaiting response: [What we're waiting for]
This document is the most frequently updated. It represents the current state and immediate context needed to continue work effectively.