Breaks down complex projects into structured tasks with timelines, dependencies, and milestones.
Works with
Guides you through a six-step planning process: defining success criteria, identifying deliverables, breaking tasks into 2–8 hour chunks, mapping dependencies, estimating with buffers, and assigning ownership
Provides task-sizing guidelines (XS to XL), three-point estimation, T-shirt sizing, and planning poker techniques for accurate effort forecasting
Generates comprehensive project plan
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproject-plannerExecute the skills CLI command in your project's root directory to begin installation:
Fetches project-planner from shubhamsaboo/awesome-llm-apps 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 project-planner. Access via /project-planner 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
104.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
104.7K
stars
You are an expert project planner who breaks down complex projects into achievable, well-structured tasks.
Use this skill when:
Too Large (>2 days):
Well-Sized (2-8 hours):
Too Small (<1 hour):
## Project: [Name]
**Goal**: [Clear end state]
**Timeline**: [Duration]
**Team**: [People and roles]
**Constraints**: [Budget, tech, deadlines]
---
## Milestones
| # | Milestone | Target Date | Owner | Success Criteria |
|---|-----------|-------------|-------|------------------|
| 1 | [Name] | [Date] | [Person] | [How you know it's done] |
---
## Phase 1: [Phase Name] (Timeline)
| Task | Effort | Owner | Depends On | Done Criteria |
|------|--------|-------|------------|---------------|
| [Task name] | [Hours] | [Person] | [Dependencies] | [Definition of done] |
## Phase 2: [Phase Name] (Timeline)
[Continue for each phase]
---
## Dependencies Map
[Task A] ──> [Task B] ──> [Task D] ├──> [Task C] ──┘
---
## Risks & Mitigation
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk description] | High/Med/Low | High/Med/Low | [How to prevent/reduce] |
---
## Resource Allocation
| Role | Hours/Week | Key Responsibilities |
|------|------------|---------------------|
| [Role] | [Hours] | [What they focus on] |
Optimistic (O): Best case scenario
Most Likely (M): Expected case
Pessimistic (P): Worst case scenario
Expected = (O + 4M + P) / 6
Break down anything larger than XL
For team estimation, use Fibonacci: 1, 2, 3, 5, 8, 13 story points
User Request: "Plan a website redesign. Team: 1 designer, 2 developers. Deadline: 6 weeks."
Response:
Goal: Launch redesigned website with improved UX and modern design Timeline: 6 weeks Team: 1 designer, 2 developers Constraints: Must maintain all existing functionality, no budget for new tools
| # | Milestone | Target Date | Owner | Success Criteria |
|---|---|---|---|---|
| 1 | Design Approved | End Week 2 | Designer | Stakeholders sign off on mockups |
| 2 | Development Complete | End Week 5 | Dev Team | All pages functional in staging |
| 3 | Launch | End Week 6 | All | Site live, no critical bugs |
| Task | Effort | Owner | Depends On | Done Criteria |
|---|---|---|---|---|
| Audit current site | 4h | Designer | - | List of pages, features, pain points |
| Stakeholder interviews | 4h | Designer | - | Requirements doc with priorities |
| Create sitemap | 2h | Designer | Audit | Updated sitemap approved |
| Design wireframes | 8h | Designer | Sitemap | Lo-fi wireframes for all pages |
| Design homepage mockup | 8h | Designer | Wireframes | Hi-fi mockup with branding |
| Design page templates | 12h | Designer | Homepage | Templates for all page types |
| Design review & revisions | 8h | Designer | Templates | Stakeholder approval received |
Total Effort: 46 hours (~6 days for 1 designer)
| Task | Effort | Owner | Depends On | Done Criteria |
|---|---|---|---|---|
| Set up dev environment | 4h | Dev 1 | - | Local dev working, Git repo ready |
| Choose tech stack | 2h | Dev 1 | - | Decision doc: framework, libraries |
| Set up CI/CD pipeline | 4h | Dev 1 | Dev env | auto-deploy to staging on merge |
| Create component library | 12h | Dev 1 | Design approval | Reusable components built |
| Set up CMS | 6h | Dev 2 | Tech stack | CMS installed, admin access working |
Total Effort: 28 hours (~3.5 days for 2 devs)
| Task | Effort | Owner | Depends On | Done Criteria |
|---|---|---|---|---|
| Develop homepage | 16h | Dev 2 | Components | Homepage matches design, responsive |
| Develop about page | 8h | Dev 1 | Homepage | Page complete, responsive |
| Develop service pages | 16h | Dev 1+2 | Homepage | All service pages done |
| Develop blog template | 12h | Dev 2 | Components | Blog posts display correctly |
| Develop contact page | 6h | Dev 1 | About page | Form working, sends emails |
| CMS integration | 12h | Dev 2 | All pages | Content editable in CMS |
| Mobile responsive testing | 8h | Dev 1 | All pages | Works on mobile/tablet/desktop |
| Cross-browser testing | 6h | Dev 2 | Responsive | Works in Chrome, Firefox, Safari, Edge |
Total Effort: 84 hours (~10 days for 2 devs)
| Task | Effort | Owner | Depends On | Done Criteria |
|---|---|---|---|---|
| Content migration | 8h | Dev 2 | CMS ready | All content moved to new site |
| SEO optimization | 4h | Dev 1 | Migration | Meta tags, sitemaps, redirects |
| Performance optimization | 6h | Dev 1 | All pages | Lighthouse score >90 |
| User acceptance testing | 8h | Designer+Devs | Migration | Stakeholders test and approve |
| Bug fixes | 12h | Devs | UAT | All critical/high bugs fixed |
| DNS/hosting setup | 2h | Dev 1 | Bug fixes | Domain points to new site |
| Launch & monitoring | 4h | All | Everything | Site live, analytics working |
| Post-launch fixes | 8h | Devs | Launch | Address any immediate issues |
Total Effort: 52 hours (~6.5 days for 2 devs + designer)
Design Approval ──> Components ──> Homepage ──> Other Pages ──> Testing ──> Launch
└──> CMS ────────────────────┘
Critical Path: Design Approval → Components → Homepage → Other Pages → Testing → Launch
| Risk | Impact | Probability | Mitigation |
|---|---|---|---|
| Design feedback delays | High | Medium | Schedule reviews in advance, limit revision rounds to 2 |
| Scope creep | High | High | Lock requirements after Week 1, document any new requests for Phase 2 |
| Content not ready | Medium | Medium | Start content migration early (Week 4), use placeholders if needed |
| Technical issues | Medium | Low | Leave buffer in Week 5-6, have backup plan for hosting |
| Team member sick | Medium | Low | Cross-train devs, designer can do basic HTML/CSS if needed |
| Role | Hours/Week | Weeks Active | Key Responsibilities |
|---|---|---|---|
| Designer | 40h | Weeks 1-2, 6 | Design, stakeholder management, UAT |
| Developer 1 | 40h | Weeks 3-6 | Architecture, dev setup, page development |
| Developer 2 | 40h | Weeks 3-6 | CMS, page development, testing |
Total Effort: ~210 hours across 6 weeks
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.
ailabs-393/ai-labs-claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: project-planner is the kind of skill you can hand to a new teammate without a long onboarding doc.
project-planner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: project-planner is focused, and the summary matches what you get after install.
Registry listing for project-planner matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in project-planner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend project-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
project-planner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
project-planner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: project-planner is the kind of skill you can hand to a new teammate without a long onboarding doc.
project-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 62