Show HN: Orchestro – Trello for Claude Code with Kanban Board

1 point

8 months ago

Hi HN! I'm building Orchestro, an AI-powered task management system for Claude Code that works like Trello but designed specifically for AI-assisted development.

  **The Problem:**
  When working with Claude Code on complex projects, I kept losing track of what the AI was doing across multiple conversations. Tasks would get duplicated, dependencies were unclear, and there was no way to
  see the big picture. I needed something between a simple todo list and full Jira complexity.

  **What it does:**
  - Decomposes user stories into technical tasks by analyzing your codebase
  - Tracks dependencies and detects conflicts automatically
  - Visual Kanban board showing real-time progress
  - Learns patterns from past work to improve future suggestions
  - Complete audit trail of AI decisions and code changes
  - 60 MCP tools for orchestrating complex development workflows

  **How it works:**
  When you give Claude Code a feature request, Orchestro can:
  1. Analyze your codebase structure (files, dependencies, patterns)
  2. Break down the story into concrete tasks with file references
  3. Detect potential conflicts with existing code
  4. Track what's done, what's in progress, and what's blocked
  5. Learn from successes/failures to improve next time

  **Tech Stack:**
  - Backend: TypeScript, Model Context Protocol SDK, Supabase (PostgreSQL)
  - Frontend: Next.js 14, React Server Components, TailwindCSS
  - Real-time: PostgreSQL triggers + WebSockets
  - Transport: stdio (runs locally, full privacy)

  **Why MCP?**
  MCP (Model Context Protocol) is Anthropic's standard for connecting AI to external tools. Instead of building yet another AI wrapper, Orchestro integrates directly into Claude Code as a native tool suite.
  Think of it as giving Claude Code a project management brain.

  **What makes it different:**
  Most MCP servers are single-purpose (GitHub integration, database queries, etc). Orchestro is a complete workflow orchestrator with 60 interconnected tools that work together: task decomposition, dependency
  analysis, pattern learning, guardian agents (database/architecture/API validation), and full audit trails.

  **Current status:**
  - v2.1.0 live on NPM: @khaoss85/orchestro
  - Published in Official MCP Registry
  - 96.7% test coverage
  - MIT licensed, fully open source

  **What I'd love feedback on:**
  1. Is "Trello for Claude Code" the right positioning?
  2. Would you use this for solo projects or mainly team workflows?
  3. What other MCP tools would make this more useful?
  4. Too many features or just right for the problem space?

  The vision is to bridge Product Managers (who think in stories), Developers (who think in code), and AI (which can do both but needs structure).

  GitHub: https://github.com/khaoss85/mcp-orchestro
  Demo: Watch the Kanban board update in real-time at http://localhost:3001 after setup

  Try it: `npx @khaoss85/orchestro@latest`

  Happy to answer any questions!

**The Problem:** When working with Claude Code on complex projects, I kept losing track of what the AI was doing across multiple conversations. Tasks would get duplicated, dependencies were unclear, and there was no way to see the big picture. I needed something between a simple todo list and full Jira complexity. **What it does:** - Decomposes user stories into technical tasks by analyzing your codebase - Tracks dependencies and detects conflicts automatically - Visual Kanban board showing real-time progress - Learns patterns from past work to improve future suggestions - Complete audit trail of AI decisions and code changes - 60 MCP tools for orchestrating complex development workflows **How it works:** When you give Claude Code a feature request, Orchestro can: 1. Analyze your codebase structure (files, dependencies, patterns) 2. Break down the story into concrete tasks with file references 3. Detect potential conflicts with existing code 4. Track what's done, what's in progress, and what's blocked 5. Learn from successes/failures to improve next time **Tech Stack:** - Backend: TypeScript, Model Context Protocol SDK, Supabase (PostgreSQL) - Frontend: Next.js 14, React Server Components, TailwindCSS - Real-time: PostgreSQL triggers + WebSockets - Transport: stdio (runs locally, full privacy) **Why MCP?** MCP (Model Context Protocol) is Anthropic's standard for connecting AI to external tools. Instead of building yet another AI wrapper, Orchestro integrates directly into Claude Code as a native tool suite. Think of it as giving Claude Code a project management brain. **What makes it different:** Most MCP servers are single-purpose (GitHub integration, database queries, etc). Orchestro is a complete workflow orchestrator with 60 interconnected tools that work together: task decomposition, dependency analysis, pattern learning, guardian agents (database/architecture/API validation), and full audit trails. **Current status:** - v2.1.0 live on NPM: @khaoss85/orchestro - Published in Official MCP Registry - 96.7% test coverage - MIT licensed, fully open source **What I'd love feedback on:** 1. Is "Trello for Claude Code" the right positioning? 2. Would you use this for solo projects or mainly team workflows? 3. What other MCP tools would make this more useful? 4. Too many features or just right for the problem space? The vision is to bridge Product Managers (who think in stories), Developers (who think in code), and AI (which can do both but needs structure). GitHub: https://github.com/khaoss85/mcp-orchestro Demo: Watch the Kanban board update in real-time at http://localhost:3001 after setup Try it: `npx @khaoss85/orchestro@latest` Happy to answer any questions!