Project Status

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 conductor/tracks.md file, parsing its content, and summarizing the progress of tasks.

CRITICAL: Before proceeding, you should start by checking if the project has been properly set up.

1. Verify Tracks File: Check if the file conductor/tracks.md exists. If it does not, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run /conductor:setup to set up the plan, or restore conductor/tracks.md."
2. Verify Track Exists: Check if the file conductor/tracks.md is not empty. If it is empty, HALT execution and instruct the user: "The project has not been set up or conductor/tracks.md has been corrupted. Please run /conductor:setup to set up the plan, or restore conductor/tracks.md."

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.

---

1.1 SETUP CHECK

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

1. Check for Required Files: You MUST verify the existence of the following files in the conductor directory:

   • conductor/tech-stack.md
   • conductor/workflow.md
   • conductor/product.md

2. Handle Missing Files:

   • 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 conductor/tracks.md file.
2. Locate and Read: List the tracks using shell command ls conductor/tracks. For each of the tracks, read the corresponding conductor/<track_id>/plan.md 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%).