make-scenarios

To generate user scenarios from a feature plan, you provide the plan or codebase and specify a perspective like end-user capability or developer extensibility. The tool then outputs structured statements describing what an actor wants to achieve.

Perspective-driven scenarios in requirements analysis are structured statements describing what a specific actor wants to do with a target. They are generated by applying specific lenses like security posture or operator workflow to a codebase or plan.

Extract use cases from a codebase by analyzing the material through a chosen lens like developer extensibility or operator workflow. The process surfaces use cases and extension points formatted as actor-action-target statements grounded in codebase evidence.

Yes, you can analyze security posture and operator workflows from a feature description by setting these as your desired perspective. The analysis will generate scenarios that frame what security or operator actors want to achieve based on the provided material.

No, scenario generation does not prescribe technical solutions for the analyzed plan. It strictly frames a specific actor, action, and target without prescribing a solution, serving purely as input for downstream requirements and design discussions.

The best way to structure actor-action-target statements for software planning is framing them as what an actor wants to do to a target. This grounds each scenario in evidence from the analyzed material and surfaces specific extension points.