tracking-github

Configure GitHub Projects V2 boards and move tickets across phase columns.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/willietran/autoboard --skill tracking-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracking-github
Source: https://github.com/willietran/autoboard/tree/main/skills/tracking-github
Command: npx skills add https://github.com/willietran/autoboard --skill tracking-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates setup and ongoing progress tracking for GitHub Projects V2 by providing a repeatable, recoverable workflow for orchestrators and session agents, reducing manual coordination and miscommunication.

Core Features & Use Cases

  • Orchestrator setup: initialize a GitHub Projects V2 board, configure phase columns, create and persist IDs for resume.
  • Session reporting: move tickets across phases and post progress updates as sessions execute, including QA gates and coherence checks.
  • Recovery & resume: store IDs and mappings to rehydrate a run without re-creating the board.

Quick Start

Load this skill and run the orchestrator to connect your repository to a GitHub Projects V2 board and begin live progress tracking.

Frequently Asked Questions about tracking-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub Projects V2 progress tracking for autonomous feature work?

You automate GitHub Projects V2 tracking by loading this skill to run an orchestrator that connects your repository to a project board, configures phase columns, and posts live progress updates as sessions execute.

What is the best way to move tickets across phase columns in GitHub Projects V2 automatically?

The best way to move tickets automatically is by using a session reporting workflow that advances tickets through configured phase columns while executing autonomous feature work and posting progress updates.

Can I resume a GitHub project tracking run after restarting my environment?

Yes, you can resume a GitHub project tracking run after a restart because the orchestrator stores IDs and mappings to rehydrate the session without re-creating the project board.

Does GitHub Projects V2 tracking support QA gates and coherence checks during autonomous sessions?

GitHub Projects V2 tracking supports QA gates and coherence checks during autonomous sessions by moving tickets across phases and posting progress updates that verify work quality before advancing.

How do I rehydrate an autonomous orchestrator setup if the GitHub board is deleted?

If the GitHub board is deleted, you rehydrate the autonomous orchestrator setup by re-creating the project board using stored IDs and mappings, enabling a recoverable workflow that reduces manual coordination.