Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .cursor/rules/sprint-context.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,13 @@ alwaysApply: true
## Current Sprint

**Sprint:** 2 (first Marathon-driven sprint)
**Phase:** Kickoff — awaiting specification
**Status:** Inputs populated, ready for `sprint-kickoff` skill activation
**Phase:** Specification
**Status:** Sprint kicked off, specification in progress

**Selected Requirements:**
- R1: Schedule/Cron Triggers — automation entity + cron scheduler
- R2: Event Triggers (GitHub/GitLab) — extend InboundRouter for automation dispatch
- R6: Automation Builder UI — create/list scaffold for managing automations

## What Exists

Expand Down Expand Up @@ -69,4 +74,4 @@ Epic 1 (Agent Powers) delivered core platform: agent loop, gateway API, web dash
## Sprint Goals

<!-- Updated at sprint kickoff by the sprint-kickoff skill -->
Sprint 2 will implement: Automation entity + schema, cron/schedule triggers, GitHub/GitLab event trigger binding, and automation builder UI scaffold.
Sprint 2 delivers the automation foundation: a persistent automation entity with cron/schedule triggers that fire unattended agent sessions, GitHub/GitLab event bindings that extend the existing InboundRouter into full automation dispatch, and a web UI scaffold (list + create flow) for managing automations. This sprint establishes the core data model and dispatch patterns that Sprint 3+ will extend with additional trigger sources.
6 changes: 3 additions & 3 deletions .marathon/inputs/requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@

### R1: Schedule/Cron Triggers

**Status:** [TODO]
**Status:** [IN SPRINT]

**Description:**
Agents can be triggered on schedules — either preset intervals (every hour, daily, weekly) or custom cron expressions. Scheduled automations run unattended and produce results like any other agent session.
Expand All @@ -41,7 +41,7 @@ Agents can be triggered on schedules — either preset intervals (every hour, da

### R2: Event Triggers (GitHub/GitLab)

**Status:** [TODO]
**Status:** [IN SPRINT]

**Description:**
Extend the existing `InboundRouter` + `InboundDispatcher` to support full automation binding — users configure trigger → prompt → tools → repos, and matching events automatically spawn agent sessions.
Expand Down Expand Up @@ -127,7 +127,7 @@ Agents can store and retrieve learnings from past runs. A memory system provides

### R6: Automation Builder UI

**Status:** [TODO]
**Status:** [IN SPRINT]

**Description:**
A web interface for creating, editing, and managing automations. Users configure trigger → prompt → tools → repos through a guided builder flow.
Expand Down
Loading