analyze-frame

Problem Frames analysis converts natural language requirements into structured YAML specifications that classify requirements by frame type (CBF, IDF, RIF, WPF, TF) and map them to domain concerns, acceptance criteria, and validation artifacts in a standardized docs/specs/ directory.

Event Storming outputs capture domain events and user interactions; Problem Frames analysis takes these outputs and transforms them into formal frame-based YAML specs that link events to specific problem frame classifications and cross-context dependencies.

Yes, Problem Frames handle both functional and technical requirements by classifying them across frame types, mapping concerns to domain and machine models, defining cross-context dependencies, and generating acceptance tests and validation artifacts.

The Skill generates a complete docs/specs/{feature-name}/ directory tree containing frame.yaml metadata, problem statements, domain definitions, acceptance criteria links, runbook documentation, and validation artifacts for traceability and governance.

Problem Frames link natural language requirements to formal YAML specifications with problem classification, frame-concern mappings, and acceptance test references, creating an auditable chain from requirement to validation for compliance and governance.

The Skill analyzes requirements and automatically applies Problem Frame classification across CBF, IDF, RIF, WPF, and TF frame types; basic familiarity with requirement structures and domain context helps, but the Skill handles frame determination.