ctp

Identifies the latest Speckit worktree path and metadata from local .specify/GIT directories.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill ctp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctp
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/.claude/skills/ctp
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill ctp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly determine the current Speckit worktree location and its related metadata, reducing context-switching and confusion when working across multiple worktrees.

Core Features & Use Cases

  • Identify Worktree: Determine the active Speckit worktree path and its associated branch and source info.
  • Metadata Visibility: Expose key metadata like BASE_BRANCH, BRANCH_NAME, and SOURCE to guide development tasks.
  • Use Case: Before running heavy commands, verify you are in the correct Speckit worktree to avoid destructive edits.

Quick Start

Run the skill to display the latest Speckit worktree details.

Frequently Asked Questions about ctp

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

FAQPage Schema
How do I find the current Speckit worktree path for my repository?

To find the Speckit worktree path, run the skill to identify the active worktree location and its associated branch info for your current repository state.

What metadata is available for a Speckit worktree?

Speckit worktree metadata includes BASE_BRANCH, BRANCH_NAME, and SOURCE details, which help guide development tasks and verify the correct worktree context.

When do I need to verify my Speckit worktree location?

You need to verify your Speckit worktree location before running heavy commands to avoid destructive edits across multiple worktrees and reduce context-switching.

Does the Speckit worktree path skill require local git directories?

Yes, the skill requires access to local .specify/GIT directories and the Speckit project structure to fetch live worktree data and metadata.

Can I use this skill to check worktree info across versioned components?

Yes, you can apply this skill in workflows where quick verification of worktree location is needed across Speckit projects and versioned components.