project-plan

Update PROJ/TODO/WAIT entries and notes in a central project.org file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jamie-Cui/skills --skill project-plan-jamie-cui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-plan
Source: https://github.com/Jamie-Cui/skills/tree/main/project-plan
Command: npx skills add https://github.com/Jamie-Cui/skills --skill project-plan-jamie-cui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes project planning by treating a single project.org file as the truth source for plans, deadlines, notes, and summaries, enabling consistent planning and governance across the team.

Core Features & Use Cases

  • Read active PROJ/TODO/WAIT items from the central file and present actionable paths.
  • Write agreed plans, update statuses, and append notes or summaries under * Note after reviews or discussions.
  • Ensure completed work is marked DONE and keep the project file synchronized with real-world progress.

Quick Start

Invoke $project-plan to review current plans, select a path to execute, or update a task in the project file.

Frequently Asked Questions about project-plan

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

FAQPage Schema
How do I manage project plans and tasks in a central org file?

To manage project plans in a central org file, use a project-plan Skill to coordinate PROJ, TODO, WAIT, and DONE states. It reads and updates your project.org file directly, keeping deadlines, notes, and summaries aligned during planning sessions and reviews.

Can I update task states like TODO and WAIT during a planning session?

Yes, you can update task states like TODO and WAIT during planning sessions. The Skill applies rules to read active items from your project.org file, update their statuses, and append notes or summaries under the * Note section after discussions.

What is the best way to keep project notes synchronized with real-world progress?

The best way to keep project notes synchronized is to treat a single project.org file as the truth source. The Skill marks completed work as DONE and appends review summaries under * Note, ensuring your project file reflects actual progress.

Does this project planning approach work for team collaboration and reviews?

Yes, this project planning approach works for team collaboration and reviews. It centralizes plans, deadlines, and summaries in one file, enabling consistent planning and governance across the team by presenting actionable paths from active items.

How do I mark a project task as DONE in the central file?

To mark a project task as DONE in the central file, invoke the Skill during a status update after work finishes. It applies defined rules to update the project.org file, ensuring the completed task state is properly recorded and synchronized.

Why use a single org file for task management instead of scattered notes?

Using a single org file for task management centralizes plans and summaries, solving the problem of scattered notes. It serves as the truth source for deadlines and statuses, ensuring consistent project governance and keeping plans aligned with real-world progress.