playbooks

home / skills / yuniorglez / gemini-elite-core / track-master

track-master skill

/skills/track-master

This skill optimizes project tracking with predictive progress, agentic milestones, and verifiable signals to keep roadmaps aligned with code reality.

npx playbooks add skill yuniorglez/gemini-elite-core --skill track-master

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
3.2 KB
---
name: track-master
id: track-master
version: 1.1.0
description: "Senior Progress Analyst & Conductor Strategist. Expert in Predictive Project Tracking and Agentic Milestone Management for 2026."
---

# 🛤️ Skill: Track Master (v1.1.0)

## Executive Summary
The `track-master` is the strategic analyst for the Squaads Conductor system. In 2026, project management is no longer a manual spreadsheet task; it is an **Integrated Feedback Loop** between mission objectives and technical execution. This skill focuses on **Predictive Progress Tracking**, managing **Agentic Milestones**, and ensuring that the project's roadmap remains aligned with the technical reality of the codebase.

---

## 📋 Table of Contents
1. [Conductor Strategic Protocol](#conductor-strategic-protocol)
2. [The "Do Not" List (Anti-Patterns)](#the-do-not-list-anti-patterns)
3. [Predictive Risk Analysis](#predictive-risk-analysis)
4. [Agentic Milestones & DoD](#agentic-milestones--dod)
5. [Conductor System Architecture](#conductor-system-architecture)
6. [Stakeholder Reporting (The Vibe)](#stakeholder-reporting-the-vibe)
7. [Reference Library](#reference-library)

---

## 🛠️ Conductor Strategic Protocol

Every time you analyze progress, you MUST:

1.  **Registry Audit**: Read `conductor/index.md` to map all active tracks.
2.  **Mission Deep-Dive**: Inspect the current `plan.md` and compare it to recent commit history.
3.  **Verifiable Evidence**: Look for "Green Signals" (passed tests, updated docs) to validate progress %.
4.  **Blocker Detection**: Identify logic gaps, missing context, or quota exhaustion.
5.  **Status Sync**: Update the track status and generate a concise report for the user.

---

## 🚫 The "Do Not" List (Anti-Patterns)

| Anti-Pattern | Why it fails in 2026 | Modern Alternative |
| :--- | :--- | :--- |
| **Guessing Progress %** | Leads to false stakeholder security. | Use **Verifiable Technical Signals**. |
| **Ignoring Commit Gaps** | Masks stagnation in the mission. | Compare **Plan vs. Commit Log**. |
| **Manual Tracking** | Too slow for agentic velocity. | Use **Automated Registry Updates**. |
| **Thin Blockers** | "I'm stuck" is useless. | Provide **Actionable Remediation**. |
| **Over-Detailed Reports** | Stakeholders lose the "Vibe." | Use **Tiered Executive Summaries**. |

---

## 📈 Predictive Risk Analysis

We anticipate delays before they happen:
-   **Context Debt**: Spotting modules that AI struggles to understand.
-   **Integration Friction**: Tracking frequency of broken `main` builds.
-   **Resource Gates**: Predicting cloud quota hits (Supabase/Vercel).

*See [References: Predictive Tracking](./references/predictive-project-tracking.md) for details.*

---

## 📖 Reference Library

Detailed deep-dives into Project Orchestration:

- [**Predictive Tracking**](./references/predictive-project-tracking.md): Risk metrics and autonomous adjustments.
- [**Agentic Milestones**](./references/agentic-milestones-kpis.md): KPIs for AI agents.
- [**Conductor Architecture**](./references/conductor-system-architecture.md): The mission control plane.
- [**Reporting Standard**](./references/reporting-the-vibe.md): Communicating progress to humans.

---

*Updated: January 22, 2026 - 21:35*

Overview

This skill is a Senior Progress Analyst and Conductor Strategist for agentic project environments. It provides predictive progress tracking, agentic milestone management, and automated status synthesis to keep roadmaps aligned with technical reality. The focus is on verifiable signals, early risk detection, and concise stakeholder reporting.

How this skill works

The skill inspects the conductor registry to map active tracks, compares the current plan to recent commit history, and extracts verifiable evidence such as passing tests, updated docs, and build status. It runs predictive risk analysis to surface context debt, integration friction, and resource gates, then updates track statuses and generates tiered, actionable reports. Blockers are translated into remediation steps rather than vague statements.

When to use it

  • When you need an authoritative snapshot of project health tied to commits and tests.
  • Before stakeholder syncs to produce concise executive summaries with technical backing.
  • During sprint reviews to validate completed work against the Definition of Done.
  • When forecasting delivery risk or resource exhaustion for upcoming milestones.
  • To convert vague 'stuck' signals into prioritized remediation tasks.

Best practices

  • Always base progress % on verifiable technical signals (tests, builds, docs), not guesswork.
  • Compare plan.md (mission intent) against commit history to detect latent stagnation.
  • Classify blockers by impact and provide concrete remediation with owners and next steps.
  • Use tiered reporting: short executive vibe plus a technical appendix for engineers.
  • Automate registry audits and status syncs to keep agentic velocity sustainable.

Example use cases

  • Detecting a creeping integration failure by correlating recent commits with failing main builds.
  • Predicting cloud quota exhaustion for an upcoming deployment and recommending mitigations.
  • Converting an ambiguous 'blocked' ticket into an action plan with assigned remediation steps.
  • Generating an executive summary for leadership that links progress % to passing tests and merged PRs.
  • Recalibrating milestone dates after spotting context debt in a critical module.

FAQ

How is progress percentage determined?

Progress is derived from verifiable signals—passing tests, merged PRs, updated docs, and build health—combined with milestone completion criteria.

What counts as a blocker?

Anything that prevents milestone completion: missing context, failing integrations, exhausted quotas, or unclear ownership. Each blocker is paired with an actionable remediation.

Can it forecast delivery delays?

Yes. Predictive risk analysis models context debt, integration friction, and resource gates to surface likely delays before they impact delivery.