Extract page-level requirements from module context into requirement.page.md and page.yaml.
npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill r2-req-page
Please help me install this Agent Skill. Skill: r2-req-page Source: https://github.com/silentbalanceyh/r2mo-lain/tree/main/skills/r2-req-page Command: npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill r2-req-page
Page requirements often lag behind module specifications, causing misalignment between design, APIs, and UI. This skill automates extracting page-level requirements from module context and generates structured documentation that teams can trust.
Generate a page requirements document from the module context.
High-intent search queries and answers about installing and using this skill.
Extracting page-level requirements from a module specification involves parsing module context like requirement.module.md, API definitions, and schemas to generate structured per-page artifacts. This process enforces an 8-section page template for ready-to-implement documentation.
Generating requirement.page.md and page.yaml for module-driven projects requires processing module context and associated metadata.yaml inputs. This automated extraction produces structured page specification documents and lifecycle configuration files trusted by implementation teams.
API definitions and schemas are required inputs to generate accurate page requirement documents. Alongside requirement.module.md and metadata.yaml, they provide the necessary module context to enforce the 8-section page template and output lifecycle configuration.
Design specs can be used as optional inputs for page requirements extraction. Including them alongside mandatory module context, API definitions, and schemas enriches the generated requirement.page.md and page.yaml artifacts with UI alignment details.
Page requirement documentation lags behind module specifications due to manual extraction overhead and misalignment between design, APIs, and UI. Automating the extraction from module context into an 8-section template resolves this synchronization gap.
The generated page.yaml supports lifecycle orchestration for module-driven pages. It is output alongside requirement.page.md to provide structured configuration that teams use to manage the implementation lifecycle of per-page artifacts.
silentbalanceyhExtract module-level requirements from project specifications into template-structured documents.
BurburtonSynchronize architecture documents with implementation changes and generate a traceability report.
tangchunwuGenerate a comprehensive PRD using an 8-section template.
angryconsultantGenerate GitHub issues for unmet requirements extracted from specification files.
