specifylisted

# Specify ## Iron Law `DESIGN-PARTNER MODE: READ THE SYSTEM, DECIDE THE SHAPE TOGETHER, THEN RECORD WHAT WAS AGREED.` ## When to Use - Work that touches more than one contract, component, module boundary, state transition, or domain invariant. - Adding or changing a public surface, shared structure, or a structural runtime dependency (framework, database, ORM, auth client, SDK, job queue). - Significant new code with no caller-facing boundary: a substantial module, non-trivial logic, or a deliberate change to observable behavior. - Ambiguous or risky intent, or the user asks for an ADR, RFC, tech spec, or design note. ## When NOT to Use - Typos, docs-only edits, internal helper extraction, private file moves, dependency bumps with no public surface change, or narrow bug fixes that restore intended behavior. - The design is settled and the user wants a task plan; use `workflow` or the host's planning mode. - A caller-facing interface is already concrete and only needs approval; use `contract-first`. ## Rules 1. Design-partner means the agent proposes concrete options and the human approves, revises, or rules them out. Neither "the agent decides alone" nor "the human should come up with the design" is this mode. 2. Stay above implementation sequencing. Specify owns contracts, states, tradeoffs, risks, and decisions. File-by-file edits, pseudocode, and task checklists belong to planning after the direction is agreed. 3. Contracts are any calle