Planification de Projet

VérifiéSûr

Crée des plans d'implémentation détaillés avec des critères d'acceptation pour un agent planner. Utilise des helpers MCP comme Gemini-Bridge et Context7 pour analyser l'architecture et rechercher de la documentation. S'applique notamment aux stacks PHP/Laravel et Python avec phases testables indépendamment et matrice de risques.

Spar Skills Guide Bot
DeveloppementIntermédiaire
7002/06/2026
Claude Code
#project-planning#implementation-plans#acceptance-criteria#mcp#architecture

Recommandé pour

Notre avis

Ce skill génère des plans d'implémentation détaillés avec des phases testables, des estimations et des critères d'acceptation, en utilisant des assistants MCP pour la recherche d'architecture et de documentation.

Points forts

  • Structure claire en phases indépendantes et testables
  • Intègre des recherches d'architecture via des assistants MCP (Gemini, Context7)
  • Fournit des techniques d'estimation (T-shirt sizing) et une matrice de risque

Limites

  • Exclusif à l'agent planner, non utilisable directement dans d'autres contextes
  • Nécessite que les outils MCP soient configurés et accessibles
  • Les estimations restent approximatives et dépendent de la complexité réelle
Quand l'utiliser

Utilisez ce skill pour décomposer une fonctionnalité complexe en tâches gérables avec des jalons clairs et des critères d'acceptation.

Quand l'éviter

Évitez ce skill pour des corrections simples ou des changements triviaux qui ne nécessitent pas de planification structurée.

Analyse de sécurité

Sûr
Score qualité90/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.

Aucun point d'attention détecté

Exemples

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"
Skills similaires