| name | session-startup |
| description | Ensures the agent is oriented on the current project state before taking action. Prevents the agent from working with stale context or making assumptions about project status. [GENERATED BY MOTIF — review and customize] |
Session Startup
Ensures the agent is oriented on the current project state before taking action. Prevents the agent from working with stale context or making assumptions about project status.
When to Use
- User opens a new session with any variant of 'refresh yourself'
- User says 'we're working in [project] today' or 'we shall continue'
- Especially when: multiple days have passed since last session
- Don't skip when: returning to a project after working on a different one
Instructions
- Read project README and any STATUS.md or MEMORY.md files
- Check recent git log (last 5-10 commits) for what changed
- Summarize: current phase, what's working, what's blocked, what's next
- If deployment state matters, check production status
- Wait for user direction before acting
- do not propose work unprompted
- If user provides specific direction, acknowledge context and proceed
Best Practices
- Keep the summary concise (3-5 bullet points)
- Mention specific recent changes by name
- Avoid: Don't dump entire file contents -- summarize
- Avoid: Avoid proposing work until asked
Common Pitfalls
| Problem | Solution |
|---|
| Agent starts working immediately without reading project state | Always read STATUS/README first, even if you think you remember |
| Summary is too long and buries the key points | Lead with phase and blockers, keep to 3-5 bullets |
Key Constraints
- Never propose work before the user gives direction
- Always read project status files before summarizing
- Summary must be concise enough to read in 10 seconds
