work-tracking

Organize feature work into parent features and child work items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a consistent structure for turning large features and initiatives into a clear parent-feature and child-work-item hierarchy so teams can plan, assign, and track work without ambiguity across systems.

Core Features & Use Cases

  • Hierarchy & conventions: Clarifies the difference between parent features (epics) and child work items, with naming patterns and label guidance.
  • Platform mapping: Shows how to implement the hierarchy in GitHub (issues, task lists, Projects v2) and Linear (parent/sub-issue, projects, cycles).
  • Templates & estimation: Includes parent and child issue templates, estimation guidance (T-shirt sizing and story points), labeling strategy, and workflow lifecycle recommendations.
  • Use cases: Breaking down a multi-component feature, preparing sprint work, creating issues for cross-team initiatives, and estimating effort for planning.

Quick Start

Create a parent feature titled 'User Authentication System' and four child work items (design database schema, implement JWT token generation, create login API endpoint, write authentication tests) formatted as GitHub issues with labels 'feature' and 'task'.

Frequently Asked Questions about work-tracking

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

FAQPage Schema
How do I break down a feature into parent and child issues for project management?

Creating a parent and child issue hierarchy involves structuring large features into parent epics and child work items. This Skill provides naming conventions, label strategies, and templates to organize the breakdown for unambiguous tracking.

Does this work with GitHub and Linear for issue tracking?

Yes, this issue tracking hierarchy works with GitHub and Linear. It maps parent and child work items to GitHub issues, task lists, Projects v2, and Linear parent/sub-issues, projects, and cycles to maintain tracking consistency across platforms.

What is the best way to structure GitHub issues for a multi-component feature?

The best way to structure GitHub issues for a multi-component feature is using a parent epic with child work items. This Skill applies labeling strategies and T-shirt sizing or story point estimations to prepare clear sprint or milestone task lists.

How do I estimate effort when creating parent and child work items?

Estimating effort for parent and child work items uses T-shirt sizing and story points. This Skill provides estimation guidance alongside parent and child issue templates to help teams accurately gauge effort during engineering planning and sprint preparation.

When do I need to use a parent-child work item hierarchy for sprint planning?

You need a parent-child work item hierarchy for sprint planning when breaking down multi-component features or cross-team initiatives. This Skill provides structural templates to clarify parent features and child work items for preparing structured milestone tasks.