This walks through building a two-role Strategy from scratch: a Watcher that goes looking for new feedback on its own schedule, and an Addresser it hands that feedback to.
Create a new Strategy and give it a name. Add a first role, Watcher — it doesn't need its own dedicated space (see Root roles vs. their own workspace), since its whole job is noticing something and handing it off.
Add a second role, Addresser, this time with its own dedicated space, since it needs somewhere to actually make and commit changes. The Watcher's instructions should describe handing work to it by name — see Referencing sibling roles in a prompt — so a hand-off always lands somewhere the Addresser is already watching.
Instantiate the Strategy, give it a project name, and confirm — DF Code sets up both roles, wires the hand-off, and turns it on.
From here, the Watcher checks in on its own interval, and the moment it finds something and hands it off, the Addresser picks it up and gets to work — no further clicking required. Ready for a second role that checks the work before it's final? See Set up an Engineer / Reviewer pipeline.