todo-tracking

Coordinate GitHub Issues to track tasks, features, and bugs for the droneroute project.

49|15|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/fcsonline/droneroute --skill todo-tracking-fcsonline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-tracking
Source: https://github.com/fcsonline/droneroute/tree/main/.opencode/skills/todo-tracking
Command: npx skills add https://github.com/fcsonline/droneroute --skill todo-tracking-fcsonline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Issues are the canonical way to manage tasks, features, and bugs, but teams often drift without a standardized workflow.

Core Features & Use Cases

  • Centralizes task tracking in GitHub Issues for the droneroute project
  • Maps work sessions to issues, linking PRs, labels, and statuses for traceability
  • Supports starting, linking, and closing issues during development sprints

Quick Start

Create or select an issue at the start of a work session and reference it in your PRs to auto-close on merge.

Frequently Asked Questions about todo-tracking

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

FAQPage Schema
How do I track project tasks using GitHub Issues automatically?

The Skill tracks project work in GitHub Issues automatically by using issues as the single source of truth, linking PRs, labels, and statuses during work sessions to ensure traceability without relying on local TODO files.

Do I need the gh CLI to manage GitHub Issues for project tracking?

Yes, you need the gh CLI and GitHub authentication to view, create, and link GitHub Issues. This environment provides the necessary access to serve issues as the single source of truth for your project.

What is the best way to link a pull request to an existing GitHub Issue?

The best way to link a pull request to a GitHub Issue is to select or create an issue at the start of a work session and reference it in your PRs, which allows the issue to auto-close on merge.

Can I use local TODO files instead of GitHub Issues for bug hunts and feature requests?

No, you should not use local TODO files. The workflow uses GitHub Issues as the canonical single source of truth to manage bug hunts, feature requests, and tasks, ensuring standardized traceability across the repository.

Why should I use GitHub Issues for project management over local task tracking?

Using GitHub Issues for project management centralizes task tracking, maps development sprints to statuses, and prevents duplicate work. It establishes a standardized workflow that local TODO files cannot enforce across a team.