Lotea
Official@lotea-be
Offers structured governance for QRSPI-based development, managing end-to-end vertical slices, OpenSpec documentation, and artifact synchronization across engineering lifecycles.
Agent Skills by Lotea
Showing 9 vetted skills indexed across 1 GitHub repositories.
qrspi-retrospective
Capture QRSPI retrospective friction and propose prompt and process edits.
vertical-slice
Organize feature changes into end-to-end vertical slices with per-slice checkpoints and model annotations.
openspec-workflow
Document and enforce an OpenSpec-backed workflow for QRSPI changes.
qrspi-postpr-fix
Process reviewer issues into followups.md and align delta specifications.
openspec-archive-change
Archive completed OpenSpec workflow changes into date-stamped directories.
context-hygiene
Enforce context budgets and delegate bounded tasks to subagents.
openspec-sync-specs
Merge delta specs into main OpenSpec specs without archiving.
qrspi-workflow
Manage the eight-stage QRSPI workflow from Questions to PR with per-stage artifacts.
qrspi-sync-copilot
Regenerate GitHub Copilot artifacts from Claude Code source mappings.
Frequently Asked Questions About Lotea
FAQPage SchemaWhat specific engineering tasks does Lotea enable?▼
Lotea enables the management of the eight-stage QRSPI process, from initial questioning to pull request submission. It facilitates the creation of vertical slices, enforces OpenSpec documentation standards, manages context budgets for sub-tasks, and ensures synchronization between Claude Code source mappings and GitHub Copilot artifacts.
Which technical personas benefit from Lotea's methodology?▼
Lotea is designed for software engineers, technical leads, and systems architects who require rigorous documentation and process enforcement. It is particularly suited for teams managing complex, multi-stage development cycles who need to maintain strict alignment between code changes, delta specifications, and project-wide documentation standards.
What are the prerequisites for implementing Lotea's processes?▼
Implementation requires an existing QRSPI-based development structure and the adoption of OpenSpec documentation standards. Users must have a repository environment capable of supporting date-stamped archival directories and the ability to map source code artifacts to GitHub Copilot configurations for effective synchronization.