Propose

Evaluate an idea honestly, then write proposal.md when it is worth pursuing. The proposal explains the motivation deeply, bounds the change at a high level, and sketches only enough technical approach to establish feasibility and expose structural risk. Detailed behavior belongs in specifications; detailed architecture belongs in design.md.

Process

1. Understand and research

Use codagent:ask-questions when the problem, audience, desired outcome, success criteria, constraints, or scope boundaries are unclear. Do not draft from a rough idea when an answer would materially change the proposal.

Ground the evaluation in available evidence: