スキル一覧に戻る
YuniorGlez

track-master

by YuniorGlez

Transform your Gemini CLI into a high-performance autonomous agentic environment. This repository provides a curated collection of tactical skills, advanced agent configurations, and automated protocol hooks used by elite engineering teams.

0🍴 2📅 2026年1月25日
GitHubで見るManusで実行

SKILL.md


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

スコア

総合スコア

60/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です