Expand one-liner build requests into structured project scope documents.
npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill expand-rcsnyder
Please help me install this Agent Skill. Skill: expand Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/expand Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill expand-rcsnyder
It turns a vague “build this” idea into a structured, agent-ready scope that defines problem context, the smallest useful version, acceptance criteria, stack, deployment target, and the data model.
Run the lo-swe init/expand flow with a one-liner describing your new project, and it will create scaffolding/scope.md containing acceptance criteria, stack, deployment target, and data model.
High-intent search queries and answers about installing and using this skill.
To generate a project scope, you provide a one-liner describing your new software project. The tool reads optional input briefs from docs/input/ and required constraints from preferences.md to create a structured scope document with acceptance criteria, stack, and deployment target.
Converting vague ideas into measurable acceptance criteria involves expanding your one-liner request into a scope document with stable AC-* identifiers. It reads sourced documents and distilled briefs to define verifiable thresholds and clear guardrails for agent execution.
Yes, project scoping works directly with your preferences.md to select stack and deployment target, and reads docs/input/ for briefs and specs. It flags conflicts for resolution when user intent contradicts configured preferences.
Defining the smallest useful version requires deriving a coherent scope from user input and sourced documents. The tool generates scaffolding/scope.md containing problem context, data model, and verifiable acceptance criteria to establish a functional baseline.
Yes, you can use the generated scope document to validate agent progress. It produces scaffolding/scope.md with agent-gated output, stable AC-* IDs, and measurable thresholds so later development phases can verify completion against defined guardrails.
Project scope generation flags conflicts to ensure preferences-aligned planning when user intent contradicts configured preferences. This mechanism prevents architectural mismatches by requiring resolution before finalizing the stack and deployment target in the scope document.
RCSnyderClassify and summarize project input files into distilled reference documents.
RCSnyderConvert scope and design documents into a build-ready readiness checklist with acceptance-criteria traceability.
iyakiGenerate engineering-grade specifications for software features and systems.
X-School-AcademyDefine MVP scope, success metrics, and acceptance criteria for early product validation.
