planner

Creates detailed implementation plans from supplied requirements and project scope.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/fx/skills --skill planner-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/fx/skills/tree/main/skills/planner
Command: npx skills add https://github.com/fx/skills --skill planner-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature request into an actionable implementation plan is where scope creep and ambiguity most often creep in. This Skill produces structured, step-by-step implementation plans that trace every task back to the original request, so developers can execute without guessing. ## Core Features & Use Cases - Scope-Disciplined Planning: Works from a Scope Brief or the user's own words, keeping adjacent improvements in a separate out-of-scope list instead of inflating the plan. - Structured Plan Output: Generates plans with architecture, technology stack, phased task breakdowns, testing strategy, risk assessment, and success criteria. - Boundary Escalation: Stops and flags when the request implies materially more work than stated, delivering the in-scope plan plus the cheapest path forward. - Use Case: Given a GitHub issue describing a new API endpoint, produce a phased plan with per-task files, dependencies, and tests that any developer on the team can implement directly. ## Quick Start Ask the planner skill to create an implementation plan for the feature described in this requirements document, following the conventions in the repository's AGENTS.md.

Frequently Asked Questions about planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan from a feature request?▼

Supply the requirements, scope, and any acceptance criteria, and the planner produces a structured plan with architecture, phased tasks, file-level details, dependencies, and testing strategy. Each task includes completion criteria so any developer can execute it.

How to prevent scope creep in software implementation plans?▼

The planner enforces scope discipline by tracing every step to the original request or an approved change document. Adjacent improvements are placed in a separate out-of-scope list rather than the numbered plan steps.

What should a good implementation plan include?▼

A complete plan covers high-level architecture, technology stack, design patterns, phased task breakdowns with files and dependencies, unit/integration/e2e testing strategy, risk assessment with mitigations, and a success criteria checklist.

Does the planner work with existing codebase conventions?▼

Yes, it reads project conventions from AGENTS.md files and existing code patterns before planning. Plans favor extending existing utilities and maintaining backward compatibility over introducing new patterns.

What happens when a request implies more work than stated?▼

The planner stops and tells the user when planning reveals unnamed subsystems, migrations, or architectural decisions beyond the request. It still delivers the in-scope plan and states the cheapest path forward for the larger work.