use-case-writer

You can generate structured use-case packets automatically by providing a declared source brief, issue, demo, or milestone context to the use-case-writer. It transforms the brief into grounded artifacts containing actors, use cases, acceptance hooks, and non-goals.

A grounded use-case packet is a structured artifact containing actors, user goals, system behavior, and unsupported assumptions aligned with the adl use_case_packet schema. You need one for product, feature, or milestone contexts requiring reviewer-anchored governance and evidence trails.

To document unsupported assumptions and non-goals during use-case generation, the use-case-writer explicitly extracts and isolates them within the output packet. This ensures reviewers can immediately identify scope boundaries and unverified constraints from the source brief.

Yes, you can output use-case artifacts in both machine-readable JSON and human-readable Markdown formats. The generation process produces both formats simultaneously while adhering to a defined stop boundary to prevent scope creep.

You define a stop boundary by processing your declared brief through the use-case-writer, which programmatically establishes scope limits within the generated packet. This boundary prevents infinite recursion by explicitly listing non-goals and unsupported assumptions.

Use-case generation works for product, feature, demo, and milestone contexts alike. The transformation applies the adl use_case_packet schema uniformly across any declared source brief to produce reviewer-anchored artifacts with acceptance hooks.