plan

Generate structured implementation plans with goals, phases, risks, and scope boundaries.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lostsolution/makelele --skill plan-lostsolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/lostsolution/makelele/tree/main/skill-graph/skills/plan
Command: npx skills add https://github.com/lostsolution/makelele --skill plan-lostsolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users create structured implementation plans for their tasks by breaking them down into actionable phases and identifying potential cross-domain risks.

Core Features & Use Cases

  • Structured Planning: Generates a detailed plan with goals, affected domains, phases, risks, and scope boundaries.
  • Constraint Adherence: Ensures plans respect injected domain constraints from /skill-graph:context.
  • Use Case: A project manager needs to outline the steps for integrating a new feature. They can use this Skill to generate a plan that accounts for dependencies and potential conflicts with existing systems.

Quick Start

Use the plan skill to create an implementation plan for the user's request.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an implementation plan for a multi-domain project?

To generate an implementation plan, provide a description of your work and any injected domain constraints. The output is a structured plan covering goals, affected domains, phases, cross-domain risks, and scope boundaries.

What is the best way to break down project tasks and map dependencies?

Task breakdown and dependency mapping are handled by generating a structured implementation plan that decomposes work into actionable phases. This approach addresses project management needs by identifying cross-domain risks and defining clear scope boundaries.

Can I include specific domain constraints when creating a project plan?

Yes, specific domain constraints can be injected into the planning process. The generated implementation plan adheres to these constraints to ensure that task decomposition and risk assessment respect your project's multi-domain requirements.

How do I identify cross-domain risks during project planning?

Identifying cross-domain risks is achieved by generating a structured implementation plan. The output explicitly highlights potential conflicts and risks across affected domains alongside task phases and scope boundaries.

What format does the generated implementation plan follow?

The implementation plan follows a specific structured output format that includes Goal, Affected domains, Phases, Cross-domain risks, and Scope boundary. This structure ensures comprehensive coverage of task decomposition and risk assessment.

When do I need a structured implementation plan instead of a simple task list?

A structured implementation plan is needed for multi-domain projects that require task decomposition, dependency mapping, and risk assessment. It provides phases, cross-domain risk identification, and scope boundaries that a simple task list lacks.