Loop/loopMaintenancehigh riskintermediatesafety B · 75Forward Futurepre-dates current gate · under review

Keep a verified daily project story

Turn repo activity, goals, and open threads into a verified daily narrative the next agent can trust.

prompt
→ Claude
On each [window], read the configured repositories, goals, prior STORY.md, and optional authorized sources. Update project files, then write STORY.md with focus, deadlines, open threads, and evidence-backed recent wins. Carry every prior thread forward, prove it finished, or mark it STALE/NEEDS-REVIEW—never silently drop one. Archive the snapshot and record the change. Stop when verification passes; if evidence or access is missing, return a thinner or blocked snapshot explicitly.
claude-code · codex

Use this when

Use this when work spans several repositories or context sources and future agents need a recurring, evidence-based account of priorities, progress, deadlines, and unfinished work.

How it runs

  1. Read the configured repositories, goals, personal context, optional authorized sources, previous STORY.md, and existing project files; report missing inputs instead of inventing them.
  2. Refresh each project record with current activity, branch state, shipped evidence, in-progress work, and stale status under the configured window.
  3. Write the new story with interpretation, focus, deadlines, open threads, and evidence-backed recent wins rather than a raw commit list.
  4. Reconcile every previous thread, archive the verified snapshot, update the changelog, and stop with an explicit complete, thinner, or blocked result.

Done when

✓ The current story accounts for every prior thread and supports every recent win with evidence. Each previous open thread is carried forward, closed with proof, or visibly flagged, and every claimed win cites a commit, release, closed task, deployment, sent deliverable, or generated artifact.

Why it works

A recurring narrative preserves the meaning behind activity without letting old commitments disappear. Evidence requirements keep recent wins factual, while thread reconciliation makes stale or unfinished work visible to the next agent.

Implementation note

Configure source paths and the stale window before relying on the story. Treat notes, calendars, task exports, and repository history as private; read only authorized sources and do not publish or transmit their contents without approval.

Source: Forward Future ↗

More maintenance loops

Upgrade to current Node LTS

Loop/goallooprepo

Move the project to the current Node LTS across .nvmrc, CI config, Dockerfiles, and engines, fixing deprecations until everything is green on the new runtime.

prompt
→ Claude
/goal the project runs on the current Node LTS — update .nvmrc, the engines field, CI workflow files, and any Dockerfile base images to the LTS version, then run install, build, lint, and the full test suite on it, fixing deprecation warnings and breakages one at a time; stop when all are green or after 15 turns
maintenancemedium riskclaude-codecodexcursor

Define done before Codex starts

Loop/loopForward Future

Set the completion contract up front, track proof for every requirement, and block partial work from being called done.

prompt
→ Claude
Run $goal-planner-codex [task] for long-running Codex work where partial work could be mistaken for done. Landing a PR and verifying production is one example. Before acting, define every required outcome and its evidence. After each bounded action, mark requirements proved, weak, missing, or contradicted. Complete the Goal only when all are proved; otherwise stop as blocked, stalled, or exhausted. Ask before creating Goal state. Finish with the requirement-to-evidence table, status, owner, and next action.
maintenancehigh riskclaude-codecodex

Chase a refund until it lands

Loop/goalForward Future

Open the claim, watch replies and deadlines, and keep the case moving until the money actually arrives.

prompt
→ Claude
Get my refund for [company and charge info]. Start the claim now through an approved support channel, then keep following up on replies, promises, and deadlines until the refund arrives. Keep a short case note so each follow-up has context. Stop only when the refund is received or you are genuinely blocked and need me.
maintenancemedium riskclaude-codecodex