speckit-worktree-list

Aggregate git worktrees and spec artifacts into a status dashboard.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-worktree-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-worktree-list
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-worktree-list
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-worktree-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and monitor multiple git worktrees by aggregating their status, artifacts, and task progress into a single view to reduce context switching and manual checks.

Core Features & Use Cases

  • List all worktrees with paths, branches, and HEAD commits.
  • Detect per-worktree artifacts (spec.md, plan.md, tasks.md, research.md) and track task completion.
  • Classify worktrees as Active, Idle, Stale, Merged, or Orphaned to inform cleanup decisions.
  • Use as a dashboard for parallel feature development and quick health checks across a spec-kit project.

Quick Start

Run the speckit-worktree-list command to generate the live dashboard of your repository.

Frequently Asked Questions about speckit-worktree-list

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

FAQPage Schema
How do I monitor multiple git worktrees and feature branches in one view?

To monitor multiple git worktrees, you can aggregate their status, artifacts, and task progress into a single dashboard. This reduces context switching by classifying worktrees as Active, Idle, Stale, Merged, or Orphaned for quick health checks across parallel feature branches.

How do I track task progress and spec artifacts across different git worktrees?

Tracking task progress across git worktrees involves detecting per-worktree artifacts like spec.md, plan.md, tasks.md, and research.md. By parsing these files, you can assess task completion and artifact visibility for each branch without manually checking each directory.

What is the best way to coordinate parallel feature development using spec-kit?

Coordinating parallel feature development with spec-kit requires aggregating branch paths, HEAD commits, and artifact status. A centralized worktree dashboard provides the necessary visibility to assess project health and inform cleanup decisions for merged or orphaned branches.

Do I need a .specify directory to use a git worktree status dashboard?

Yes, a .specify directory is required to use this worktree status dashboard. The tool parses the spec-kit structure within this directory to detect artifacts and track task completion, and it also requires git to list worktrees and read HEAD commits.

Can I identify stale or orphaned git worktrees for repository cleanup?

Yes, you can identify stale or orphaned git worktrees for cleanup. The dashboard classifies each worktree's status as Active, Idle, Stale, Merged, or Orphaned, helping you quickly spot abandoned feature branches and safely remove them.

Why does my worktree dashboard require parsing the .specify directory?

The worktree dashboard parses the .specify directory to extract spec-kit artifacts like spec.md and tasks.md. This parsing is necessary to map task progress and feature specifications to their corresponding git worktrees, enabling comprehensive status assessment.