From c7e371c124a80ee9d21584cf10e6fd18ed6f25c3 Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 18 Mar 2026 10:36:20 +0000 Subject: [PATCH] story-kit: create 280_story_long_running_supervisor_agent_with_periodic_pipeline_polling --- ...unning_supervisor_agent_with_periodic_pipeline_polling.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md b/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md index daaa6d6..a918cbd 100644 --- a/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md +++ b/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md @@ -18,7 +18,10 @@ As a project owner, I want a long-running supervisor agent (opus) that automatic - [ ] Supervisor can be chatted with via Matrix (timmy relays to supervisor) or via the web UI - [ ] Supervisor logs its decisions so the human can review what it did and why - [ ] Polling interval is configurable in project.toml (e.g. supervisor_poll_interval_secs = 30) +- [ ] Supervisor logs persistent/recurring problems to `.story_kit/problems.md` with timestamp, description, and frequency — humans review this file periodically to create stories for systemic issues ## Out of Scope -- TBD +- Supervisor accepting or merging stories to master (human job) +- Supervisor making architectural decisions +- Replacing the existing per-story agent spawning — supervisor coordinates on top of it