Requirement Doc Review

Overview

Turn rough requirement material into a stable Markdown pack. Keep the formatted file faithful to the source, then write separate review documents for product, architecture, and engineering.

Workflow

1. Stabilize the source.

• Accept a file path, pasted text, or a small set of related requirement files.
• Preserve the source language by default. Translate only when the user asks.
• Process each source document independently unless the user explicitly asks for a merged pack.