Repository navigation
Release v7.50.0
Summary
The Screenplay skills go deeper on the modeling method, with the most weight on understanding existing systems and turning them into Screenplay models.
Added
- Legacy extraction keeps its analysis history, where each feature lives in the code and the decisions that span a feature as committed model notes, with open assumptions as anchored questions, so re-runs and drift checks have a baseline after the working area is gone; line-level code locations stay in the evidence file, and a client can keep evidence out of the repository. (part of #672)
- Legacy extraction maps how the existing system realizes each slice today, with targeted ways to read the code for it, and adds pass discipline and question wording for expert interviews. (part of #672)
- Model review explains an existing feature or walks a planned change through the model, and the Screenplay Reviewer has a walkthrough mode. (part of #672)
- Discovery reads documents with certainty marks and exact numbers, keeps source documents unchanged, records suspected source typos with their locator, and can produce a read-only blueprint summary for people who don't read models. (part of #672)
- Method skills add story order when declaring slices, decision state with one field per fact a scenario branches on, guidance for choosing a durable process or a plain automation, and further slicing, scenario and stream-design checks. (part of #672)
- Delivery guidance covers redelivery against commands that refuse duplicates, temporal and fan-out cases for automations, reading all of a command's scenarios together, frontend slice isolation, query-isolation specifications, append-only committed migrations and authenticated webhook captures with a published inbound contract. (part of #672)
- The quality gate reports which slices a change touches, as advisory output that never fails the gate. (part of #672)
- Hand-written code changed since it was last verified is investigated per delivery, with findings routed to restoring the code or to a model change request. (part of #672)
Changed
- Read models that mix kinds of computation are split by default; keeping them together needs a written reason. (part of #672)