plan

Create phased execution plans for multi-file tasks with overview and phase files.

218|11|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/poteto/noodle --skill plan-poteto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/poteto/noodle/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/poteto/noodle --skill plan-poteto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic planning for medium-to-large tasks. Gathers context, identifies domain skills, writes phased plans to brain/plans/. Does NOT implement. Use for new features, multi-file refactors, or architectural changes — not small fixes.

Core Features & Use Cases

  • Gathers context and requirements before starting work.
  • Identifies and binds domain skills needed for the task.
  • Produces phased execution plans saved to brain/plans/, including an overview and phase files.
  • Serves as a roadmap for implementation without performing changes directly.

Quick Start

Describe the task to be planned and trigger the plan to generate a phased roadmap.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan a multi-file refactor before writing any code?

To plan complex tasks, gather context and constraints to produce a phased execution roadmap saved as overview and phase files. This systematic planning assembles requirements for multi-file refactors or feature rewrites without performing the actual implementation.

What is the best way to create an architectural roadmap for a feature rewrite?

Creating an architectural roadmap involves assembling context and constraints to generate phased execution plans. These plans serve as a roadmap saved to an index, guiding complex feature rewrites across several files without executing changes directly.

When do I need phased execution steps for project management?

Phased execution steps are needed for medium-to-large tasks spanning several files, architectural changes, or new features. You do not need them for small fixes where a formal roadmap and phase files would be unnecessary overhead.

Can I use this planning approach to execute code changes directly?

No, this planning approach does not execute code changes directly. It strictly produces an overview and phase files that serve as a roadmap to guide the implementation of complex, multi-file tasks.

Does systematic planning work for single file bug fixes?

Systematic planning is not designed for single file bug fixes or small fixes. It applies to initiatives spanning several files or modules where a clear, phased roadmap is required to manage complexity.

How do I generate task planning documents for a new feature?

To generate task planning documents, describe the feature task to trigger the plan creation. It assembles context and outputs an overview document alongside phase files that guide the implementation process.