plan

Decompose complex implementation requests into master plans and phase files.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill plan-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/linenoize/topia/tree/main/skills/plan
Command: npx skills add https://github.com/linenoize/topia --skill plan-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps AI coding assistants handle complex work without losing structure, context, or quality. It breaks large requests into clear plans so implementation can proceed safely across sessions and multiple files.

Core Features & Use Cases

  • Master plan creation: Produces a concise overview that defines the feature, phases, risks, and key decisions.
  • Phase file generation: Writes self-contained execution instructions for each phase so even a weaker model can implement them reliably.
  • Workflow discipline: Supports planning modes for implementation, feature specs, and roadmaps, with test coverage, dependency tracking, and explicit acceptance criteria.
  • Use Case: A team asks for a multi-file feature change, and this Skill turns the request into a phased rollout with tests, dependencies, and execution handoff.

Quick Start

Use the plan skill to convert your complex engineering request into a master plan with phase files.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan multi-file feature changes for AI coding workflows?

Breaking large requests into phased execution involves creating a master plan that defines phases, risks, and key decisions, then generating self-contained phase files for each step. This structure preserves context across session-spanning engineering tasks and multiple files.

What is phase file generation in project management?

Phase file generation writes self-contained execution instructions for each implementation phase so even a weaker AI model can implement them reliably. It enforces workflow discipline by requiring explicit phase breakdowns, test tasks, and acceptance criteria.

How do I break down cross-module architecture changes into executable phases?

To break down cross-module changes, you create a concise overview defining the feature, phases, risks, and key decisions, then split the work into dependency-aware, self-contained instructions. This ensures safe implementation across sessions.

Does TDD workflow planning work for session-spanning engineering tasks?

TDD workflow planning works for session-spanning engineering tasks by integrating test coverage and dependency tracking directly into the master plan and phase files. This allows implementation to proceed safely across multiple sessions without losing structure.

When do I need to decompose a complex implementation request into a master plan?

You need to decompose a complex implementation request into a master plan when handling multi-file features, cross-module changes, or tasks requiring phased execution. It prevents AI coding assistants from losing structure, context, or quality during complex work.