conductorstatus

name	conductor:status
description	Displays the current progress of the project
disable-model-invocation	true
model	sonnet
allowed-tools	Read, Bash, Glob, Grep

0.0 PRE-LOADED PROJECT CONTEXT

The following project files have been automatically injected at skill invocation time. If any section shows "NOT FOUND", the file does not exist — Conductor may not be set up.

Conductor Index

!cat conductor/index.md 2>/dev/null || echo "NOT FOUND — conductor/index.md does not exist."

Tracks Registry (conductor/tracks.md)

!cat conductor/tracks.md 2>/dev/null || echo "NOT FOUND — conductor/tracks.md does not exist."

---

1.0 SYSTEM DIRECTIVE

You are an AI agent. Your primary function is to provide a status overview of the current tracks file. This involves reading the Tracks Registry file, parsing its content, and summarizing the progress of tasks.

CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

---

0.1 CONTEXT AND FILE RESOLUTION

If a user mentions a "plan" or asks about the plan, they are likely referring to the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md).

Universal File Resolution Protocol

PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):

1. Identify Index: Determine the relevant index file:

   • Project Context: conductor/index.md
   • Track Context: a. Resolve and read the Tracks Registry (via Project Context). b. Find the entry for the specific <track_id>. c. Follow the link provided in the registry to locate the track's folder. The index file is <track_folder>/index.md. d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken: 1. Resolve the Tracks Directory (via Project Context). 2. The index file is <Tracks Directory>/<track_id>/index.md.

2. Check Index: Read the index file and look for a link with a matching or semantically similar label.

3. Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.

   • Example: If conductor/index.md links to ./workflow.md, the full path is conductor/workflow.md.

4. Fallback: If the index file is missing or the link is absent, use the Default Path keys below.

5. Verify: You MUST verify the resolved file actually exists on the disk.

Standard Default Paths (Project):

• Product Definition: conductor/product.md
• Tech Stack: conductor/tech-stack.md
• Workflow: conductor/workflow.md
• Product Guidelines: conductor/product-guidelines.md
• Tracks Registry: conductor/tracks.md
• Tracks Directory: conductor/tracks/

Standard Default Paths (Track):

• Specification: conductor/tracks/<track_id>/spec.md
• Implementation Plan: conductor/tracks/<track_id>/plan.md
• Metadata: conductor/tracks/<track_id>/metadata.json

---

1.1 SETUP CHECK

PROTOCOL: Verify that the Conductor environment is properly set up.

1. Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:

   • Tracks Registry
   • Product Definition
   • Tech Stack
   • Workflow

2. Handle Failure:

   • If ANY of these files are missing, you MUST halt the operation immediately.
   • Announce: "Conductor is not set up. Please run /conductor:setup to set up the environment."
   • Do NOT proceed to Status Overview Protocol.

---

2.0 STATUS OVERVIEW PROTOCOL

PROTOCOL: Follow this sequence to provide a status overview.

2.1 Read Project Plan

1. Locate and Read: Read the content of the Tracks Registry (resolved via Universal File Resolution Protocol).
2. Locate and Read Tracks:
   • Parse the Tracks Registry to identify all registered tracks and their paths.
     • Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format - [ ] **Track: or the legacy format ## [ ] Track:.
   • For each track, resolve and read its Implementation Plan (using Universal File Resolution Protocol via the track's index file).

2.2 Parse and Summarize Plan

1. Parse Content:
   • Identify major project phases/sections (e.g., top-level markdown headings).
   • Identify individual tasks and their current status (e.g., bullet points under headings, looking for keywords like "COMPLETED", "IN PROGRESS", "PENDING").
2. Generate Summary: Create a concise summary of the project's overall progress. This should include:
   • The total number of major phases.
   • The total number of tasks.
   • The number of tasks completed, in progress, and pending.

2.3 Present Status Overview

1. Output Summary: Present the generated summary to the user in a clear, readable format. The status report must include:
   • Current Date/Time: The current timestamp.
   • Project Status: A high-level summary of progress (e.g., "On Track", "Behind Schedule", "Blocked").
   • Current Phase and Task: The specific phase and task currently marked as "IN PROGRESS".
   • Next Action Needed: The next task listed as "PENDING".
   • Blockers: Any items explicitly marked as blockers in the plan.
   • Phases (total): The total number of major phases.
   • Tasks (total): The total number of tasks.
   • Progress: The overall progress of the plan, presented as tasks_completed/tasks_total (percentage_completed%).