issue-shaping

To turn rough requests into actionable GitHub issues, you must shape the input into a clear problem statement with constraints, risks, and acceptance criteria before writing any code. This prevents scope creep and ensures alignment.

Issue shaping is a planning workflow that converts vague input into a concrete issue contract. It produces a durable problem statement, constraints, risks, acceptance checks, and a brainstorm placeholder to guide development.

Writing acceptance criteria for a poorly defined request requires applying a blueprint fit workflow to assess feasibility. This process shapes the rough input into a ready-to-run GitHub issue body with clear, actionable acceptance checks.

You should create a brainstorm file, such as `00_brainstorm.md`, when a rough request requires shaping into a structured plan. The blueprint fit workflow decides when this placeholder is needed to prevent misalignment.

Issue shaping works for risk management by guiding feasibility assessment and blueprint fit before development begins. By creating a durable problem statement with explicit constraints, it actively prevents scope creep and misalignment.

Yes, you can use issue shaping to generate project artifacts from a vague idea. It shapes the input into a complete, ready-to-action artifact set that can be integrated into `.project/` directories for development planning.