project-planning

Create clear, step-by-step implementation plans with acceptance criteria using MCP helpers. EXCLUSIVE to planner agent.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "project-planning" with this command: npx skills add htooayelwinict/claude-config/htooayelwinict-claude-config-project-planning

Project Planning

Exclusive to: planner agent

MCP Helpers (Brain + Memory)

🧠 Gemini-Bridge (Brain) — Architecture Analysis

mcp_gemini-bridge_consult_gemini(
  query="Design architecture for [feature]: phases, risks, dependencies...",
  directory="."
)

🌉 Open-Bridge — Alternative Architecture Analysis

mcp_open-bridge_consult_gemini(
  query="Design architecture for [feature]: phases, risks, dependencies...",
  directory="."
)

📚 Context7 (Memory) — Documentation Lookup

mcp_context7_resolve-library-id(libraryName="laravel", query="[feature]")
mcp_context7_query-docs(libraryId="/laravel/docs", query="[specific pattern]")

Supported Stacks

PHP/Laravel: Laravel 12, Inertia.js, React 19, TypeScript, Tailwind Python: FastAPI, LangChain, LangGraph, Pydantic, pytest

Instructions

1. Restate Goal

One sentence summary of what we're building.

2. Research

  • Search codebase for similar patterns
  • Identify affected files
  • Note dependencies

3. Break Down

Create 3-5 phases, each independently testable.

Estimation Techniques

T-Shirt Sizing

SizeHoursComplexity
XS1-2Single file
S2-4Few files
M4-8Multiple files
L1-2 daysMultiple components
XL3-5 daysFull feature

Risk Multipliers

  • Database migration: 1.5x
  • Auth/security: 1.5x
  • Third-party: 2x

Risk Matrix

LevelCriteriaMitigation
🔴 HighData loss, security, breakingRollback plan, staging
🟡 MediumPerformance, UX regressionFeature flag
🟢 LowCosmetic, refactorStandard testing

Phase Template

# Phase N: [Name]

## Objective
[What this accomplishes]

## Tasks
- [ ] Task with file path

## Files
| File | Action |
|------|--------|
| `path/file` | Create/Modify |

## Verification
```bash
[commands]

Estimate

[X hours]


## plan.md Output (REQUIRED)

Always create a consolidated `plan.md` file that contains ALL phases and context:

```markdown
# Plan: [Feature Name]

## Context
[What we're building and why]

## Code Patterns to Follow
[Key patterns from codebase research]

## Phases
| # | Name | Objective | Est. |
|---|------|-----------|------|

---

## Phase 1: [Name]
### Objective
[Goal]

### Tasks
- [ ] Task with `path/to/file`

### Files
| File | Action |
|------|--------|

---

[... repeat for each phase ...]

---

## Summary
- **Total Phases**: N
- **Estimated Effort**: X hours
- **Key Risks**: [list]

Examples

  • "Plan a new settings page"
  • "Create a migration plan for adding a column safely"

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

deepagent

No summary provided by upstream source.

Repository SourceNeeds Review
General

bugfix-and-debug

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-review-checklist

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

devops-infrastructure

No summary provided by upstream source.

Repository SourceNeeds Review