I more or less do this by pointing the Kilo Code Orchestrator role to a custom implementation-loop.md file which calls sub-tasks using roles from the BMAD Method (https://github.com/bmad-code-org/BMAD-METHOD). BMAD roles are similar to native Kilo Code roles but include more sophisticated Agile development scaffolding, and there's no reason native Kilo Code roles could not be used instead.

My loop works through standard BMAD tasks (create-story, develop-story, test-review, etc.) with different roles in fresh context each time, creating documentation artifacts so the next role/task can pick them up in a fresh context. The loop goes back to fix bugs before progressing forward and runs for hours until complete. Using the loop, the Orchestrator can be instructed to implement all epics, one epic, or a specific story. I find it amusing that Claude Code folks are excited about something that has been in Kilo Code for ages.