linear-backlog-manager

Publish approved feature specs as hierarchical issue trees in Linear.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill linear-backlog-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-backlog-manager
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/linear-backlog-manager
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill linear-backlog-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and maintaining Linear issues for approved feature specs is time-consuming, error-prone, and often breaks traceability between original requirements and tracked work.

Core Features & Use Cases

  • Hierarchical Issue Creation: Automatically translates approved tasks.md, requirements.md, and design.md inputs into a tree of labeled Linear issues (feature → story → task) with correct parentId nesting and traceability links.
  • Consistent Convention Enforcement: Applies standardized labels for issue type, feature association, requirement mapping, skill routing, and execution engine assignment to align with team workflows.
  • Backlog Amendment Support: Handles updates to existing Linear backlogs when specs change, including adding, removing, or editing tasks without breaking audit trails.
  • Use Case: For software teams using Linear as their project tracker, this skill eliminates hours of manual backlog setup and ensures every tracked task is directly linked to its original approved spec and requirement.

Quick Start

Use the linear-backlog-manager skill to publish the approved user authentication feature spec to the Ontoledgy Linear project as a structured nested backlog of issues.

Frequently Asked Questions about linear-backlog-manager

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

FAQPage Schema
How do I automatically create Linear issues from approved feature specifications?

You can automatically create Linear issues from approved feature specifications by using a backlog manager to translate tasks.md, requirements.md, and design.md files into a structured hierarchy of feature, story, and task issues with requirement traceability.

What is the best way to maintain spec-to-issue traceability in Linear backlog management?

Maintaining spec-to-issue traceability in Linear backlog management is achieved by translating approved specs into nested issues with standardized labels for feature association, requirement mapping, and skill routing, ensuring every tracked task links directly to its original requirement.

Can I update an existing Linear backlog when software design specs change?

Yes, you can update an existing Linear backlog when software design specs change by applying amendment tracking, which adds, removes, or edits nested tasks without breaking the original audit trail between the issues and requirements.

Does the Linear backlog manager require the Linear MCP for issue management?

Yes, the Linear backlog manager requires the Linear MCP to handle all issue management operations, applying standardized conventions for issue type and execution engine assignment while publishing the hierarchical issue trees.

How are feature specs structured into nested issues for agile project tracking?

Feature specs are structured into nested issues for agile project tracking by mapping the approved documents into a parent-child tree format (feature → story → task) with correct parentId nesting and consistent labeling conventions.