lo-plan

Transforms unstructured ideas into detailed software implementation plans with backlog integration and EARS requirements generation.

Updated Feb 26, 2026

Search Tags:#planning #workflow automation #feature design #requirements gathering #backlog management #ear

Ready to run

npx skills add https://github.com/looselyorganized/lo-plugin --skill lo-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lo-plan
Source: https://github.com/looselyorganized/lo-plugin/tree/main/plugins/lo/skills/lo-plan
Command: npx skills add https://github.com/looselyorganized/lo-plugin --skill lo-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms raw ideas and conversation fragments into structured, actionable implementation plans, ensuring that projects are well-defined before development begins.

Core Features & Use Cases

Context-Aware Planning: Adapts planning depth based on conversation history, project status, and feature complexity.
Backlog Integration: Creates or updates backlog entries automatically.
Use Case: When you have a new feature idea, use /lo:plan to brainstorm, define requirements (including EARS if needed), and generate a detailed plan file, ready for execution.

Quick Start

Use the lo-plan skill to create a plan for the feature described as "implement user authentication".

Frequently Asked Questions about lo-plan

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

FAQPage Schema

How do I turn unstructured feature ideas into actionable implementation plans?▼

To turn unstructured feature ideas into actionable implementation plans, you can use context-aware planning tools that analyze conversation history and project status to generate structured plan files ready for execution.

How do I generate EARS requirements for software backlog management?▼

Generating EARS requirements for software backlog management involves transforming raw feature ideas into structured conditions, automatically creating or updating backlog entries to ensure projects are well-defined before development begins.

Can I adapt planning depth based on feature complexity and project status?▼

Yes, you can adapt planning depth based on feature complexity and project status. Context-aware planning evaluates conversation history and existing work directories to adjust the detail level of the generated implementation plans.

What is the best way to automate workflow planning for new software features?▼

The best way to automate workflow planning for new software features is to use a skill that transforms conversation fragments into detailed plans, integrates with existing backlogs, and delegates design to specialized agentic superpowers.

Does backlog management integrate with existing project work directories?▼

Yes, backlog management integrates with existing project work directories. The planning process adapts to your current project status, ensuring that automatically generated or updated backlog entries align with your existing work.

When should I not use automated planning for software requirements gathering?▼

You should not use automated planning for software requirements gathering when the feature idea is completely undefined, as the mechanism relies on analyzing conversation context, project status, and feature complexity to generate a detailed plan.