Issue Cards

Why it's ranked here

The tool has a coherent opinion: keep agents focused on one documented step, not an entire issue. Local Markdown storage, parseable output, task expansion, and direct assistant access reinforce that goal. The author’s caveat about limited real-project use warrants caution, but the workflow is concrete and inspectable.

What's good

Issue records preserve decisions that agents often lose, including unresolved questions and failed approaches. Tags expand testing requirements into consistent steps. JSON and quiet output support scripts. Git integration stages issue updates automatically, while schema validation rejects malformed MCP arguments before tool execution.

Tradeoffs

The workflow is intentionally linear, which may constrain projects that need parallel task execution. Automatic Git staging changes repository state during routine updates. The HTTP server can run without authentication, so remote exposure requires deliberate token configuration. Its value also depends on maintaining detailed issue records inside each project.

How to use it well

Use it for repository-local coding work where an agent should complete, document, and close one step before receiving the next. Start with a clear problem, approach, and ordered tasks, then record questions and failures as work proceeds. Choose another system for nonlinear planning or a hosted shared workspace.

Observed

License

MIT

Primary language

JavaScript using CommonJS modules

Runtime

Node.js 14 or newer

Installation

Global npm package or on-demand npx execution

Interfaces

Command line, programmatic module execution, stdio MCP, and HTTP MCP API

Storage

Markdown issue files stored directly within the project

Validation

MCP arguments are validated with Ajv JSON schemas

Testing surface

Jest scripts cover unit, end-to-end, MCP, link, and coverage workflows