← ClaudeAtlas

backlog-authoringlisted

Author plans and native records for existing Backlog.md projects, using their configured MCP or CLI workflow. Use for planning requests or task, milestone, decision, and doc updates only when the project already contains a backlog/ directory belonging to Backlog.md. Does not apply without that directory and does not initialize Backlog.md.
itsjavi/skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill itsjavi/skills
# Backlog.md authoring This general skill is for [Backlog.md](https://github.com/MrLesk/Backlog.md), the Markdown-based tracker with a CLI and an MCP server. It is not tied to any particular project. Keep executable work in tasks, delivery outcomes in milestones, durable choices in decisions, and maintained guidance in docs. For every applicable planning request, consider all four record types, then change only the records that materially support the requested work. ## Confirm applicability and read the local workflow Resolve the project root first, since the current working directory may be nested. If the project has no `backlog/` directory, this skill does not apply. Do not create that directory, initialize Backlog.md, or migrate another tracker to make the skill apply. Continue ordinary planning when requested, and treat tracker setup as separate work. An MCP server exposing only initialization guidance does not satisfy this prerequisite. Confirm that the existing directory belongs to Backlog.md using the project's configuration and guidance. Read applicable AGENTS.md instructions, the documentation index, and the configured Backlog.md workflow. Do not assume a particular package manager, version, directory layout beyond the applicability check, or project-specific policy. Backlog.md provides both CLI and MCP access. Use the interface required by the project. Otherwise, use a configured MCP connection for operations it supports, with the project-local CLI as a fallba