Project Planning

VerifiedSafe

Creates detailed step-by-step implementation plans with acceptance criteria, exclusive to the planner agent. Leverages MCP helpers like Gemini-Bridge and Context7 for architecture analysis and documentation lookup. Supports PHP/Laravel and Python stacks with independently testable phases and risk matrices.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude Code
#project-planning#implementation-plans#acceptance-criteria#mcp#architecture

Recommended for

Our review

This skill creates detailed implementation plans with testable phases, estimates, and acceptance criteria, using MCP helpers for architecture and documentation research.

Strengths

  • Clear structure with independent, testable phases
  • Integrates architecture research via MCP helpers (Gemini, Context7)
  • Provides estimation techniques (T-shirt sizing) and risk matrix

Limitations

  • Exclusive to the planner agent, not directly usable in other contexts
  • Requires MCP tools to be configured and accessible
  • Estimates remain approximate and depend on actual complexity
When to use it

Use this skill to break down a complex feature into manageable tasks with clear milestones and acceptance criteria.

When not to use it

Avoid this skill for simple fixes or trivial changes that do not require structured planning.

Security analysis

Safe
Quality score90/100

The skill instructs the planner agent to create implementation plans using MCP tools for research and documentation lookup. It does not execute destructive or exfiltrating commands; the use of Bash is only for suggested verification commands within the plan template, with no actual execution risk.

No concerns found

Examples

New settings page
Plan a new settings page for the Laravel app with Inertia.js, including fields for user profile, notifications, and privacy. Use MCP helpers to research existing patterns.
Safe column migration
Create a migration plan for adding a column safely to the users table, with rollback steps and risk mitigation.
Feature implementation plan
Plan the implementation of a two-factor authentication feature, breaking it down into phases with estimates and acceptance criteria.

name: project-planning description: Create clear, step-by-step implementation plans with acceptance criteria using MCP helpers. EXCLUSIVE to planner agent. allowed-tools: Read, Grep, Glob, Bash, mcp_gemini-bridge, mcp_open-bridge, mcp_codex-bridge, mcp_context7

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

| Size | Hours | Complexity | |------|-------|------------| | XS | 1-2 | Single file | | S | 2-4 | Few files | | M | 4-8 | Multiple files | | L | 1-2 days | Multiple components | | XL | 3-5 days | Full feature |

Risk Multipliers

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

Risk Matrix

| Level | Criteria | Mitigation | |-------|----------|------------| | πŸ”΄ High | Data loss, security, breaking | Rollback plan, staging | | 🟑 Medium | Performance, UX regression | Feature flag | | 🟒 Low | Cosmetic, refactor | Standard 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"
Related skills