Strategic planning for open source contributions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpr-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches pr-plan from boshu2/agentops and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pr-plan. Access via /pr-plan in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
260
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
260
stars
Strategic planning for open source contributions.
Create a contribution plan that bridges research and implementation. Takes
$pr-research output and produces an actionable plan.
Output: .agents/plans/YYYY-MM-DD-pr-plan-{repo-slug}.md
When to Use:
$pr-researchWhen NOT to Use:
$plan)0. Input Discovery -> Find/load pr-research artifact
1. Scope Definition -> What exactly to contribute
2. Target Selection -> Which issues/areas to address
3. Criteria Definition -> Acceptance criteria from research
4. Risk Assessment -> What could go wrong
5. Strategy Formation -> Implementation approach
6. Output -> Write plan artifact
| Question | Why It Matters |
|---|---|
| What specific functionality? | Clear deliverable |
| Which files/packages? | Limits impact surface |
| What's explicitly out of scope? | Prevents scope creep |
| Single PR or series? | Sets expectations |
## Scope
**Contribution**: [1-2 sentences describing the change]
**Affected Areas**:
- `path/to/file.go` - [what changes]
**Out of Scope**:
- [Related but excluded work]
Define success from maintainer perspective:
## Acceptance Criteria
### Code Quality
- [ ] Follows project coding style
- [ ] Passes existing tests
- [ ] Adds tests for new functionality
- [ ] No linting warnings
### PR Requirements
- [ ] Title follows convention
- [ ] Body uses project template
- [ ] Size within acceptable range
- [ ] Single logical change
### Project-Specific
- [ ] [Any project-specific requirements from research]
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| PR review takes > 2 weeks | Medium | Medium | Start small, be responsive |
| Scope expands during review | Medium | High | Define scope clearly upfront |
| Breaking change discovered | Low | High | Test against multiple versions |
## Implementation Strategy
### Approach
1. **Setup**: Fork repo, configure dev environment
2. **Understand**: Read existing code in affected area
3. **Implement**: Make changes following project patterns
4. **Test**: Run existing tests + add new tests
5. **Document**: Update any affected documentation
6. **Submit**: Create PR following project conventions
### Pre-Implementation Checklist
- [ ] Fork created and up-to-date with upstream
- [ ] Dev environment working
- [ ] Issue claimed or comment posted
- [ ] Recent repo activity reviewed
Write to .agents/plans/YYYY-MM-DD-pr-plan-{repo-slug}.md
# PR Plan: {repo-name}
## Executive Summary
{2-3 sentences: what you're contributing, why, expected outcome}
## Scope
**Contribution**: {description}
**Affected Areas**: [list]
**Out of Scope**: [list]
## Target
**Primary Issue**: #{N} - {title}
## Acceptance Criteria
[checklist]
## Risk Assessment
[table]
## Implementation Strategy
[numbered steps]
## Next Steps
1. Claim/comment on target issue
2. Fork and set up development environment
3. Implement following strategy
4. Run `$pr-prep` when ready
$pr-research <repo> -> $pr-plan <research> -> implement -> $pr-prep
User says: "Create a contribution plan from my PR research artifact."
What happens:
User says: "Check if this PR plan is too large for one submission."
What happens:
| Problem | Cause | Solution |
|---|---|---|
| Plan has vague acceptance criteria | Criteria not measurable | Convert criteria to concrete behavioral checks |
| Scope too broad | Multiple concerns mixed | Split by user-visible change or subsystem boundary |
| Risk section is weak | Missing failure-mode analysis | Add integration, review, and rollback risks explicitly |
| Plan conflicts with repo norms | Research artifact incomplete | Re-run $pr-research and refresh constraints |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pr-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: pr-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for pr-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
pr-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
pr-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend pr-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in pr-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend pr-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in pr-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in pr-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 30