r2-req-page

Extract page-level requirements from module context into requirement.page.md and page.yaml.

2|1|Updated Nov 20, 2025

Search Tags:#workflow #documentation #specification #requirements #yaml #page #module-context

Ready to run

npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill r2-req-page

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Extracts page-level requirements from module context (requirement.module.md) and associated inputs (metadata.yaml, API definitions, schemas, and design specs).
Outputs per-page artifacts: requirement.page.md (in Simplified Chinese) and page.yaml for lifecycle orchestration.
Use Case: When starting a new module-driven page, run this skill to automatically produce a ready-to-implement page spec and lifecycle configuration.

Quick Start

Generate a page requirements document from the module context.

Frequently Asked Questions about r2-req-page

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

FAQPage Schema

How do I extract page-level requirements from a module specification?▼

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.

What is the best way to generate requirement.page.md and page.yaml for module-driven projects?▼

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.

Do I need API definitions and schemas to generate page requirement documents?▼

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.

Can I use design specs as optional inputs for page requirements extraction?▼

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.

Why does page requirement documentation lag behind module specifications?▼

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.

Does the generated page.yaml support lifecycle orchestration for module-driven pages?▼

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.