Skip to content

Latest commit

 

History

History
41 lines (36 loc) · 3.05 KB

LOOP_PROMPT.md

File metadata and controls

41 lines (36 loc) · 3.05 KB

LOOP PROMPT: Ratelord Orchestrator

Maintain the implementation and maintenance process for ratelord following the rules in AGENTS.md.

Execution Protocol

  • Single Task Focus: Each iteration (one execution) must pick the highest leverage task from NEXT_STEPS.md or TASKS.md and complete it. Do not multitask.
  • Frequent Progress Tracking:
    • Update PROGRESS.md, TASKS.md, PHASE_LEDGER.md, and NEXT_STEPS.md immediately as sub-steps are completed.
    • Commit often: Use the terminal to commit small, coherent changes to track progress.
  • Mandatory Final Action: At the end of EVERY iteration, before signaling completion, you MUST use the terminal agent to commit all tracked and untracked changes (excluding ignored files) with a descriptive commit message following the conventions in AGENTS.md. Maintain .gitignore to ensure unwanted files (logs, binaries, local state) are never committed.
  • Test Verification Loop:
    • Run Tests: After any code implementation, run relevant tests (e.g., go test ./...).
    • Handle Failures: If tests fail, immediately add a high-priority task to NEXT_STEPS.md to fix the specific broken tests. Do not mark the implementation task as "done" until tests pass.
    • Coverage: Ensure new code has adequate test coverage.
  • Documentation Synchronization:
    • After any implementation, verify that relevant design docs (e.g., API_SPEC.md, DATA_MODEL.md) reflect the code.
    • If docs are stale, immediately update them in this iteration, OR add a high-priority task to NEXT_STEPS.md to update them before proceeding.
    • User Docs: After major user-facing implementations, update the comprehensive user docs in docs/.
  • Example Verification:
    • Ensure major specific features have good examples in the examples/ folder.
    • If examples are missing, add a task to NEXT_STEPS.md to create them.
  • Resilience & Resumability:
    • Assume work may be halted at any point.
    • Every iteration should start by reading NEXT_STEPS.md to pick up exactly where the last one left off.

Context & Constraints

  • Role: Orchestrator (Coordinate sub-agents, ensure consistency, enforce architecture).
  • Core Principles: Local-first, Daemon Authority, Event-sourced, Predictive, Intent Negotiation (See PROJECT_CONTEXT.md).
  • Rules:
    • Always read NEXT_STEPS.md first.
    • Document decisions before implementation.
    • Ensure code changes are verified by tests (pkg/) or acceptance tools (ratelord-sim).

Signaling Completion

  • If you have completed the current high-leverage task and there are pending tasks remaining, output <promise>NEXT_TASK</promise>.
  • If all tasks in the current scope/phase are done and no more work remains, output <promise>DONE</promise>.

Sub-Agent Usage

  • Delegate drafting, implementation, or verification tasks to sub-agents.
  • Ensure sub-agents are briefed with PROJECT_CONTEXT.md and the specific relevant specs.
  • Perform a consistency check on all sub-agent output before finalizing.