lo-setup

Scaffold the `.lo/` directory with configuration files and subdirectories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of the essential .lo/ directory structure and configuration files required for any new project managed by the LO Work System.

Core Features & Use Cases

  • Project Initialization: Sets up project.yml, BACKLOG.md, and STREAM.md.
  • Directory Structure: Creates necessary subdirectories like park/, work/, and solutions/.
  • Use Case: When starting a new project, use this Skill to quickly establish the foundational LO structure, ensuring all subsequent LO commands function correctly from the outset.

Quick Start

Run the lo-setup skill to initialize a new LO project in the current directory.

Frequently Asked Questions about lo-setup

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

FAQPage Schema
How do I set up the initial directory structure for a new project workflow?

Project initialization scripts scaffold the `.lo/` directory convention in your repository root, generating `project.yml`, `BACKLOG.md`, and `STREAM.md` alongside `park/`, `work/`, and `solutions/` directories.

What files do I need to create for project initialization to ensure workflow commands function correctly?

For project initialization, you need `project.yml`, `BACKLOG.md`, and `STREAM.md` with essential metadata and counters. Automating this scaffolding ensures all subsequent LO commands function correctly from the outset.

Does project setup work with existing GitHub automation scripts?

Yes, project setup can optionally reconcile GitHub automation scripts during the initialization process. This ensures your newly scaffolded `.lo/` directory and configuration files integrate smoothly with existing automation.

When do I need to run project scaffolding for my repository?

You need to run project scaffolding when starting a new project to quickly establish the foundational `.lo/` structure. This creates the necessary subdirectories and metadata files required for the system to manage your work.

Can I manually create the backlog and stream files instead of using a scaffolding tool?

You can manually create `BACKLOG.md` and `STREAM.md`, but using a scaffolding tool ensures the correct metadata and counters are established. It also guarantees the `park/`, `work/`, and `solutions/` directories are created properly to support subsequent commands.