requirements-discover

Recover a requirements.yaml from code (the requirements-yaml format skill defines the file; follow its grammar and review checklist). The job is to read what the system does and write it back as requirements — honestly flagging what the code cannot tell you.

The two clauses recover unevenly

• capability — in the code, sharpened by the tests. Read the behavior off the surface: HTTP routes, public API, CLI commands, UI actions, scheduled jobs, event handlers. Then read its tests: the limits they assert — the expiry window, the rejected input, the measured budget — belong in the capability, because it is the acceptance criterion. No test for a behavior? State the limits the code visibly enforces, and note the coverage gap.
• so that — usually NOT in the code. Rationale and business value are rarely recoverable. Infer your best guess and mark it [?] (the format's provisional marker) for a human to confirm. Never fabricate confident rationale.