Coordinator
Responsible for maintaining project context, tracking changes, and ensuring collaboration coherence across sessions.
When This Skill Activates
- Start of a new session (context loading)
- After major changes (documentation update)
- Before switching focus areas (handoff documentation)
- When project state is unclear
- After deployments or releases
Core Responsibilities
- Context Continuity: Maintain awareness of recent changes, decisions, and pending work
- Change Tracking: Keep a living record of what's been modified and why
- Collaboration Sync: Ensure consistent understanding across sessions
- Decision Memory: Document architectural decisions and their rationale
Coordination Artifacts
1. STATUS.md (Project Root)
Track current state:
# Project Status
## Current Focus
[What we're actively working on]
## Recent Changes (Last 5 Sessions)
- [Date] - [Summary of changes]
## Pending/Blocked
- [Items waiting on dependencies or decisions]
## Known Issues
- [Active bugs or technical debt]2. CHANGELOG.md (Project Root)
Keep a living changelog:
# Changelog
## [Unreleased]
### Added
### Changed
### Fixed
### Removed3. DECISIONS.md (Project Root)
Record significant decisions:
# Architectural Decision Records
## ADR-001: [Title]
- **Date**: YYYY-MM-DD
- **Status**: Accepted/Superseded
- **Context**: [Why was this decision needed?]
- **Decision**: [What did we decide?]
- **Consequences**: [What are the implications?]Session Start Protocol
- Read STATUS.md - Understand current state
- Check recent commits -
git log -10 --oneline - Review CHANGELOG.md - What's changed recently
- Summarize context - Brief the session on current priorities
Session End Protocol
- Update STATUS.md - Reflect new current state
- Update CHANGELOG.md - Add entries for changes made
- Document decisions - Add ADRs if significant choices were made
- Note pending work - What remains to be done next
Quick Reference Commands
# Check recent changes
git log -10 --oneline --all
# Check modified files
git status
# Check deployment state (if applicable)
cat apps/web/src/config/deployments.json | jq '.networks'Anti-Patterns to Avoid
- Making changes without updating coordination docs
- Assuming previous session context is remembered
- Not documenting why a decision was made
- Leaving work in an unclear state