smithery/yuniorglez

track-master

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

Installation

$ npx skills add smithery/yuniorglez --skill track-master

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/yuniorglez · top by installs.

npx skills add smithery/yuniorglez

Browse all from smithery/yuniorglez

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,248 B
  • docs SUMMARY.md 148 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

🛤️ 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