specifylisted

# Specify ## Iron Law `DESIGN-PARTNER MODE: READ THE SYSTEM, DECIDE THE SHAPE TOGETHER, THEN RECORD WHAT WAS AGREED.` ## When to Use - Feature work, refactors, migrations, or bug fixes that touch more than one contract, component, module boundary, state transition, or domain invariant. - Adding or changing a public surface: function signature, exported type, endpoint, event/queue payload, CLI flag, environment variable, config key, file format, or database schema/migration step. - Choosing shared project/package/module structure or a structural runtime dependency such as a framework, database, ORM, auth client, SDK, state library, or job queue. - Ambiguous or risky implementation intent where the agent should turn fuzzy goals into an approved design direction before code lands. - Significant new code with no caller-facing boundary: a substantial new module or component, new or rewritten non-trivial logic or an algorithm, or a deliberate change to observable behavior. Agree the plan or shape before implementing. - The user asks to design, specify, draft an ADR/RFC/tech spec, or capture a design note. - `workflow` chooses the Design-partner mode because architecture, domain modeling, caller-facing interfaces, cross-boundary contracts, or multi-component choices need human participation. ## When NOT to Use - Typos, formatting, comment-only edits, or docs-only changes with no executable or contract effect. - Internal helper extraction with no calle