Workflow specify

Turn the agreement into tickets another agent could build, and get the plan approved. No application code or tests.

Read shared policies from sibling ../workflow/, including its "Always" list. Stop if missing; never substitute another installed copy.

Before you start, check: rules cover this scope (workflow/RULES.md); the checkpoint Agreement is agreed, legacy or waived for this revision, or clarify sent a small settled change here to ask both gates at once (workflow/VISUAL-REVIEW.md); otherwise go to workflow-clarify; no open choice blocks the plan; application UI has its ui-design mode and sources recorded (an unrecorded mode blocks only UI tickets); read ../ui-design/SKILL.md if this session has not. When existing styles cannot produce the agreed layout, ask design.md rule 4's question; never offer new CSS. Refresh evidence for files changed since the agreement.

1. Place the behavior

Put each behavior in the code that already owns it. Read ../codebase-design/SKILL.md when an interface or seam is in question, ../domain-modeling/SKILL.md when a term or owner is unclear. Every new helper, wrapper, fallback or setting must pass the necessity check in workflow/AUDIT.md. Pick guidance for the real risks from rule-maker's ENGINEERING.md.

2. Cut vertical tickets

A ticket delivers one visible slice of a journey through every layer it needs, so it can be tested and reviewed alone. A ticket with no behavior of its own is a labelled prerequisite that names what it enables.

Write TODO in the workflow/TASK-FOLDER.md format (overview table, labelled tickets) via record.py. Supports, Depends on and Rules go under References; the rest under Technical details: