kano-agent-backlog-skill

You can track an AI agent backlog locally without a server by using this markdown-based skill to capture items hierarchically. It bootstraps via CLI, stores data as local markdown files, and generates version-controlled dashboards.

The best way to manage multi-agent coordination is using a durable markdown backlog with append-only worklogs. This approach ensures context survives across sessions and keeps multiple agents aligned without requiring external databases.

A Ready gate enforces backlog quality by validating structured items like Epics, Features, and User Stories before execution. It checks frontmatter metadata to ensure tasks and bugs meet defined criteria for agent processing.

Yes, you can use markdown dashboards to track Architecture Decision Records. The skill creates append-only ADRs to capture auditable decisions and refreshes local views from these markdown artifacts automatically.

No, you do not need a database to maintain AI agent context across sessions. This skill provides a local-first workspace that saves decisions, rationale, and worklogs directly as markdown files in your repository.

Backlog item types supported for local AI agent planning include Epic, Feature, User Story, Task, and Bug. These hierarchical items are managed with frontmatter metadata to structure planning and tracking effectively.