Conducty Shape — Appetite, Boundaries, Design

Turn unclear or complex goals into bounded, executable designs. Shaping answers three questions before any prompt is written: How much is this worth? What's in scope? What's explicitly out?

This is not brainstorming in the open-ended sense. Shaping is opinionated — you propose boundaries, cut rabbit holes, and produce a design that fits the declared appetite. The output is a design doc that [[conducty-plan]] can decompose into prompts.

[!warning] Hard gate Do NOT generate prompts for a non-trivial goal until you have presented a design with appetite, scope, and no-go zones, and the user has approved it.

When to Use

Mandatory (invoked by [[conducty-plan]]):

• Goal is Medium or High complexity
• Goal spans multiple subsystems or projects
• Goal requirements are ambiguous or underspecified

Optional (user-triggered):

• User says "shape", "design", "brainstorm", "think through"
• User wants to explore approaches before committing