work-tracking

Structure product work into parent features and child work items for Linear and GitHub.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill work-tracking-csackrider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-tracking
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/work-tracking
Command: npx skills add https://github.com/csackrider/AI-DLC --skill work-tracking-csackrider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structure and manage work using a hierarchical parent-feature and child-work-item model, enabling clear planning and cross-tool coordination for Linear and GitHub.

Core Features & Use Cases

  • Hierarchical planning: create Parent Features and Child Work Items with clear scope and acceptance criteria.
  • Cross-tool mapping: align work items to Linear Epics and GitHub issues.
  • Naming conventions and labeling guidance to maintain consistency across teams.
  • Templates and guidance for breaking down work into manageable tasks.

Quick Start

Provide a product idea and I will generate a hierarchical work plan with a parent feature and actionable child items.

Frequently Asked Questions about work-tracking

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

FAQPage Schema
How do I structure product features into parent-child work items for Linear and GitHub?

To structure product features, generate a hierarchical work plan with parent features and actionable child items, applying clear naming conventions and cross-tool mapping to align work across Linear and GitHub.

How do I map Linear Epics to GitHub issues for cross-tool project management?

Map Linear Epics to GitHub issues by aligning parent features and child work items across both platforms, using consistent naming conventions and labeling guidance to maintain cross-team coordination.

What is the best way to break down product ideas into manageable tasks for sprint planning?

Break down product ideas by generating a hierarchical work plan with clear parent-child relationships, defining specific scope and acceptance criteria for each child work item to coordinate sprint work.

Does this work tracking approach require existing Linear or GitHub projects to function?

This work tracking approach does not require existing projects; provide a product idea to generate a hierarchical parent-feature and child-work-item plan compatible with Linear and GitHub.

Why do I need naming conventions and labels when planning features across teams?

Naming conventions and labels maintain consistency across teams during feature planning, ensuring clear parent-child scope and accurate cross-tool alignment between Linear and GitHub.