create-task-files

Convert planning lists into structured markdown task files with YAML frontmatter.

14|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/Shoebtamboli/rails_claude_skills --skill create-task-files
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: create-task-files
Source: https://github.com/Shoebtamboli/rails_claude_skills/tree/main/lib/generators/claude/skills_library/create-task-files
Command: npx skills add https://github.com/Shoebtamboli/rails_claude_skills --skill create-task-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams keep feature plans, todos, and bug lists outside version control or scattered across tools, making work hard to track, review, and integrate with engineering workflows. This Skill converts planning artifacts into consistent, trackable markdown task files stored in a tasks/ directory so work is discoverable, git-friendly, and easy to review.

Core Features & Use Cases

  • Export and convert TodoWrite lists or freeform feature descriptions into structured markdown files (epic, user-story, bug, issue) with YAML frontmatter.
  • Organize and index tasks with numbered, slugified filenames, an INDEX.md, and a tasks/README to enforce naming and status conventions.
  • Template-driven generation using pre-defined templates for each task type and incremental numbering to avoid collisions.
  • Use cases: convert a completed /plan-feature output into an epic plus stories, export current todo lists into tracked files, or create bug-only exports for triage.

Quick Start

Run the create-task-files skill and follow the prompts to convert a todo list or feature description into a tasks/ directory with numbered markdown files and an index.

Frequently Asked Questions about create-task-files

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

FAQPage Schema
How do I export TodoWrite lists into markdown files for version control?โ–ผ

To export TodoWrite lists into markdown files, this Skill converts your task lists into structured files with YAML frontmatter, numbered slugified filenames, and an INDEX.md for git-friendly version control tracking.

Can I convert a feature plan into epics and user stories in a repository?โ–ผ

Yes, you can convert freeform feature descriptions into epics and user stories. It generates template-driven markdown files within a tasks directory, applying incremental numbering to avoid filename collisions in your repository.

What is the best way to track bugs and issues using markdown in git?โ–ผ

Tracking bugs and issues using markdown in git is best achieved by exporting them into dedicated task files with YAML frontmatter. This Skill organizes bugs into numbered, slugified filenames and generates a tasks README for status conventions.

Does this markdown task export generate an index for project directories?โ–ผ

Yes, the markdown task export generates an INDEX.md and a tasks README to organize project directories. These files enforce naming conventions and provide a discoverable overview of all tracked epics, user stories, and issues.

Do I need a specific project management tool to create version-controlled task files?โ–ผ

No, you do not need a specific project management tool. It directly converts existing TodoWrite lists or feature plans into standalone markdown files structured with YAML frontmatter, relying entirely on git for version control.

When should I not use markdown files for project task tracking?โ–ผ

You should not use markdown files for project task tracking if your team requires real-time collaborative editing or complex dependency mapping. This approach relies on git commits and static files, lacking dynamic progress dashboards.