issue-tracker-planfile

Manage project tasks and dependencies in local Markdown plan files.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/SpiceLabsHQ/Reaper --skill issue-tracker-planfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-tracker-planfile
Source: https://github.com/SpiceLabsHQ/Reaper/tree/main/skills/issue-tracker-planfile
Command: npx skills add https://github.com/SpiceLabsHQ/Reaper --skill issue-tracker-planfile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a way to manage project tasks and their dependencies locally using Markdown files when a dedicated issue tracking system is not available.

Core Features & Use Cases

  • Local Task Management: Creates and updates tasks directly in .claude/plans/ Markdown files.
  • Dependency Tracking: Manages task relationships and execution order within the plan file.
  • Use Case: When working on a small project or a feature without a formal issue tracker, use this Skill to define tasks, their statuses, and how they relate to each other, ensuring a clear development path.

Quick Start

Use the issue-tracker-planfile skill to create a new parent task titled "Implement user authentication".

Frequently Asked Questions about issue-tracker-planfile

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

FAQPage Schema
How do I track project tasks locally without an issue tracker?

Task dependencies are managed using Mermaid syntax or annotations within a defined schema in Markdown plan files, allowing you to establish execution order and relationships between issues in local development environments.

Can I create and close issues directly in Markdown files?

Yes, you can create, update, and close issues directly within local Markdown files stored in a designated plans directory, providing full task lifecycle management without needing a dedicated issue tracking system.

What is the best way to manage task dependencies for small projects?

The best way to manage task dependencies for small projects is using file-based Markdown plan files that support task decomposition, progress tracking, and execution order definition without the overhead of a formal issue tracker.

Does local Markdown task management work for defining execution order?

You should use file-based Markdown task management when working on small projects or features without a formal issue tracker, providing task decomposition and progress tracking directly in your repository.