npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

cc-tasks

v1.0.0

Published

A powerful command-line task management tool that uses Markdown files as a database

Readme

Claude Code Tasks

A powerful command-line task management tool that uses Markdown files as a database. Perfect for developers who want to track project tasks alongside their code.

Features

  • Markdown-based: Store tasks in human-readable .md files that can be versioned with git
  • Hierarchical tasks: Support for main tasks and subtasks with completion tracking
  • Dependencies: Define task dependencies and validate task order
  • Rich querying: Filter and search tasks by status, topic, or ID
  • Export options: Export tasks to JSON or HTML for reporting
  • File watching: Auto-reload when task files change
  • Validation: Ensure task format consistency across your project

Installation

Use directly with npx (no installation required):

npx cc-tasks <command>

Or install globally:

npm install -g cc-tasks

Or add to your project:

npm install --save-dev cc-tasks

Quick Start

  1. Create a tasks.md file in your project:
## Task 1.0: Setup Project
- [ ] **Complete**
**Main Topic:** Initial Setup
**Description:** Set up the project structure and dependencies
**Subtasks:**
- [x] Initialize npm project
- [ ] Install dependencies
- [ ] Create folder structure
**Required Tasks:** None
**Validation:** 
- [ ] package.json exists
- [ ] All dependencies installed
  1. Validate your task file:
npx cc-tasks parse
  1. List all tasks:
npx cc-tasks list

Commands

parse

Validate the format of your tasks.md file.

npx cc-tasks parse [file]
# Default: ./tasks.md

Options:

  • --file, -f: Specify task file (default: tasks.md)
  • --strict: Enable strict validation mode

list

Display all tasks with their status.

npx cc-tasks list [options]

Options:

  • --status, -s: Filter by status (complete, incomplete, all)
  • --topic, -t: Filter by main topic
  • --format: Output format (table, json, minimal)
  • --file, -f: Specify task file

Examples:

# List all incomplete tasks
npx cc-tasks list --status incomplete

# List tasks for a specific topic
npx cc-tasks list --topic "UI Components"

# Output as JSON
npx cc-tasks list --format json

get

Get detailed information about a specific task.

npx cc-tasks get <taskId>

Example:

npx cc-tasks get 2.1
# Shows full details for Task 2.1

status

Display task statistics and overall progress.

npx cc-tasks status

Output example:

Task Statistics:
Total Tasks: 24
Completed: 18 (75%)
In Progress: 4 (17%)
Not Started: 2 (8%)

By Topic:
- UI Components: 8/10 (80%)
- Backend Integration: 6/8 (75%)
- Testing: 4/6 (67%)

deps

Show task dependencies and dependency tree.

npx cc-tasks deps <taskId>

Options:

  • --reverse: Show tasks that depend on this task
  • --tree: Display as dependency tree

Example:

npx cc-tasks deps 3.0 --tree
# Task 3.0: Extract Section Components
# └── Requires:
#     ├── Task 1.1: Create Directory Structure
#     ├── Task 1.2: Analyze Current Components
#     └── Task 2.0: Extract Major UI Components

create

Create a new task interactively.

npx cc-tasks create

This will prompt you for:

  • Task ID
  • Task title
  • Main topic
  • Description
  • Subtasks
  • Required tasks
  • Validation criteria

update

Update task completion status.

npx cc-tasks update <taskId> <status>

Status options: complete, incomplete

Example:

npx cc-tasks update 2.1 complete

check

Toggle subtask completion status.

npx cc-tasks check <taskId> <subtaskIndex>

Example:

# Toggle the first subtask of task 2.1
npx cc-tasks check 2.1 1

# Toggle by partial text match
npx cc-tasks check 2.1 "Create directory"

validate

Toggle validation criteria completion status.

npx cc-tasks validate <taskId> <criterionIndex>

Example:

# Toggle the first validation criterion of task 2.1
npx cc-tasks validate 2.1 1

