Requirements Extraction — Reverse Engineering Phase 3

Extract system requirements from source code and logic diagrams using EARS notation. This skill reads targets from manifest.json (populated by Phase 2) and implements internal Doer/Critic verification within a single execution.

Three Principles

1. Code is Truth

• Requirements reflect ACTUAL code behavior, not intended behavior
• Bugs are documented as requirements with note: [Suspected Bug]
• Separate As-Is requirements from Question List

2. Traceability to Line

• Every requirement MUST cite file:line reference
• Requirements without evidence are rejected as hallucination

3. Behavior over Intent

• Requirements describe observable behavior: input → output, side effects
• Use concrete values from code (e.g., "retry 3 times", not "retry several times")