Does this skill actually implement the code changes?

No, this skill focuses strictly on scoping and planning. It creates the documentation and requirements. Once created, you can use /ctx:task to begin the actual implementation phase.

How does create-task differ from the breakdown skill?

While the breakdown skill decomposes large epics into multiple related tasks, create-task is designed for one-off, independent items like bug fixes or quick updates that don't belong to a larger feature set.

Can I modify the task before it is finalized?

Yes, the skill presents a detailed draft including success criteria and complexity. You can ask Claude to adjust any part of the draft before it writes the file to your disk.

Where are the tasks stored in my project?

Tasks are created as markdown files within the .context/tasks/ directory, using a zero-padded three-digit numbering system for easy sorting and reference.

Task Creator for Claude Code

Name: Task Creator for Claude Code
Author: tdp1999

bytdp1999

0•

Productivity & Workflow

Generates structured, standalone task files for bug fixes and small features within a task-driven development workflow.

The create-task skill enables developers to quickly formalize small work items, bug fixes, or investigations into documented tasks without the overhead of creating a full epic. It intelligently analyzes existing codebase patterns, determines correct task numbering, and generates a comprehensive markdown file complete with acceptance criteria, complexity estimation, and technical notes. By automating the scaffolding of tasks, it ensures that even minor updates follow project-specific architectural standards and remain visible in the project's progress tracking system.

Key Features

010 GitHub stars

02Real-time synchronization with progress.md for project tracking

03Standardized task templates including acceptance criteria and complexity ratings

04Intelligent codebase analysis to generate relevant technical implementation notes

05Interactive drafting process with user verification before any files are written

06Automatic task numbering and file management within the .context directory

Use Cases

01Documenting a quick bug fix while maintaining project standards

02Formalizing a technical investigation or research task within a TDD workflow

03Scoping a small feature enhancement that doesn't require a full epic breakdown

Key Features

010 GitHub stars

02Real-time synchronization with progress.md for project tracking

03Standardized task templates including acceptance criteria and complexity ratings

04Intelligent codebase analysis to generate relevant technical implementation notes

05Interactive drafting process with user verification before any files are written

06Automatic task numbering and file management within the .context directory

Use Cases

01Documenting a quick bug fix while maintaining project standards

02Formalizing a technical investigation or research task within a TDD workflow

03Scoping a small feature enhancement that doesn't require a full epic breakdown