lo-solution

Capture reusable problem-solution pairs with context and tags into .lo/solutions/.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/looselyorganized/lo-plugin --skill lo-solution
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lo-solution
Source: https://github.com/looselyorganized/lo-plugin/tree/main/plugins/lo/skills/lo-solution
Command: npx skills add https://github.com/looselyorganized/lo-plugin --skill lo-solution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of knowledge loss within projects by providing a structured way to capture and store reusable solutions, patterns, and lessons learned.

Core Features & Use Cases

  • Knowledge Capture: Documents solutions to problems encountered during development or project execution.
  • Prior Art Scanning: Integrates with /lo:plan to scan existing solutions, preventing redundant work and accelerating future planning.
  • Use Case: After successfully debugging a complex performance issue, use this skill to document the specific workaround and its context, making it easily discoverable for future similar problems.

Quick Start

Use the lo-solution skill to capture what you learned about the new caching strategy.

Frequently Asked Questions about lo-solution

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

FAQPage Schema
How do I capture reusable solutions and lessons learned during a project?▼

To capture reusable solutions, document the problem-solution pairs and context encountered during project execution into a structured format within the .lo/solutions/ directory. This prevents knowledge loss by making lessons learned easily discoverable for reuse across future projects.

What is the best way to document project knowledge for team reuse?▼

The best way to document project knowledge is to record problem-solution pairs alongside their specific context and relevant tags. Storing these structured entries in a dedicated .lo/solutions/ directory facilitates knowledge sharing and accelerates reuse across projects.

How does prior art scanning prevent redundant work in software engineering?▼

Prior art scanning prevents redundant work by integrating with planning workflows to scan existing documented solutions. It checks the .lo/solutions/ directory for previously captured problem-solution pairs, accelerating future planning and preventing duplicate debugging efforts.

Can I use lo-solution to document a complex debugging workaround?▼

Yes, you can use lo-solution to document a complex debugging workaround. After successfully resolving a performance issue, the skill captures the specific workaround and its context into the .lo/solutions/ directory, making it easily discoverable for future similar problems.