backlog-local

Manage backlog items in a local Markdown file with bracket status markers.

12|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ovargas/virtual-team --skill backlog-local
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-local
Source: https://github.com/ovargas/virtual-team/tree/main/skills/backlog-local
Command: npx skills add https://github.com/ovargas/virtual-team --skill backlog-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog Local solves the need for a lightweight, local backlog tracker by storing items in a single Markdown file (docs/backlog.md) using bracket-based status markers. It defaults to this local implementation when stack.md specifies backlog: local or when no backlog field is present.

Core Features & Use Cases

  • Local backlog storage in docs/backlog.md with bracket markers for statuses
  • Supports statuses: ready ([ ]), doing ([>]), implemented ([=]), done ([x])
  • Provides operations to list, start, mark_implemented, complete, and create backlog items; supports feature tagging, grouping, and ordering

Quick Start

Create a docs/backlog.md file and start tracking backlog items using bracket markers to reflect status.

Frequently Asked Questions about backlog-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a project backlog locally using Markdown?▼

You manage a project backlog locally by creating a docs/backlog.md file and using bracket-based status markers to track items. The file supports operations like listing, starting, implementing, and completing tasks.

What Markdown syntax does local backlog tracking use for task statuses?▼

Local backlog tracking uses bracket-based status markers in Markdown: ready ([ ]), doing ([>]), implemented ([=]), and done ([x]). These markers define the current state of each backlog item.

Can I track agile project management items offline without a database?▼

Yes, you can track agile project management items offline by storing them in a single local Markdown file. The system reads and writes docs/backlog.md, offering a lightweight alternative to database-backed trackers.

What is the best way to structure a lightweight backlog for offline planning?▼

The best way to structure a lightweight backlog for offline planning is using a single Markdown file with bracket markers for statuses. This approach supports feature tagging, grouping, and ordering for clear organization.

Do I need any dependencies to create and manage a local Markdown backlog?▼

No dependencies are required to manage a local Markdown backlog. The implementation operates entirely on a local docs/backlog.md file using bracket-based status markers without external packages.

Why use a single Markdown file instead of dedicated project management software for backlog tracking?▼

Using a single Markdown file for backlog tracking provides a lightweight, offline solution that avoids database overhead. It defaults to this local implementation when stack.md specifies backlog: local or lacks a backlog field.