project-management

Manages project tasks and change documents in docs/tasks.md and docs/changes/ directories.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/fx/skills --skill project-management-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-management
Source: https://github.com/fx/skills/tree/main/skills/project-management
Command: npx skills add https://github.com/fx/skills --skill project-management-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It keeps AI-driven development work organized by enforcing a single source of truth for tasks, preventing duplicated or stale task tracking across docs/tasks.md, docs/changes/ change documents, and external trackers like GitHub Issues or Jira. ## Core Features & Use Cases - Change-document-first tracking: Routes feature work into docs/changes/ documents and reserves docs/tasks.md strictly for orphan tasks, with a strict no-duplication rule. - Task lifecycle workflows: Handles feature requests, "work on next" selection, task breakdown into PR-scoped checklists, and initial docs structure setup. - Index synchronization: Keeps docs/index.yml and docs/index.md in sync with change document status in the same PR that completes the work. - Use Case: When a user says "add a feature that does X", the skill checks for an existing spec, creates or updates a change document with PR-scoped tasks, gets approval, and tracks completion with PR numbers. ## Quick Start Ask the agent to add a new task for your feature or to work on the next uncompleted task in the project.

Frequently Asked Questions about project-management

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

FAQPage Schema
How do I track tasks for a new feature in an AI-driven project?▼

Feature work should be tracked in a docs/changes/ change document, not docs/tasks.md. The skill checks for an existing spec, creates or updates a change document with PR-scoped checkbox tasks, and gets user approval before implementation begins.

What is the difference between docs/tasks.md and docs/changes/ files?▼

docs/changes/ documents hold feature-level task lists tied to specific changes and are the primary tracking location. docs/tasks.md is a catch-all only for orphan work not tied to any change document, and tasks must never be duplicated between them.

Can I use GitHub Issues or Jira instead of markdown task files?▼

Yes, if the project's AGENTS.md configures an external tracker such as task-tracking: github-issues or jira, the skill creates issues in that tool. docs/tasks.md then becomes a lightweight reference, and completion is marked in both places.

Why must docs/index.yml and docs/index.md be updated with every status change?▼

These index files are how contributors discover change document status, so they must be updated in the same PR that changes a document's status. Leaving them stale causes drift that requires manual cleanup later.

When should a task not be added to docs/tasks.md?▼

Never add a task to docs/tasks.md if the work relates to an existing spec or change document. Tasks tied to a change must live in that change document, and each task exists in exactly one place.