Fetches handoff from boshu2/agentops and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/handoff
Restart Cursor to activate handoff. Access via /handoff in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Write to:.agents/handoff/YYYY-MM-DD-<topic-slug>.md (use date +%Y-%m-%d)
# Handoff: <Topic>**Date:** YYYY-MM-DDTHH:MM:SSZ
**Session:**<briefsessiondescription>**Status:**<Pausedmid-task|Betweentasks|BlockedonX>---## What We Accomplished This Session### 1. <Accomplishment 1><Briefdescriptionwithfile:linecitations>**Files changed:**-`path/to/file.py` - Description
### 2. <Accomplishment 2>...
---## Where We Paused<Cleardescriptionofpausepoint>**Last action:**<whatwasjustdone>**Next action:**<whatshouldhappennext>**Blockers (if any):**<anythingblockingprogress>---## Context to Gather for Next Session1.<Contextitem1> - <whyneeded>2.<Contextitem2> - <whyneeded>---## Questions to Answer1.<Openquestionneedingdecision>2.<Clarificationneeded>---## Files to Read
### Step 7: Write Continuation Prompt
**Write to:** `.agents/handoff/YYYY-MM-DD-<topic-slug>-prompt.md` (use `date +%Y-%m-%d`)
```markdown
# Continuation Prompt for New Session
Copy/paste this to start the next session:
---
## Context
<2-3 sentences describing the work and where we paused>
## Read First
1. The handoff doc: `.agents/handoff/YYYY-MM-DD-<topic-slug>.md`
2. <Other critical files>
## What I Need Help With
<Clear statement of what the next session should accomplish>
## Key Files
Open Questions
<Question 1>
<Question 2>
<Suggested skill to invoke, e.g., "Use /implement to continue">
### Step 8: Extract Learnings (Optional)
If significant learnings occurred this session, also run post-mortem:
```bash
# Check if post-mortem skill should be invoked
# (if >3 commits or major decisions made)
git log --oneline --since="2 hours ago" 2>/dev/null | wc -l
If ≥3 commits: Suggest running /post-mortem --quick to extract learnings.
If <3 commits: Handoff alone is sufficient; learnings are likely minimal.
Step 9: Report to User
Tell the user:
Handoff document location
Continuation prompt location
Summary of what was captured
Suggestion: Copy the continuation prompt for next session
If learnings detected, suggest /post-mortem --quick
Output completion marker:
<promise>DONE</promise>
If no context to capture (no commits, no changes):
<promise>EMPTY</promise>
Reason: No session activity found to hand off
Example Output
Handoff created:
.agents/handoff/20260131T143000Z-auth-refactor.md
.agents/handoff/20260131T143000Z-auth-refactor-prompt.md
Session captured:
- 5 commits, 12 files changed
- Paused: mid-implementation of OAuth flow
- Next: Complete token refresh logic
To continue: Copy the prompt from auth-refactor-prompt.md
<promise>DONE</promise>
Key Rules
Capture state, not just summary - next session needs to pick up exactly where we left off
Identify blockers clearly - don't leave the next session guessing
List files explicitly - paths, not descriptions
Write the continuation prompt - make resumption effortless
Cite everything - file:line for all references
Integration with /post-mortem
Handoff captures state for continuation.
Post-mortem captures learnings for the flywheel (full knowledge lifecycle).
For a clean session end:
/handoff # Capture state for continuation/post-mortem --quick# Extract learnings for future
Both should be run when ending a productive session.
Without ao CLI
If ao CLI not available:
Skip the ao ratchet status check in Step 2
Step 8 retro suggestion still works (uses git commit count)
All handoff documents are still written to .agents/handoff/
Knowledge is captured for future sessions via handoff, just not indexed
Examples
Paused Mid-Implementation
User says:/handoff (after working on OAuth flow for 2 hours, need to stop)
What happens:
Agent detects recent commits (5 commits in last 2 hours, auth-related)
Agent checks in-progress work with bd list (issue #42 still open)
Agent identifies pause point: "Completed token generation, about to start refresh logic"
Agent lists key files: auth.go, token.go, research doc, plan doc
Agent writes handoff document with accomplishments and pause state
Agent writes continuation prompt with clear next action
Agent checks commits (5) and suggests running /post-mortem --quick to extract learnings
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
