skills.rest
intelligentcode-ai
intelligentcode-aiOFFICIAL
Explore all skills by this author →
GitHub

create-work-items

Classify and create typed work items for GitHub or file-based backends.

1|1|Updated Feb 6, 2026
Search Tags:#planning#tdd#task management#github#issue tracking#work items
One-click install
npx skills add https://github.com/intelligentcode-ai/skills --skill create-work-items
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-work-items
Source: https://github.com/intelligentcode-ai/skills/tree/main/skills/create-work-items
Command: npx skills add https://github.com/intelligentcode-ai/skills --skill create-work-items

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and managing work items, ensuring that all necessary information is captured and categorized correctly for tracking and execution.

Core Features & Use Cases

  • Work Item Creation: Supports the creation of various item types like epics, stories, bugs, and findings.
  • Backend Integration: Seamlessly integrates with configured tracking backends (GitHub, file-based) for publishing.
  • TDD Support: Integrates with TDD workflows, creating explicit items for RED, GREEN, and REFACTOR phases.
  • Use Case: When a new feature is discussed, use this skill to create a 'feature' work item, link it to an 'epic', and ensure it's properly configured for the development team.

Quick Start

Use the create-work-items skill to create a new story titled "Implement user authentication" with high priority.

Frequently Asked Questions about create-work-items

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

FAQPage Schema
How do I automate creating GitHub issues for TDD phases?▼

You can automate creating GitHub issues for TDD phases by classifying work items into RED, GREEN, and REFACTOR tasks, then publishing them directly to configured GitHub tracking backends.

Can I track epics and user stories in a local file system without GitHub?▼

Yes, you can track epics and user stories using file-based systems as a configured tracking backend, allowing you to capture and categorize work items locally without requiring GitHub integration.

What's the best way to classify bugs and features for issue tracking?▼

The best way to classify bugs and features for issue tracking is to automate the categorization of typed work items, ensuring missing fields are clarified before publishing them to your tracking backend.

How does TDD decomposition into RED, GREEN, and REFACTOR phases work for task management?▼

TDD decomposition for task management works by breaking down features into explicit RED, GREEN, and REFACTOR work items, creating separate tracked tasks for each test-driven development phase.

Do I need configured tracking backends to create and manage work items?▼

You need configured tracking backends like GitHub or file-based systems to publish work items, though the skill automates classification and clarifies missing fields before publishing.

Why does creating a new feature require linking it to an epic for issue tracking?▼

Creating a new feature requires linking it to an epic to ensure hierarchical organization and proper configuration, streamlining tracking and execution for the development team.

Related Skills

Explore More Software Engineering Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
dot-dodot-do
5

beads

Track TDD phases with Git-native issues using RED, GREEN, and REFACTOR labels.

Official
Intermediate
intelligentcode-aiintelligentcode-ai
1

run-work-items

Execute prioritized work items from a configured backend with quality gates.

Official
Advanced
eric-sabeeric-sabe
1

issue-tracker-linear

Manage Linear issue lifecycle, project boards, and automated PR-linked closures.

Community
Intermediate