Sprint 81: improve pulse_check dispatch hints to use project_breakdown data
This commit is contained in:
@@ -41,16 +41,20 @@ steps:
|
||||
If everything looks healthy, say so briefly -- don't invent problems.
|
||||
|
||||
Also assess Crimson Leaf Publishing (CLP) production status:
|
||||
- Look for projects under crimson_leaf_publishing: cypress-bend, crimson-vows, binding-thread
|
||||
- For each, note: tasks_in_progress count, total tasks, last task date
|
||||
- Identify which project is MOST IDLE (least active, most overdue for a chapter)
|
||||
- The portfolio report includes a project_breakdown array for each company.
|
||||
- Look at the crimson_leaf_publishing company's project_breakdown.
|
||||
- Each project entry has: name, slug, tasks_in_progress, tasks_completed,
|
||||
last_activity_utc, hours_since_activity, and is_idle (true/false).
|
||||
- is_idle is true when tasks_in_progress=0 AND hours_since_activity > 4.
|
||||
- Identify which CLP project has is_idle=true and the highest hours_since_activity.
|
||||
- That is the project most overdue for a chapter dispatch.
|
||||
|
||||
- type: think
|
||||
max_tokens: 100
|
||||
output_key: dispatch_project_slug
|
||||
hint: |
|
||||
Based on Edgar's portfolio analysis above, which single CLP project is most idle
|
||||
and needs a chapter dispatched right now?
|
||||
Based on the portfolio report's project_breakdown for crimson_leaf_publishing,
|
||||
which single CLP project has is_idle=true with the most hours_since_activity?
|
||||
|
||||
Output EXACTLY one of these values, nothing else:
|
||||
- cypress-bend
|
||||
@@ -58,8 +62,8 @@ steps:
|
||||
- binding-thread
|
||||
- none
|
||||
|
||||
Output only the value. No explanation. No punctuation. No newlines.
|
||||
If all projects are actively producing, output: none
|
||||
Output only the slug value. No explanation. No punctuation. No newlines.
|
||||
If ALL three projects have is_idle=false (tasks currently in progress), output: none
|
||||
|
||||
- type: think
|
||||
max_tokens: 500
|
||||
|
||||
Reference in New Issue
Block a user