BRICK stage 1. Turns an approved task list into pruned Gherkin `.feature` files: one scenario per distinct behaviour, written in the language of the domain rather than the language of the implementation.
Prunes redundancy aggressively, because every surviving scenario becomes acceptance tests, property tests, and mutation targets downstream.
Refuses to invent behaviour the tasks do not state. Produces `.feature` files and nothing else — no tests, no code.
Harness-layer BRICK stage skill with clean stratified disclosure. Always activate together with `code-writer`.
