generated from coulomb/repo-seed
49 lines
1.6 KiB
Markdown
49 lines
1.6 KiB
Markdown
---
|
|
id: weekly-coding-retro
|
|
name: Weekly Coding Retrospection
|
|
enabled: false # flip to true once the coding_retro resolver + session-memory publish (AGENTIC-WP-0010) are verified
|
|
owner: custodian-agent
|
|
governance: custodian
|
|
status: proposed
|
|
trigger:
|
|
type: cron
|
|
cron_expression: "0 19 * * 6" # Saturday 19:00
|
|
timezone: Europe/Berlin
|
|
misfire_policy: skip
|
|
context_sources:
|
|
- type: state-hub
|
|
query: coding_retro
|
|
params:
|
|
window_days: 7
|
|
limit: 100
|
|
bind_to: context.retro
|
|
# The coding_retro resolver returns the most recent event_type=coding_retro read
|
|
# model published to the hub by helix_forge session-memory (AGENTIC-WP-0010).
|
|
# Its detail.suggestions[] are already ranked (impact x frequency, cross-flavor
|
|
# first) and capped at 3 per repo, so the rule below just routes them.
|
|
---
|
|
|
|
# Weekly Coding Retrospection
|
|
|
|
Runs every Saturday 19:00 Berlin time. Reads the previous week's coding-session
|
|
analysis (published to the hub by helix_forge session-memory) and opens one
|
|
improvement suggestion per relevant repo — the three most promising, already
|
|
ranked upstream.
|
|
|
|
```rule
|
|
id: propose-weekly-improvements
|
|
for_each: context.retro.suggestions
|
|
bind_as: s
|
|
condition: 'context.s.score > 0'
|
|
action:
|
|
task_template: context.s.title
|
|
description: context.s.recommendation
|
|
target_repo: context.s.repo
|
|
priority: context.s.priority
|
|
labels: ["coding-retro", "improvement", "automated"]
|
|
```
|
|
|
|
Each suggestion carries `repo`, `title`, `recommendation`, `priority`, and
|
|
`score`. The upstream retro caps the list at three per repo, so this emits at most
|
|
three improvement tasks per relevant repository per week.
|