plan

Plan architecture and implementation steps for complex multi-file projects.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/xjiang77/agent-wisp --skill plan-xjiang77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/xjiang77/agent-wisp/tree/main/tools/setup-toolkit/skills/plan
Command: npx skills add https://github.com/xjiang77/agent-wisp --skill plan-xjiang77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to architecture and implementation planning for complex tasks and multi-file projects, turning vague goals into actionable roadmaps.

Core Features & Use Cases

  • Structured planning workflow: Understand requirements, explore code, design solutions, and decompose tasks.
  • Deterministic task planning: Map dependencies and interfaces across a codebase to construct a coherent plan.
  • Collaborative alignment: Present decisions and milestones to stakeholders for confirmation and alignment.

Quick Start

Define a plan for implementing a feature that touches multiple files or services to obtain a clear execution path.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan architecture and implementation steps for multi-file projects?▼

Plan architecture for complex tasks by applying a structured workflow that elicits requirements, explores the codebase, proposes designs, and decomposes tasks with dependencies to present a structured execution plan.

When do I need task decomposition for software architecture planning?▼

Task decomposition is needed when a task touches 5 or more files, involves multiple systems, or requires design decisions and stakeholder alignment to turn vague goals into actionable deterministic roadmaps.

What is the best way to map dependencies across a codebase for project planning?▼

Mapping dependencies across a codebase requires deterministic task planning that explores code to identify interfaces, mapping dependencies to construct a coherent plan for stakeholder confirmation and alignment.

Can I use this planning workflow for feature implementation touching multiple services?▼

Yes, this planning workflow is suitable for feature implementation touching multiple services or files, as it provides a structured approach to elicit needs, explore code, design solutions, and present milestones.

How does code exploration fit into the architecture planning process?▼

Code exploration fits into architecture planning by enabling the tool to understand existing requirements, map interfaces, and propose design solutions before decomposing tasks into a structured execution plan.