plan

Generate structured markdown implementation plans for software development tasks.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill plan-layerdynamics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/plan
Command: npx skills add https://github.com/LayerDynamics/Lore --skill plan-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating detailed, bite-sized implementation plans for software development tasks, ensuring clarity and adherence to best practices.

Core Features & Use Cases

  • Guided Planning: Walks users through defining task scope, development practices, and required skills.
  • Structured Output: Generates markdown plans with clear goals, architecture, tech stack, and task breakdowns.
  • Use Case: Before starting a new feature, use this skill to generate a plan that includes TDD, specifies the exact files to modify, and provides step-by-step code implementation and testing instructions.

Quick Start

Use the plan skill to create an implementation plan for adding user authentication.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a structured implementation plan for a software development task?

To create a structured implementation plan, you need to define the task scope, development practices, and required skills. This process generates a markdown plan with clear goals, architecture, tech stack, and bite-sized task breakdowns for software development.

What is a structured implementation plan and when do I need one?

A structured implementation plan is a markdown document detailing bite-sized execution steps for software development. You need one before starting a new feature to ensure clarity, define task scope, and adhere to best practices like TDD and contract-first development.

Can I generate a TDD execution plan that specifies exact files to modify?

Yes, you can generate a TDD execution plan that specifies exact files to modify. By querying you for development practices and inclusions, the planning process outputs step-by-step code implementation and testing instructions tailored to your project context.

What's the best way to break down a complex feature into bite-sized development tasks?

The best way to break down a complex feature is to use a guided planning workflow that reads project context and queries you for inclusions. This produces a structured markdown plan with clear goals, architecture, and bite-sized task breakdowns for execution.

Does the planning process support typed interfaces and contract-first development?

Yes, the planning process supports typed interfaces and contract-first development. It queries you for specific development practices and inclusions, ensuring the generated markdown plan adheres to your chosen architectural standards and testing methodologies.

Why should I generate a markdown plan before starting a new software feature?

You should generate a markdown plan to streamline the process of creating detailed implementation steps. It ensures clarity and adherence to best practices by defining task scope, architecture, and tech stack before writing any code, reducing development friction.