What problem does it solve?
This skill solves the problem of creating a structured, trackable project backlog from approved feature specifications when no cloud-based tracker MCP (JIRA, Linear, Azure DevOps) is available, eliminating the need for external tracker services for teams using local filesystem-based project tracking.
Core Features & Use Cases
- Hierarchical Work Item Generation: Creates epic, story, and task markdown files from approved tasks.md feature specs, grouped by requirement for full traceability.
- Execution Engine Assignment: Auto-classifies tasks as simple (Codex) or complex (Claude) based on complexity rules, with user override options before publishing.
- Automated Board and Ticket Map Generation: Produces a browsable tracker index and canonical ticket map linking tasks back to their source specs for downstream sprint planning and execution.
- Use Case: Engineering teams using local filesystems instead of cloud trackers can automate backlog creation after spec approval, keeping all work items git-diffable and reviewable in pull requests.
Quick Start
Use the local-backlog-manager skill to convert the approved feature spec stored in documentation/specs/your-feature-name/ into a structured local filesystem backlog of epics, stories, and tasks with full requirements traceability.