Use this skill to maintain project context across sessions. Read docs/project.md at session start. Update it as work completes. Enables natural conversation about what to work on next.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Maintain a living document that tracks project evolution, enabling continuity between sessions.
Location: docs/project.md
This file is the source of truth for project context. Read it at session start. Update it as work progresses.
# Project Name
## Vision
[What this project is and why it exists - 2-3 sentences]
## Tech Stack
- **Language/Framework**: [X]
- **Key Dependencies**: [Y]
- **Deployment**: [Z]
## Decisions Log
| Date | Decision | Rationale |
|------|----------|-----------|
| YYYY-MM-DD | [Decision made] | [Why we made it] |
## Completed
- [x] [Feature/milestone] (YYYY-MM-DD)
## Current Focus
[What we're actively working on right now - updated when starting new work]
## Next Steps
- [ ] [Next thing to build]
- [ ] [After that]
- [ ] [Then this]
## Notes
[Context useful between sessions - blockers, ideas, open questions, gotchas]
When user asks "what should we work on next?":
When user describes new work:
If no docs/project.md exists and user wants to start a new project: