remove-track

Remove a specified track and all its tasks from every phase of a multi-phase tracker.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill remove-track
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-track
Source: https://github.com/HirogaKatageri/hirokata-cc-marketplace/tree/main/plugins/cc-tracker-plugin/skills/remove-track
Command: npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill remove-track

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe, irreversible removal of a track and all its tasks from a multi-phase tracker, helping teams keep project structures clean and up-to-date.

Core Features & Use Cases

  • Track deletion across all phases: Removes a specified track and its tasks from every phase, preserving tracker integrity.
  • Phase-aware cleanup: Updates phase structures and handles empty phases by marking them appropriately.
  • Safety prompts and confirmation: Warns about data loss and requires explicit confirmation unless an override flag is used.
  • Use Case: When a feature is canceled or deprecated, use this skill to remove its track and associated tasks from the tracker to prevent orphaned work items.

Quick Start

To remove a track named "authentication" from tracker "prod-tracker", run the command with the track name and tracker reference, for example: /remove-track prod-tracker --track=authentication. You can add --confirm to bypass prompts.

Frequently Asked Questions about remove-track

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

FAQPage Schema
How do I delete a track and all its tasks from a multi-phase markdown project tracker?

To delete a track from a multi-phase tracker, you run the remove-track command with the tracker name and specify the target track. It validates the track, removes it and its tasks from every phase, cleans up plan files, and updates tracker metadata.

What is the safest way to clean up deprecated feature tracks and orphaned tasks in a project tracker?

The safest way to clean up deprecated feature tracks is using a removal skill that validates the track and prompts for explicit confirmation before deleting tasks across all phases and updating the tracker files.

How do I bypass confirmation prompts when removing a track from a markdown tracker?

You can bypass confirmation prompts when removing a track by adding the --confirm flag to your command. This overrides the safety warning and executes the irreversible deletion immediately.

Does removing a track from a multi-phase tracker affect the other phases in the markdown file?

Removing a track updates the phase structures by deleting the track's tasks from every phase. It preserves overall tracker integrity and marks phases appropriately if they become empty after the cleanup.

Do I need any external dependencies to remove tracks and clean up tasks from local tracker files?

No external dependencies are required to remove tracks and clean up tasks. The skill operates entirely on local tracker files and relies only on the existing repository tooling.

What happens to associated plan files when a track is removed from a multi-phase tracker?

When a track is removed, associated plan files are cleaned up and deleted alongside the track's tasks. The tracker metadata is also updated to reflect the removal and maintain project structure integrity.