lbrlabs
Official@lbrlabs
Offers standardized artifact-driven lifecycle management for software architecture specifications and iterative change implementation.
Agent Skills by lbrlabs
Showing 10 vetted skills indexed across 2 GitHub repositories.
lbrlabsopenspec-explore
Explore software architecture through iterative questioning and OpenSpec artifact generation.
lbrlabsopenspec-onboard
Guides developers through the complete OpenSpec change lifecycle using their own codebase and CLI.
lbrlabsopenspec-verify-change
Validate change implementation against specs, tasks, and design artifacts.
lbrlabsopenspec-bulk-archive-change
Archive multiple completed changes into date-stamped directories using the openspec CLI.
lbrlabsopenspec-continue-change
Generate the next OpenSpec artifact to continue a change workflow.
lbrlabsopenspec-sync-specs
Merge delta specifications into main specs across ADDED, MODIFIED, REMOVED, and RENAMED changes.
lbrlabsopenspec-apply-change
Automate OpenSpec change implementation through CLI-driven task workflows.
lbrlabsopenspec-new-change
Scaffold a new OpenSpec change with a standardized artifact-driven workflow.
lbrlabsopenspec-archive-change
Archive completed OpenSpec changes under openspec/changes/archive with metadata preservation.
lbrlabsopenspec-ff-change
Scaffold all OpenSpec implementation change artifacts in one command.
Frequently Asked Questions About lbrlabs
FAQPage SchemaWhat specific tasks does lbrlabs enable for software architects?▼
Lbrlabs enables the systematic generation, validation, and archiving of architecture specifications. It facilitates iterative exploration of software designs, ensures delta specifications are merged correctly into main documentation, and provides standardized scaffolding for implementation changes to maintain consistency across the development lifecycle.
Which technical personas benefit most from these capabilities?▼
Software architects, lead developers, and technical documentation engineers benefit most from these capabilities. The system is designed for teams requiring rigorous versioning of design artifacts and those needing to enforce standardized change implementation patterns across complex, evolving codebases.
What are the primary prerequisites for implementing these specifications?▼
Implementation requires an existing codebase and familiarity with the OpenSpec artifact structure. Users must maintain their architecture documentation within the specified directory hierarchy to enable the system to perform delta merging, validation, and archival tasks effectively.