MRD Requirements Content Generation
Based on the business context, current status, and change requirements provided by the user, organizes the content into MRD-ready requirements.
Default Output Structure
Each interface retains only the following three sections:
- Core Logic
- Detail List
- Filter Options
Unless explicitly requested by the user, do not add independent sections such as "Add/Edit Fields," "Permissions and Logs," "Pending Items," or "Acceptance Criteria." Necessary rules should be merged into the core logic section.
Writing Rules
- The core logic should cover key business rules, uniqueness, data sources, batch operations, import validations, error feedback, permissions, and notification deduplication, while remaining concise.
- Do not treat simple control changes as complete requirements; explain the impact on data relationships and business processes.
- Do not generate interface diagrams or invent specific page positions when the actual interface layout is unknown.
- Only describe features confirmed by the user. Do not reintroduce fields or operations that the user explicitly deleted.
- Organizational structure fields should prioritize stable codes as association identifiers; names are used for display.
- Personnel should be identified using unique identifiers such as JMS IDs, not relying solely on names.
- For deletions, batch operations, and imports, describe confirmation steps, validations, and success or failure feedback.
Table Format
Detail lists use the following uniform format:
| No. | Field Name | Adjustment Description | List Description | Remarks | |---|---|---|---|
Filter options use the following uniform format:
| No. | Field Name | Adjustment Description | Filter Description | Remarks | |---|---|---|---|
Each "Filter Description" must specify:
- Control type
- Whether multi-select is allowed
- Default value
Based on the field type, supplement the query method, data source, options, or cascading relationships.
Confirmed Baseline
When requirements involve "Site Arbitration Notifier Configuration," the skill must read and follow references/site-arbitration-notifiers.md. The fields, deletions, and business definitions in that file are considered the current confirmed version.
Document Output
- When the user says "discuss content only," output only a content draft without generating a DOCX file.
- Only when the user explicitly requests a Word document should the skill combine the specified template and use document generation tools with formatting checks.
- When the user requests modifications, only modify the parts they indicate, while synchronously cleaning up affected fields, filter options, and logical descriptions to avoid inconsistencies.