One-click install
npx skills add https://github.com/ahostbr/liteharness --skill ls-arch-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-arch-gen
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-arch-gen
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-arch-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the effort of manually mapping a codebase into understandable architecture documentation by scouting the project and producing structured, navigation-friendly docs.

Core Features & Use Cases

  • Automated codebase scouting: Dispatches parallel scout agents (e.g., structure, entry points, APIs/protocols, data, and features) to gather the information needed for documentation.
  • Structured architecture output: Writes an architecture documentation set under docs/architecture/ including an INDEX.md plus one file per major subsystem/module.
  • Update-friendly workflow: Rewrites stale sections and refreshes INDEX.md, including backing up prior documentation when updating.

Quick Start

Ask an agent to run the ls-arch-gen skill on your project to generate updated architecture documentation with an INDEX.md.

Frequently Asked Questions about ls-arch-gen

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

FAQPage Schema
How do I generate architecture documentation for an existing codebase?

To generate architecture documentation, an agent scouts your project in parallel for structure, entry points, APIs, and data models, then transforms findings into structured Markdown deliverables under docs/architecture/.

What is the best way to update outdated architecture notes?

Updating outdated architecture notes is handled by rewriting stale sections and refreshing the INDEX.md file, which includes backing up prior documentation to prevent data loss.

Can I use this to create subsystem breakdowns for any software stack?

Yes, subsystem breakdowns apply to any software stack, producing one Markdown file per major module alongside an INDEX.md to organize the architecture documentation set.

How does automated codebase scouting work for architecture docs?

Automated codebase scouting works by dispatching parallel scout agents to gather information across structure, entry points, APIs/protocols, data, and features for comprehensive documentation.

Do I need to manually index project modules before generating architecture docs?

No manual project indexing is required, as the skill autonomously scouts the codebase structure and generates an INDEX.md plus module docs within the docs/architecture/ directory.