project-router

What This Skill Does

The project-router skill acts as the central nervous system for OpenClaw’s project management and workspace orchestration. It bridges the gap between high-level task tracking and low-level terminal operations, transforming any local directory into a manageable project bundle. By leveraging a canonical SQLite-based task store and a Trello-syncing backend, it ensures that your project context—documentation, build targets, artifact indices, and task status—remains consistent across environments. It facilitates seamless context switching, allowing developers to jump between projects while instantly loading relevant code paths, documentation, and operational targets.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/safatinaztepe/project-router

Once installed, verify that the project CLI tool is accessible in your path and that the mcp-project-router server is registered within your MCP configurations. You may need to authenticate with Trello via environment variables if you intend to use the synchronization features.

Use Cases

1. Standardized Development Workflows: Automate linting, testing, and deployment by defining project-local target sets. Instead of memorizing commands, simply run project target run <name>.
2. Context Switching: Quickly load the state of a specific project, including active tasks, relevant artifacts, and environment context, allowing for efficient task migration.
3. Hybrid Task Management: Maintain a local "source of truth" for tasks in SQLite while keeping your team informed via Trello boards. The synchronization engine ensures cards, labels, and lists remain in lock-step with your local activity.
4. Project Bootstrapping: Initialize new projects with standard folder structures, manifests, and artifact tracking, ensuring consistent setup across your workspace.

Example Prompts

1. "Detect the current project and list all available targets; then execute the 'test' target to verify the current build state."
2. "Switch context to the 'backend-api' project, show me my top priority tasks, and open the relevant documentation artifacts."
3. "Sync my current task list with the project Trello board and ensure all P0 items are tagged appropriately."

Tips & Limitations

• Idempotency: All operations are designed to be idempotent. Feel free to re-run project apply or project sync as needed without side effects.
• Storage: Keep your .project/ directory ignored in .gitignore if it contains sensitive internal build metadata, though the .project/PROJECT.md is intended for version control.
• Offline Usage: The SQLite store allows for local task management, meaning you can continue working even when disconnected from Trello. Simply run project pm trello sync once you have network access again.