cleo

CLEO is an agent-first task orchestration system designed for Claude Code agents and solo developers working on complex projects. It solves the coordination crisis of multi-agent workflows by providing hierarchical task management, persistent memory across sessions, and multi-provider support for Claude Code, Cursor, Gemini, and other AI coding platforms. The system includes six core components: TASKS for project management, LOOM for a 9-stage development lifecycle, BRAIN for semantic memory that doesn't decay, NEXUS for code intelligence, CANT for agent definition, and CONDUIT for agent-to-agent communication. CLEO reconnects agents to project context after interruptions and enables structured coordination where power is paired with memory and continuity.

[{"step":"Define the task and constraints","action":"Use the prompt template to specify the task (e.g., 'Deploy a Node.js app to AWS EC2'), error cases (e.g., 'AWS credentials expired'), and validation criteria (e.g., 'Port 3000 must respond').","tip":"Be explicit about environment requirements (e.g., 'Node.js 20+', 'Docker installed')."},{"step":"Run CLEO in a compatible environment","action":"Execute the task in a terminal with CLEO installed (e.g., `cleo run --task \"[YOUR_TASK]\"`). Ensure the environment matches the task requirements (e.g., Python for a Python task).","tip":"Use `cleo init` to set up a new project if starting from scratch. Test CLEO’s anti-hallucination checks by intentionally providing invalid inputs."},{"step":"Monitor execution and validate outputs","action":"Review CLEO’s step-by-step report for errors or warnings. Manually verify critical outputs (e.g., API responses, file contents) against expected results.","tip":"For complex tasks, break them into smaller CLEO subtasks (e.g., 'Build Docker image' → 'Run container' → 'Validate endpoints')."},{"step":"Iterate and log results","action":"Address any issues flagged by CLEO (e.g., retries, error handling). Save the final report and artifacts (e.g., logs, screenshots) to a designated directory.","tip":"Use CLEO’s logging features to track task history (e.g., `cleo log --task-id [ID]`). Share reports with team members for collaboration."},{"step":"Integrate with CI/CD pipelines","action":"Embed CLEO tasks in scripts (e.g., GitHub Actions, Jenkins) to automate workflows. Use CLEO’s CLI for programmatic control (e.g., `cleo run --task \"deploy\" --env staging`).","tip":"Test CLEO tasks in a staging environment before production. Use CLEO’s error handling to trigger rollback procedures if validation fails."}]