track-master

Senior Progress Analyst & Conductor Strategist. Expert in Predictive Project Tracking and Agentic Milestone Management for 2026.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "track-master" with this command: npx skills add yuniorglez/gemini-elite-core/yuniorglez-gemini-elite-core-track-master

🛤️ 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
  2. The "Do Not" List (Anti-Patterns)
  3. Predictive Risk Analysis
  4. Agentic Milestones & DoD
  5. Conductor System Architecture
  6. Stakeholder Reporting (The Vibe)
  7. 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-PatternWhy it fails in 2026Modern Alternative
Guessing Progress %Leads to false stakeholder security.Use Verifiable Technical Signals.
Ignoring Commit GapsMasks stagnation in the mission.Compare Plan vs. Commit Log.
Manual TrackingToo slow for agentic velocity.Use Automated Registry Updates.
Thin Blockers"I'm stuck" is useless.Provide Actionable Remediation.
Over-Detailed ReportsStakeholders 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 for details.


📖 Reference Library

Detailed deep-dives into Project Orchestration:


Updated: January 22, 2026 - 21:35

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

subagent-orchestrator

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

git-automation

No summary provided by upstream source.

Repository SourceNeeds Review
General

filament-pro

No summary provided by upstream source.

Repository SourceNeeds Review
General

pdf-pro

No summary provided by upstream source.

Repository SourceNeeds Review