Skip to main content

Daily Runbook

Use this checklist at the start and end of each working session to keep the platform stable and documentation current.

Morning Kickoff​

  1. Review docs/status/status.mdx for yesterday’s updates.
  2. Check ClickUp “Platform Docs Hub” list for open tasks or blockers.
  3. Verify Render + Supabase dashboards for incidents (CPU, errors).
  4. Confirm Slack #engineering has no unresolved alerts.

During Work​

  • Log significant actions in ClickUp tasks and commit messages.
  • Update the relevant documentation page immediately after shipping.
  • Run targeted tests (npm run test:api, npm run test:e2e) for features touched.
  • If adding credentials, store them in Render + GitHub secrets + secure vault, then update docs.

End of Day Routine​

  1. Summarize Work
    • Note completed features, bug fixes, pending items.
    • Update ClickUp tasks (status/comments).
  2. Update Docs
    • Refresh docs/status/status.mdx recent changes.
    • Append notes to relevant architecture/API pages.
  3. Run Health Checks
    • curl https://reformer-platform.onrender.com/healthz
    • Spot-check critical endpoints.
  4. Post Summary
    • Add summary comment to ClickUp Daily Runbook task.
    • Inform Slack/Email as needed.

Incident Response Snapshot​

  1. Capture logs from Render (mcp Render list_logs).
  2. Document issue in ClickUp Bugs list; link relevant files.
  3. Update docs/status/status.mdx with “Incident” section.
  4. Notify stakeholders via Slack with remediation steps.

Keep this runbook updated whenever the workflow changes. A clear routine keeps the docs trustworthy for everyone.***