lo-stream

Creates public milestone entries in .lo/STREAM.md from manual input or git history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you maintain a clear, public-facing narrative of your project's significant achievements, ensuring stakeholders and the community are informed about key developments.

Core Features & Use Cases

  • Milestone Tracking: Capture and log important project milestones, such as feature releases, architectural changes, or research findings.
  • Public Narrative: Formulate entries suitable for public consumption, appearing on project pages or social media.
  • Use Case: After successfully shipping a major new feature, use this Skill to create a concise, impactful milestone entry that highlights the achievement and its benefits.

Quick Start

Use the lo-stream skill to add a new milestone entry with the title "Launched public API documentation".

Frequently Asked Questions about lo-stream

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

FAQPage Schema
How do I create a public project log for milestones and release notes?

You can document project milestones by generating public entries in .lo/STREAM.md, which captures significant events and achievements for public view. The skill formulates entries suitable for public consumption and prepends them after any YAML frontmatter.

Can I scan git history to find candidates for project milestone entries?

Yes, you can scan git history to find candidates for project milestone entries. The skill supports scanning git history, manual entry, and generating entries post-shipment to document significant events for your public narrative.

What is the best way to maintain a public narrative of project achievements?

The best way to maintain a public narrative is logging project milestones in .lo/STREAM.md. This ensures stakeholders and the community are informed about key developments like feature releases, architectural changes, or research findings.

Does the milestone tracking process enforce quality checks for public-facing content?

Yes, the milestone tracking process enforces a quality gate for public-facing content. This ensures that entries added to STREAM.md are suitable for public consumption before being prepended to the file.

How do I document a major feature release in a project log after shipping?

You can document a major feature release post-shipment by generating a concise, impactful milestone entry in .lo/STREAM.md. The skill highlights the achievement and its benefits for stakeholders.