Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.
.claude/skills/aiskillstore-project-planner/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | 132% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 54% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 55% | 0% |
| case-18 | ✗→✓ | ▲ Improved | 100% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 171% | 0% |
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):
markdown## 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) / 6Break 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
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-09 | fail→pass | 9,999 | 9,224 | -8% | 1 | 1 | 0% | 1,773 | 4,105 | +132% | 0 | 0 | — |
case-01 | fail→fail | 36,613 | 36,334 | -1% | 1 | 1 | 0% | 8,335 | 6,731 | -19% | 0 | 0 | — |
case-02 | fail→fail | 33,892 | 27,340 | -19% | 1 | 1 | 0% | 7,024 | 7,310 | +4% | 0 | 0 | — |
case-03 | fail→fail | 37,930 | 21,513 | -43% | 1 | 1 | 0% | 8,335 | 6,754 | -19% | 0 | 0 | — |
case-04 | pass→fail | 21,196 | 18,938 | -11% | 1 | 1 | 0% | 3,298 | 6,721 | +104% | 0 | 0 | — |
case-05 | pass→pass | 13,553 | 15,348 | +13% | 1 | 1 | 0% | 2,172 | 5,104 | +135% | 0 | 0 | — |
case-06 | pass→fail | 12,645 | 18,047 | +43% | 1 | 1 | 0% | 2,628 | 5,698 | +117% | 0 | 0 | — |
case-07 | fail→fail | 17,454 | 17,495 | +0% | 1 | 1 | 0% | 2,594 | 5,558 | +114% | 0 | 0 | — |
case-08 | pass→pass | 5,550 | 4,406 | -21% | 1 | 1 | 0% | 1,172 | 3,285 | +180% | 0 | 0 | — |
case-10 | fail→fail | 10,725 | 10,377 | -3% | 1 | 1 | 0% | 1,918 | 4,337 | +126% | 0 | 0 | — |
case-11 | fail→pass | 12,516 | 9,702 | -22% | 1 | 1 | 0% | 2,516 | 3,875 | +54% | 0 | 0 | — |
case-12 | fail→fail | 9,175 | 7,818 | -15% | 1 | 1 | 0% | 1,673 | 3,873 | +132% | 0 | 0 | — |
case-13 | fail→fail | 14,398 | 17,648 | +23% | 1 | 1 | 0% | 2,574 | 5,258 | +104% | 0 | 0 | — |
case-14 | fail→pass | 20,919 | 19,647 | -6% | 1 | 1 | 0% | 3,943 | 6,125 | +55% | 0 | 0 | — |
case-15 | pass→pass | 14,048 | 11,742 | -16% | 1 | 1 | 0% | 2,318 | 4,460 | +92% | 0 | 0 | — |
case-16 | pass→pass | 9,058 | 9,169 | +1% | 1 | 1 | 0% | 1,619 | 4,039 | +149% | 0 | 0 | — |
case-17 | pass→pass | 12,084 | 9,972 | -17% | 1 | 1 | 0% | 2,226 | 4,265 | +92% | 0 | 0 | — |
case-18 | fail→pass | 9,335 | 5,730 | -39% | 1 | 1 | 0% | 1,639 | 3,284 | +100% | 0 | 0 | — |
case-19 | fail→pass | 8,067 | 8,732 | +8% | 1 | 1 | 0% | 1,455 | 3,941 | +171% | 0 | 0 | — |
case-20 | pass→pass | 11,233 | 14,710 | +31% | 1 | 1 | 0% | 1,836 | 4,048 | +120% | 0 | 0 | — |
case-21 | fail→fail | 17,471 | 47,347 | +171% | 1 | 1 | 0% | 3,052 | 5,388 | +77% | 0 | 0 | — |
case-22 | pass→pass | 8,617 | 32,191 | +274% | 1 | 1 | 0% | 1,561 | 2,788 | +79% | 0 | 0 | — |
case-23 | pass→pass | 11,016 | 12,542 | +14% | 1 | 1 | 0% | 2,023 | 4,712 | +133% | 0 | 0 | — |
case-24 | pass→pass | 13,877 | 14,196 | +2% | 1 | 1 | 0% | 2,246 | 4,742 | +111% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 24 cases were attempted. The headline lift of +13 percentage points is the difference between those two pass rates over the 24 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
| Model | Method | Date | Lift |
|---|---|---|---|
| gemini-3.6-flash | verified | 8/21/2026 | +82% |
Other measured skills in the registry, with their headline benchmark lift.