Chris Hendrickson
0723c7d996
- Flesh out docs/index.md, docs/config.md, docs/features/mcp.md, docs/features/kanban.md with full content and aligned tables - Fix .markdownlint-cli2.mjs config (rules were outside 'config' key) - Add packages/mcp as a standalone MCP server package - Update all pubspec descriptions - Implement DewCommand + CommandRegistry in core - Implement KanbanCommand and McpCommand stubs with registerCommands() - Wire CLI entry point using CommandRunner + CommandRegistry - Add 'melos run dew' script for running the CLI from workspace root - Update tests across core, kanban, mcp packages Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1.4 KiB
1.4 KiB
Dew Documentation
Welcome to the documentation for the Dew project management tool!
Contents
- Configuration — Configuring Dew via
dew.yaml
Features
- Kanban Board — Visualize and manage tasks in a column-based workflow
- MCP Server — AI agent integration via the Model Context Protocol
Package Architecture
Dew is structured as a Dart workspace with the following packages:
| Package | Description |
|---|---|
packages/cli |
The dew command-line tool. Wires all packages together at startup. |
packages/core |
Shared types (tickets, columns, config) and the McpToolProvider interface. |
packages/kanban |
Kanban board logic. Implements McpToolProvider to expose its tools to the MCP server. |
packages/mcp |
The MCP server. Depends on core; collects and serves registered tools from all packages. |
kanban (and future feature packages) depend only on core — not on mcp — keeping them usable independently of the AI integration layer. The cli package is the only one that depends on mcp and is responsible for starting the server and registering all providers.