melech-idea-to-canvas

Turn @ into a standalone Cursor Canvas that helps the team quickly understand and align on how we are going to build this.

Accept any starting point: a rough idea, a shower thought, a Slack thread dump, meeting notes, a decision log, a product brief, a PRD fragment, a design doc, an RFC, or a tech spec. The less structured the input, the more the skill must do the structuring work.

This is primarily a knowledge-transfer artifact — not an approval workflow, debate space, or prettier copy of the input.

Core objective: Make what the author knows as easy as humanly possible for the team to absorb without losing important meaning, decisions, constraints, or implementation direction.

Before building the canvas, identify:

• The problem and why it matters
• The intended outcome
• The core mental model
• The proposed system and how its parts work together
• The key flows, states, boundaries, and ownership
• Important decisions and their reasoning
• Constraints, risks, assumptions, and explicit non-goals
• The implementation sequence and what each team or component owns
• Details needed for alignment versus details that can be progressively disclosed