# Toggle by partial text match
npx cc-tasks validate 2.1 "Directory structure exists"

# Mark all validation criteria as complete
npx cc-tasks validate 2.1 --all

export

Export tasks to different formats.

npx cc-tasks export <format> [output]

Formats: json, html, csv

Examples:

# Export to JSON
npx cc-tasks export json tasks.json

# Export to HTML report
npx cc-tasks export html report.html

# Export to stdout
npx cc-tasks export json

watch

Watch for changes in task files and display live updates.

npx cc-tasks watch

Options:

  • --command, -c: Command to run on change
  • --file, -f: Specify task file to watch

Task Format Specification

Tasks must follow this Markdown format:

## Task <ID>: <Title>
- [x] **Complete** | - [ ] **Complete**
**Main Topic:** <Topic Name>
**Description:** <Detailed description>
**Subtasks:**
- [ ] Subtask description
- [x] Completed subtask
**Required Tasks:** <Comma-separated task IDs or "None">
**Validation:** 
- [ ] Validation criterion 1
- [x] Completed validation

Format Rules

  1. Task ID: Must follow semantic versioning pattern (e.g., 1.0, 2.1, 3.14)
  2. Completion Status: Use - [x] for complete, - [ ] for incomplete
  3. Required Fields: All fields (Main Topic, Description, Subtasks, Required Tasks, Validation) must be present
  4. Subtasks: At least one subtask is required
  5. Required Tasks: Use task IDs (e.g., "1.0, 1.1") or "None"

Configuration

Create a .cctasksrc file in your project root:

{
  "taskFile": "tasks.md",
  "validation": {
    "strict": true,
    "requireValidation": true
  },
  "export": {
    "defaultFormat": "json",
    "htmlTemplate": "custom-template.html"
  }
}

Examples

Project Refactoring Workflow

# 1. Parse and validate your task file
npx cc-tasks parse

# 2. View current status
npx cc-tasks status

# 3. List incomplete tasks
npx cc-tasks list --status incomplete

# 4. Work on a task and mark subtasks
npx cc-tasks get 2.1
npx cc-tasks check 2.1 1
npx cc-tasks check 2.1 2

# 5. Complete the task
npx cc-tasks update 2.1 complete

# 6. Export progress report
npx cc-tasks export html progress-report.html

Dependency Management

# Check what needs to be done before starting a task
npx cc-tasks deps 5.0

# See the full dependency tree
npx cc-tasks deps 5.0 --tree

# Find tasks that depend on current task
npx cc-tasks deps 2.0 --reverse

API Usage

You can also use cc-tasks programmatically:

const { TaskParser, TaskManager } = require('cc-tasks');

// Parse tasks
const parser = new TaskParser();
const tasks = await parser.parseFile('tasks.md');

// Query tasks
const manager = new TaskManager(tasks);
const incompleteTasks = manager.filter({ status: 'incomplete' });
const uiTasks = manager.filter({ topic: 'UI Components' });

// Update task
await manager.updateTask('2.1', { status: 'complete' });
await manager.toggleSubtask('2.1', 0);

// Export
const json = manager.exportJSON();
const html = manager.exportHTML();

Contributing

Contributions are welcome! Please follow these steps:

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Development Setup

# Clone the repository
git clone https://github.com/peerasak-u/cc-tasks-parser.git
cd cc-tasks-parser

# Install dependencies
npm install

# Run tests
npm test

# Run in development mode
npm run dev

License

MIT © Peerasak Unsakon

Acknowledgments

  • Inspired by the need for simple, version-controllable task management
  • Built for developers who prefer plain text over complex tools

Roadmap

  • [ ] GitHub integration for automatic issue creation
  • [ ] Task templates for common project types
  • [ ] Time tracking functionality
  • [ ] Multi-file task support
  • [ ] Web UI for task visualization
  • [ ] Integration with popular project management tools