Tick Md

What This Skill Does

Tick Md is a powerful coordination layer for OpenClaw that enables multi-agent project management using a git-backed, markdown-first protocol. By leveraging the TICK.md file format, this skill allows you to track tasks, assign roles to agents, and maintain a high-fidelity audit trail of work progress within your codebase. It bridges the gap between human intent and automated execution, ensuring that every task is documented, tracked, and verifiable.

Installation

Prerequisites: Ensure the Tick CLI and the corresponding MCP server are installed in your environment. Run tick --version to verify connectivity. If your repository lacks a tracker, navigate to your root directory and run tick init to generate a project-level TICK.md file. For specialized IDE integrations, consult the primary installation documentation provided with the CLI tools.

Use Cases

This skill is ideal for projects requiring collaborative autonomy. Use it when managing complex, multi-step refactors where you need to track dependencies between agents. It is perfect for teams (human or AI) needing transparency; it acts as the 'source of truth' for status updates, ensuring no work is duplicated or forgotten. It also provides excellent historical reporting for project post-mortems via standard Git logs.

Example Prompts

1. "Check the current project status and tell me which tasks are assigned to the backend agent."
2. "Create a high-priority task for updating our API documentation and assign it to yourself."
3. "List all incomplete tasks tagged with 'frontend' and summarize the remaining work for me."

Tips & Limitations

• Transparency is key: Always use tick comment to keep human stakeholders updated on reasoning behind technical changes.
• Stay Organized: Use tags consistently to allow for efficient filtering with tick list commands.
• Safety First: The tool requires explicit authorization for write operations that modify Git history. When prompted to push code, ensure the current branch state is verified before approving. Note that this skill is local-first; if you work across different machines, you must ensure the repository is synced via git to keep the TICK.md state consistent across all environments.