agentleFS
hlhr202hlhr202/Conductor-for-all/.agents/skills/conductor-status/SKILL.md

conductor-status

Skill52 starsChanged 8 months agoApache-2.0View on GitHub

Displays the current progress of the project

7 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If ANY of these files are missing, you MUST halt the operation immediately.

    line 24
  2. Distinctive:

    Do NOT proceed to Status Overview Protocol.

    line 26
  3. Distinctive:

    Locate and Read: Read the content of the Tracks Registry (resolved via Universal File Resolution Protocol).

    line 34
  4. Very specific:

    Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format - [ ] Track: or …

    line 37
  5. Distinctive:

    Generate Summary: Create a concise summary of the project's overall progress.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.


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%).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.