project-planner

Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones. Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines, managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.

Compatible avec~Claude Code~Codex CLI~Cursor
npx add-skill https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/awesome_agent_skills/project-planner

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

#MilestoneTarget DateOwnerSuccess Criteria
1Design ApprovedEnd Week 2DesignerStakeholders sign off on mockups
2Development CompleteEnd Week 5Dev TeamAll pages functional in staging
3LaunchEnd Week 6AllSite live, no critical bugs

Phase 1: Discovery & Design (Weeks 1-2)

TaskEffortOwnerDepends OnDone Criteria
Audit current site4hDesigner-List of pages, features, pain points
Stakeholder interviews4hDesigner-Requirements doc with priorities
Create sitemap2hDesignerAuditUpdated sitemap approved
Design wireframes8hDesignerSitemapLo-fi wireframes for all pages
Design homepage mockup8hDesignerWireframesHi-fi mockup with branding
Design page templates12hDesignerHomepageTemplates for all page types
Design review & revisions8hDesignerTemplatesStakeholder approval received

Total Effort: 46 hours (~6 days for 1 designer)


Phase 2: Development Setup (Week 3)

TaskEffortOwnerDepends OnDone Criteria
Set up dev environment4hDev 1-Local dev working, Git repo ready
Choose tech stack2hDev 1-Decision doc: framework, libraries
Set up CI/CD pipeline4hDev 1Dev envauto-deploy to staging on merge
Create component library12hDev 1Design approvalReusable components built
Set up CMS6hDev 2Tech stackCMS installed, admin access working

Total Effort: 28 hours (~3.5 days for 2 devs)


Phase 3: Page Development (Weeks 4-5)

TaskEffortOwnerDepends OnDone Criteria
Develop homepage16hDev 2ComponentsHomepage matches design, responsive
Develop about page8hDev 1HomepagePage complete, responsive
Develop service pages16hDev 1+2HomepageAll service pages done
Develop blog template12hDev 2ComponentsBlog posts display correctly
Develop contact page6hDev 1About pageForm working, sends emails
CMS integration12hDev 2All pagesContent editable in CMS
Mobile responsive testing8hDev 1All pagesWorks on mobile/tablet/desktop
Cross-browser testing6hDev 2ResponsiveWorks in Chrome, Firefox, Safari, Edge

Total Effort: 84 hours (~10 days for 2 devs)


Phase 4: QA & Launch (Week 6)

TaskEffortOwnerDepends OnDone Criteria
Content migration8hDev 2CMS readyAll content moved to new site
SEO optimization4hDev 1MigrationMeta tags, sitemaps, redirects
Performance optimization6hDev 1All pagesLighthouse score >90
User acceptance testing8hDesigner+DevsMigrationStakeholders test and approve
Bug fixes12hDevsUATAll critical/high bugs fixed
DNS/hosting setup2hDev 1Bug fixesDomain points to new site
Launch & monitoring4hAllEverythingSite live, analytics working
Post-launch fixes8hDevsLaunchAddress 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

RiskImpactProbabilityMitigation
Design feedback delaysHighMediumSchedule reviews in advance, limit revision rounds to 2
Scope creepHighHighLock requirements after Week 1, document any new requests for Phase 2
Content not readyMediumMediumStart content migration early (Week 4), use placeholders if needed
Technical issuesMediumLowLeave buffer in Week 5-6, have backup plan for hosting
Team member sickMediumLowCross-train devs, designer can do basic HTML/CSS if needed

Resource Allocation

RoleHours/WeekWeeks ActiveKey Responsibilities
Designer40hWeeks 1-2, 6Design, stakeholder management, UAT
Developer 140hWeeks 3-6Architecture, dev setup, page development
Developer 240hWeeks 3-6CMS, 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

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

academic-researcher

Academic research assistant for literature reviews, paper analysis, and scholarly writing. Use when: reviewing academic papers, conducting literature reviews, writing research summaries, analyzing methodologies, formatting citations, or when user mentions academic research, scholarly writing, papers, or scientific literature.

code-reviewer

Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.

content-creator

Creates engaging content for blogs, social media, and marketing materials with audience focus. Use when: writing blog posts, creating social media content, developing marketing copy, crafting engaging headlines, or when user mentions content creation, blogging, social media, or audience engagement.

content-writer

Writes marketing copy for landing pages, emails, and social media posts. Use when creating promotional content, sales copy, or brand messaging.

data-analyst

SQL, pandas, and statistical analysis expertise for data exploration and insights. Use when: analyzing data, writing SQL queries, using pandas, performing statistical analysis, or when user mentions data analysis, SQL, pandas, statistics, or needs help exploring datasets.

debugger

Systematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, troubleshooting bugs, investigating crashes, analyzing stack traces, fixing broken code, or when user mentions debugging, error, bug, crash, or "not working".

decision-helper

Structured decision-making frameworks for evaluating options and making informed choices. Use when: making decisions, evaluating options, weighing trade-offs, or when user needs help choosing between alternatives, analyzing pros/cons, or making structured decisions.

deep-research

Comprehensive research assistant that synthesizes information from multiple sources with citations. Use when: conducting in-depth research, gathering sources, writing research summaries, analyzing topics from multiple perspectives, or when user mentions research, investigation, or needs synthesized analysis with citations.

editor

Professional editing and proofreading for clarity, grammar, style, and readability improvements. Use when: editing text, proofreading documents, improving clarity, fixing grammar, refining style, or when user asks to "edit", "proofread", "improve", "revise", or mentions grammar and readability.

email-drafter

Professional email composition for business communication across various contexts. Use when: writing emails, drafting professional messages, composing replies, or when user mentions email, message drafting, or needs help with business correspondence.

fact-checker

Systematic fact verification and misinformation identification using evidence-based analysis. Use when: verifying claims, checking facts, identifying misinformation, evaluating source credibility, or when user asks to "fact check", "verify", "is this true", or mentions claims that need validation.

fullstack-developer

Modern web development expertise covering React, Node.js, databases, and full-stack architecture. Use when: building web applications, developing APIs, creating frontends, setting up databases, deploying web apps, or when user mentions React, Next.js, Express, REST API, GraphQL, MongoDB, PostgreSQL, or full-stack development.

meeting-notes

Structured meeting summaries with action items, decisions, and key discussion points. Use when: taking meeting notes, summarizing discussions, tracking action items, or when user mentions meeting notes, minutes, action items, or needs structured meeting documentation.

python-expert

Senior Python developer expertise for writing clean, efficient, and well-documented code. Use when: writing Python code, optimizing Python scripts, reviewing Python code for best practices, debugging Python issues, implementing type hints, or when user mentions Python, PEP 8, or needs help with Python data structures and algorithms.

sprint-planner

Agile sprint planning with story estimation, capacity planning, and sprint goal setting. Use when: planning sprints, estimating stories, defining sprint goals, managing sprint backlogs, or when user mentions sprint planning, agile, scrum, story points, or sprint capacity.

strategy-advisor

High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.

technical-writer

Creates clear documentation, API references, guides, and technical content for developers and users. Use when: writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly.

ux-designer

Expert UX design assistance for user research, wireframing, prototyping, and design strategy. Use when: creating wireframes, conducting user research, building prototypes, designing user flows, writing UX copy, reviewing designs for usability, creating personas, planning usability tests, or when user mentions UX design, user experience, wireframes, prototypes, user research, information architecture, or design systems.

visualization-expert

Chart selection and data visualization guidance for effective data communication. Use when: creating visualizations, choosing chart types, designing dashboards, or when user mentions data visualization, charts, graphs, or needs help presenting data visually.

Skills associés