shaping-writing-problem-frames

Problem framing structures your project's core problem statement by defining the trigger and impact. It prevents scope creep by establishing clear non-goals and time constraints before development begins.

You write a problem frame document by applying this Skill to a structured context brief. It generates defined sections for triggers, impacts, success criteria, appetites, non-goals, and constraints to bound the project.

Project success criteria and non-goals should include measurable outcomes and explicit project boundaries. The generated problem frame document separates what the project will attempt to do from what it will not attempt to do.

No, defining project appetite and time constraints requires a structured input based on a context brief. The Skill uses this brief to establish measurable outcomes and define specific project boundaries.

Use problem framing when kicking off a new project to ensure everyone understands the exact problem being solved. It differs from general planning by focusing strictly on scope bounding, success measurement, and setting appetite constraints.