project-management
必须主动使用,当用户要求:创建PROJECT.md、设置PROJECT.md、初始化项目跟踪、创建工单、创建问题、编写功能文档、创建PRD、创建产品需求、管理TODO.md、管理STATUS.md、跟踪项目进度、"添加功能"、"改进X以允许Y"、"处理下一个问题"、"处理下一个功能"、"规划功能"、"分解任务"或任何项目管理/任务管理活动时。当用户在任何上下文中提到PROJECT.md时也加载此技能。此技能通过docs/PROJECT.md或外部工具(GitHub Projects、Jira)处理所有项目规划、文档和工作跟踪。
name: project-management description: MUST BE LOADED BEFORE modifying docs/PROJECT.md. Also load when user mentions PROJECT.md in ANY form (docs/PROJECT.md, @docs/PROJECT.md, "the project file", etc.) or discusses tasks/tracking. Triggers include: "add a task", "add this task", "update PROJECT.md", "mark as done", "mark complete", "track this", "next task", "what's next", "work on next", create tickets/issues, write feature docs, create PRD, manage TODO.md/STATUS.md, "add a feature", "improve X to allow Y", plan features, break down tasks, or ANY project/task management discussion. This skill handles all project planning, documentation, and work tracking through docs/PROJECT.md or external tools (GitHub Projects, Jira).
Project Management
This skill manages project tasks and documentation for AI-driven development. All work is tracked in docs/PROJECT.md (or linked external tools) and results in pull requests.
Core Principles
- Single Source of Truth -
docs/PROJECT.mdis the central tracking document - One Task = One PR - Every task represents work that results in a single pull request
- Clarify Before Acting - Use AskUserQuestion to resolve ambiguity
- Research First - Use available agents to understand requirements before planning
When This Skill Triggers
CRITICAL: Load this skill BEFORE reading, modifying, or editing docs/PROJECT.md. Do not use Read/Edit tools on PROJECT.md without loading this skill first.
Load this skill IMMEDIATELY when:
- About to modify PROJECT.md - Before ANY edit to docs/PROJECT.md, load this skill first
- Mentions PROJECT.md in ANY form:
docs/PROJECT.md,@docs/PROJECT.md, "project file", "project tasks" - Says: "add a task", "add this task", "new task", "track this"
- Says: "mark as done", "mark complete", "check off", "finished this"
- Says: "next task", "what's next", "work on next", "next issue", "next feature"
- Discusses tasks, features, or project tracking in general
- Asks to create tickets, issues, or feature documentation
- Requests PRD, product requirements, or feature specs
- Mentions TODO.md, STATUS.md, or project tracking
- Says "add a feature that does X" or "improve X to allow Y"
- Asks to plan, break down, or organize work
Available Agents
Research Agents (Use Liberally)
agent-fx-research:tech-scout- Research libraries, technologies, solutionsagent-Explore- Explore codebase structure, patterns, implementationsagent-Plan- Design implementation plans
Development Agents
agent-fx-dev:coder- Implement features, fix bugsagent-fx-dev:planner- Create detailed implementation plansagent-fx-dev:pr-preparer- Prepare and create pull requestsagent-fx-dev:sdlc- Orchestrate complete development lifecycle
GitHub Integration
When working with GitHub issues or projects:
- Load the GitHub skill first:
Skilltool withskill="fx-dev:github" - Use
ghCLI for all GitHub operations
docs/PROJECT.md
To create or understand the PROJECT.md format, read the template at:
references/project-md-template.md
Task Format Rules
- Flat list - No categories or groupings. Just tasks in priority order.
- Up to 3 levels - Feature → Task → Subtask (2-space indent per level)
- One top-level item = One PR - Each feature/task results in a single PR
- Mark completion:
- [x] Task name (PR #N) - Link issues:
- [ ] Task (#123)when linked to GitHub issue
Workflows
Workflow 1: Feature Requests
When user says "add a feature that does X" or "improve X to allow Y":
Analyze deeply
- Use
agent-Exploreto understand current codebase - Use
agent-fx-research:tech-scoutif technology decisions needed
- Use
Determine scope
- Single PR scope? → Proceed to implementation
- Multi-PR scope? → Propose task breakdown
Clarify ambiguity via AskUserQuestion:
- "This could be implemented as [A] or [B]. Which approach?"
- "I've identified these tasks: [list]. Add to PROJECT.md?"
Update PROJECT.md with tasks (if breakdown needed)
Get approval then begin work on first task
Workflow 2: "Work on Next"
When user says "work on next issue", "next feature", or "what's next":
Read docs/PROJECT.md
Select next uncompleted task (top of list = highest priority)
Announce the task to user
Execute using development agents
Update PROJECT.md marking task complete with PR number
Ensure PR includes PROJECT.md update
Workflow 3: Creating PRDs
When user requests PRD or feature documentation:
Gather requirements via AskUserQuestion
Research context using
agent-Exploreandagent-fx-research:tech-scoutCreate PRD in
docs/folderUpdate PROJECT.md with reference and tasks
Create PR with documentation
Workflow 4: External Tool Integration
When GitHub Projects, Jira, or other tools are available:
Load GitHub skill if using GitHub
Create issues/tickets in external tool
Update PROJECT.md to reference external tracking
Link tasks between PROJECT.md and external tool
Workflow 5: Initial Setup
When docs/PROJECT.md doesn't exist:
Explore the project using
agent-ExploreAsk about tracking preferences via AskUserQuestion:
- "Use docs/PROJECT.md only"
- "Use GitHub Issues + PROJECT.md"
- "Other (Jira, Linear, etc.)"
Read the template at
references/project-md-template.mdCreate PROJECT.md with initial backlog
Migrate existing tracking (TODO.md, STATUS.md) if present
Critical Requirements
Every Task Completion Must:
- Mark task complete in PROJECT.md:
- [x] Task (PR #N) - Include PROJECT.md update in the PR
Before Creating Tasks:
- Verify task is atomic (single PR scope)
- Ensure description is clear and actionable
When Ambiguity Exists:
- ALWAYS use AskUserQuestion to clarify
- Present concrete options
- Wait for user decision before proceeding