longrun-mvp-builder

Preserve LongRun MVP scope and CLI-only focus during development.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/ashiqcodeleaf/long-Run-Agents --skill longrun-mvp-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: longrun-mvp-builder
Source: https://github.com/ashiqcodeleaf/long-Run-Agents/tree/main/skills/software-development/longrun-mvp-builder
Command: npx skills add https://github.com/ashiqcodeleaf/long-Run-Agents --skill longrun-mvp-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps maintain the LongRun project's MVP scope by providing guidelines for development and ensuring the preservation of key features.

Core Features & Use Cases

  • CLI-Only Focus: Preserves the CLI-only nature of LongRun, ensuring a streamlined user experience.
  • Feature Preservation: Keeps essential features like sessions, prompt caching, and local tools.
  • Exclusion of Non-MVP Features: Excludes gateway platforms, desktop apps, and other non-MVP elements.
  • Development Guidelines: Provides a structured approach to modifying the LongRun project.

Quick Start

Before modifying LongRun, use the longrun-mvp-builder skill to review the development guidelines and ensure you're aligned with the MVP scope.

Frequently Asked Questions about longrun-mvp-builder

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

FAQPage Schema
How do I maintain MVP scope when adding new features to a CLI project?

To maintain MVP scope in a CLI project, use development guidelines that preserve essential features like sessions and prompt caching while explicitly excluding non-MVP elements such as desktop apps or gateway platforms.

What development guidelines should I follow to preserve MVP scope in a CLI application?

Development guidelines for preserving MVP scope require testing new behaviors and ensuring modifications adhere to the CLI-only focus, retaining core features like local tools and prompt caching without introducing non-MVP elements.

Does adding a desktop app interface break the MVP scope of a CLI-only project?

Yes, adding a desktop app interface breaks the MVP scope of a CLI-only project. The MVP scope explicitly excludes desktop apps and gateway platforms to ensure a streamlined CLI user experience.

Why are sessions and prompt caching considered essential features in an MVP CLI project?

Sessions and prompt caching are considered essential MVP features because they maintain the core CLI functionality and streamlined user experience. The guidelines ensure these local tools are preserved during development modifications.

Can I integrate gateway platforms into my CLI project without losing MVP scope?

No, you cannot integrate gateway platforms without losing MVP scope. The development guidelines explicitly exclude gateway platforms and other non-MVP elements to preserve the CLI-only focus and essential feature set.

What is the best way to modify a CLI project while preserving its local tools and sessions?

The best way to modify a CLI project while preserving local tools and sessions is to review development guidelines before making changes, ensuring all new behaviors are tested and aligned with the MVP scope.