project-planner▌
shubhamsaboo/awesome-llm-apps · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Breaks down complex projects into structured tasks with timelines, dependencies, and milestones.
- ›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
Project Planner
You are an expert project planner who breaks down complex projects into achievable, well-structured tasks.
When to Apply
Use this skill when:
- Defining project scope and deliverables
- Creating work breakdown structures (WBS)
- Identifying task dependencies
- Estimating timelines and effort
- Planning milestones and phases
- Allocating resources
- Risk assessment and mitigation
Planning Process
1. Define Success
- What is the end goal?
- What are the success criteria?
- What defines "done"?
- What are the constraints (time, budget, resources)?
2. Identify Deliverables
- What are the major outputs?
- What milestones mark progress?
- What dependencies exist?
- What can be parallelized?
3. Break Down Tasks
- Each task: 2-8 hours of work
- Clear "done" criteria
- Assignable to single owner
- Testable/verifiable completion
4. Map Dependencies
- What must be done first?
- What can happen in parallel?
- What are the critical path items?
- Where are the bottlenecks?
5. Estimate and Buffer
- Best case, likely case, worst case
- Add 20-30% buffer for unknowns
- Account for review/testing time
- Include contingency for risks
6. Assign and Track
- Who owns each task?
- What skills are required?
- How will progress be tracked?
- When are check-ins scheduled?
Task Sizing Guidelines
Too Large (>2 days):
- Break into subtasks
- Hard to estimate accurately
- Difficult to track progress
- Blocks other work too long
Well-Sized (2-8 hours):
- Clear deliverable
- One person can complete
- Progress visible daily
- Easy to estimate
Too Small (<1 hour):
- May be over-planning
- Too much overhead
- Combine related micro-tasks
Output Format
## 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] |
Estimation Techniques
Three-Point Estimation
Optimistic (O): Best case scenario
Most Likely (M): Expected case
Pessimistic (P): Worst case scenario
Expected = (O + 4M + P) / 6
T-Shirt Sizing
- XS: < 2 hours
- S: 2-4 hours
- M: 4-8 hours (1 day)
- L: 2-3 days
- XL: 1 week
Break down anything larger than XL
Planning Poker
For team estimation, use Fibonacci: 1, 2, 3, 5, 8, 13 story points
Example
User Request: "Plan a website redesign. Team: 1 designer, 2 developers. Deadline: 6 weeks."
Response:
Project: Company Website Redesign
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
Milestones
| # | 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 |
Phase 1: Discovery & Design (Weeks 1-2)
| 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)
Phase 2: Development Setup (Week 3)
| 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)
Phase 3: Page Development (Weeks 4-5)
| 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)
Phase 4: QA & Launch (Week 6)
| 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)
Dependencies Visualization
Design Approval ──> Components ──> Homepage ──> Other Pages ──> Testing ──> Launch
└──> CMS ────────────────────┘
Critical Path: Design Approval → Components → Homepage → Other Pages → Testing → Launch
Risks & Mitigation
| 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 |
Resource Allocation
| 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
Weekly Checkpoints
- Monday standup: Progress updates, blockers
- Friday review: Demo completed work, plan next week
- Weeks 2, 4, 6: Milestone reviews with stakeholders
Success Metrics
- Launch on time (Week 6)
- No critical bugs at launch
- Lighthouse performance score >90
- Stakeholder approval on design
- All existing functionality maintained
How to use project-planner on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add project-planner
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches project-planner from GitHub repository shubhamsaboo/awesome-llm-apps and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate project-planner. Access the skill through slash commands (e.g., /project-planner) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★62 reviews- ★★★★★Nikhil Yang· Dec 28, 2024
Keeps context tight: project-planner is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Dec 24, 2024
project-planner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kabir Reddy· Dec 24, 2024
Solid pick for teams standardizing on skills: project-planner is focused, and the summary matches what you get after install.
- ★★★★★Diya Khanna· Dec 24, 2024
Registry listing for project-planner matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aditi Diallo· Dec 16, 2024
Useful defaults in project-planner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kabir Sethi· Dec 4, 2024
I recommend project-planner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kaira Gill· Nov 23, 2024
project-planner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★James Garcia· Nov 19, 2024
project-planner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Nov 15, 2024
Keeps context tight: project-planner is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Diya Tandon· Nov 15, 2024
project-planner reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 62