Daily Loop Runner
by @sunbinnju-star
Run one controlled daily project loop for a single active project. Use on: scheduled daily runs, planner-initiated project steps, resuming a project after cl...
clawhub install daily-loop-runnerπ About This Skill
name: daily-loop-runner description: "Run one controlled daily project loop for a single active project. Use on: scheduled daily runs, planner-initiated project steps, resuming a project after cleanup, user requests for active project advancement. Triggered when a project needs to advance by one meaningful step per day."
Daily Loop Runner
Advance one project by one meaningful step per loop. State read before execution, structured writeback after.
Input
Required:
project_card β full project card with current state, goals, blockerslatest_weekly_review β most recent weekly review notesrecent_daily_logs β list of recent daily loop logs (last 3-5)open_questions β unresolved questions from previous loopsOptional:
forced_bottleneck β override automatic bottleneck selectionOutput Schema
today_objective: string # one clear goal for today
selected_agent: string | null # which agent or tool will execute
task_input: object # structured input for the selected agent
expected_output: string # what success looks like
execution_summary: string # what actually happened
findings: string[] # key discoveries
decisions: string[] # decisions made based on findings
next_action: string | null # what to do tomorrow
project_card_updates: object # fields to update on project card
writeback_payload: object # structured record for project memory
safe_to_proceed: boolean # false if state was incomplete
Hard Rules
1. One project per run. Do not split focus. 2. One bottleneck per run. Pick the most critical blocker. 3. One main action per run. One meaningful step, not a sprint. 4. No execution without state read. Always read project_card and recent logs first. 5. No successful completion without next_action. Every loop must feed into the next.
Loop Phases
Phase 1: State Read
Phase 2: Bottleneck Selection
Phase 3: Task Input Construction
Phase 4: Execution
Phase 5: Writeback
Failure Handling
If state is incomplete (missing project_card, no recent logs, unclear objective):
safe_to_proceed = falseState Machine
IDLE β READY β RUNNING β WRITING β DONE
β
BLOCKED (if state incomplete)
Respect the state machine. Never skip from IDLE to RUNNING.