/end-work
Complete work session with final checklist
$ npx -y skills add bybren-llc/safe-agentic-workflow --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/end-work
Context preview
What this command does when you run it.
Complete work session with final checklist
Command definition
end-work.mddescription: Complete work session with final checklist
allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]
You are completing a work session. Execute final checklist before context switch or session end.
Completion Checklist
1. Work Status
Verify current state:
git status
git log origin/dev..HEAD --oneline
Status options:
- **Work Complete**: Ready for PR
- **Work In Progress**: Safe stopping point, commit and document
- **Blocked**: Document blockers
2. Commit All Work
If uncommitted changes:
git add .
git commit -m "type(scope): description [{{TICKET_PREFIX}}-XXX]"Verify all work committed:
git status # Should show clean working tree
3. Documentation Status
Quick check:
- [ ] Inline comments for complex logic?
- [ ] README updated if new feature?
- [ ] CLAUDE.md/CONTRIBUTING.md updated if workflow changed?
- [ ] Linear ticket status current?
4. Update Linear Ticket
> **Note**: Tickets referenced in commit messages (e.g., `[{{TICKET_PREFIX}}-XXX]`) auto-sync to Done when the PR merges via the GitHub-Linear integration. Manually close any child stories not referenced in commits.
Based on work status:
**If Complete**:
- Update ticket status to "Ready for Review" or "In Progress"
- Add comment summarizing work done
- Link to PR if created
**If In Progress**:
- Update ticket with progress notes
- Document any blockers or questions
- Set status appropriately
**If Blocked**:
- Document blocker clearly
- Add comments to ticket
- Tag appropriate people
Use Linear MCP:
mcp__{{MCP_LINEAR_SERVER}}__update_issue
mcp__{{MCP_LINEAR_SERVER}}__create_comment5. Context Preservation
If stopping mid-work, document:
- What was completed
- What's next
- Any decisions made
- Any blockers encountered
- Questions to discuss
Create context document if needed:
## Session Context - [Date]
### Completed
- Item 1
- Item 2
### Next Steps
1. Task 1
2. Task 2
### Decisions
- Decision 1: Rationale
### Blockers
- Blocker 1: Details
### Questions
- Question 1
6. Branch Status
Decide next action:
**If Ready for PR**:
- Push branch: `git push origin {branch-name}`
- Create PR (or remind to create)
- Reference `/pre-pr` command
**If In Progress**:
- Push work: `git push origin {branch-name}` (if exists)
- Or: Keep local until next session
**If Experimental**:
- Consider creating WIP PR for visibility
- Or: Keep local and document intent
Output Format
Provide summary:
- ✅ Work status (complete/in-progress/blocked)
- ✅ All changes committed
- ✅ Documentation current
- ✅ Linear ticket updated
- ✅ Context preserved (if needed)
- ✅ Ready for next session
Include any action items for user:
- PR creation needed?
- Blockers to resolve?
- Questions to answer?
- Follow-up tasks?
Success Criteria
Session ends cleanly:
- No uncommitted work (if complete)
- or: Safe stopping point documented (if in-progress)
- Linear ticket reflects current status
- Next session can pick up smoothly
This ensures continuity and prevents context loss.
Read more
description: Complete work session with final checklist allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]
You are completing a work session. Execute final checklist before context switch or session end.
Completion Checklist
1. Work Status
Verify current state:
git status git log origin/dev..HEAD --oneline
Status options:
- **Work Complete**: Ready for PR
- **Work In Progress**: Safe stopping point, commit and document
- **Blocked**: Document blockers
2. Commit All Work
If uncommitted changes:
git add .
git commit -m "type(scope): description [{{TICKET_PREFIX}}-XXX]"Verify all work committed:
git status # Should show clean working tree
3. Documentation Status
Quick check:
- [ ] Inline comments for complex logic?
- [ ] README updated if new feature?
- [ ] CLAUDE.md/CONTRIBUTING.md updated if workflow changed?
- [ ] Linear ticket status current?
4. Update Linear Ticket
> **Note**: Tickets referenced in commit messages (e.g., `[{{TICKET_PREFIX}}-XXX]`) auto-sync to Done when the PR merges via the GitHub-Linear integration. Manually close any child stories not referenced in commits.
Based on work status:
**If Complete**:
- Update ticket status to "Ready for Review" or "In Progress"
- Add comment summarizing work done
- Link to PR if created
**If In Progress**:
- Update ticket with progress notes
- Document any blockers or questions
- Set status appropriately
**If Blocked**:
- Document blocker clearly
- Add comments to ticket
- Tag appropriate people
Use Linear MCP:
mcp__{{MCP_LINEAR_SERVER}}__update_issue
mcp__{{MCP_LINEAR_SERVER}}__create_comment5. Context Preservation
If stopping mid-work, document:
- What was completed
- What's next
- Any decisions made
- Any blockers encountered
- Questions to discuss
Create context document if needed:
## Session Context - [Date] ### Completed - Item 1 - Item 2 ### Next Steps 1. Task 1 2. Task 2 ### Decisions - Decision 1: Rationale ### Blockers - Blocker 1: Details ### Questions - Question 1
6. Branch Status
Decide next action:
**If Ready for PR**:
- Push branch: `git push origin {branch-name}`
- Create PR (or remind to create)
- Reference `/pre-pr` command
**If In Progress**:
- Push work: `git push origin {branch-name}` (if exists)
- Or: Keep local until next session
**If Experimental**:
- Consider creating WIP PR for visibility
- Or: Keep local and document intent
Output Format
Provide summary:
- ✅ Work status (complete/in-progress/blocked)
- ✅ All changes committed
- ✅ Documentation current
- ✅ Linear ticket updated
- ✅ Context preserved (if needed)
- ✅ Ready for next session
Include any action items for user:
- PR creation needed?
- Blockers to resolve?
- Questions to answer?
- Follow-up tasks?
Success Criteria
Session ends cleanly:
- No uncommitted work (if complete)
- or: Safe stopping point documented (if in-progress)
- Linear ticket reflects current status
- Next session can pick up smoothly
This ensures continuity and prevents context loss.
SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!) Works for any team with repeatable processes: Software, Marketing, Research, Legal, Operations.
Other commands on safe-agentic-workflow.
- /audit-deps
Run comprehensive dependency audit
Open command - /check-docker-status
Check if {{DEV_MACHINE}} Docker environment needs updating
Open command - /check-workflow
Quick status check of current workflow state
Open command - /deploy-dev
Deploy latest Docker image to {{DEV_MACHINE}} dev environment
Open command - /dev-health
Check {{DEV_MACHINE}} dev environment health dashboard
Open command - /dev-logs
View {{DEV_MACHINE}} dev container logs
Open command

