project-tracking-patterns

Automate progress tracking by updating progress files and syncing Flyee after each task.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill project-tracking-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-tracking-patterns
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/project-tracking-patterns
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill project-tracking-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates progress tracking across long-running workflows by updating progress files, recording history, and syncing Flyee after each task.

Core Features & Use Cases

  • Enforces per-epic progress updates in PROJECT-PROGRESS.md or LEGACY-PROGRESS.md.
  • Records a running history of actions and ensures Flyee synchronization after each task.
  • Provides deterministic task synchronization and audit-ready artifacts for reviews.

Quick Start

Enable and start tracking progress for your current epic, and ensure Flyee synchronization after each task.

Frequently Asked Questions about project-tracking-patterns

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

FAQPage Schema
How do I automate progress tracking for long-running project workflows?

Automate progress tracking for multi-phase projects by standardizing updates in PROJECT-PROGRESS.md files, recording action history, and enforcing Flyee task synchronization after each phase to maintain audit-ready artifacts.

How do I maintain an audit trail for epic progress updates?

Maintain an audit trail for epics by recording a running history of actions and enforcing standardized updates in PROJECT-PROGRESS.md or LEGACY-PROGRESS.md after each task to generate audit-ready artifacts.

Does this workflow tracking method require mandatory task synchronization with Flyee?

Yes, mandatory task synchronization with Flyee is enforced as a blocker. It performs per-epic sync checks via task APIs to ensure every task is synchronized across multi-phase projects.

What's the best way to standardize progress updates across multi-phase projects?

The best way to standardize progress updates is enforcing structured updates in PROJECT-PROGRESS.md or LEGACY-PROGRESS.md after each phase, combined with mandatory Flyee synchronization to maintain consistent tracking.

Can I use LEGACY-PROGRESS.md for project tracking instead of PROJECT-PROGRESS.md?

Yes, you can use LEGACY-PROGRESS.md for project tracking. The workflow enforces per-epic progress updates in either LEGACY-PROGRESS.md or PROJECT-PROGRESS.md while ensuring Flyee synchronization after each task.

When should I not use automated project tracking for my workflows?

You should avoid automated project tracking for short-lived tasks or single-phase workflows. This approach applies to multi-phase projects and epics requiring per-epic sync checks, mandatory Flyee synchronization, and standardized progress file updates.