functional-testcases — functional test-case catalog

Turn the approved design into a functional test-case catalog: black-box cases derived from observable behavior (the acceptance criteria + the contract's operations), not from the implementation. Each case is a plain-language spec a human can execute by hand and that /qa later automates. Write cases only; never edit app code.

When to use / not use

• Use in the design phase, after /api-contract — once the contract and acceptance criteria exist and the HLD is approved. It closes the design phase and seeds QA.
• Don't write automation code or framework specs (that's /qa), and don't derive cases from internals — a case must be justified by an acceptance criterion or a contract operation.