plan

Create and update structured .plan.md files in .cursor/plans directories.

2|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/gullitmiranda/.cursor --skill plan-gullitmiranda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/gullitmiranda/.cursor/tree/main/skills/plan
Command: npx skills add https://github.com/gullitmiranda/.cursor --skill plan-gullitmiranda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan creation and updates for projects are often inconsistent and scattered. This skill helps enforce a standard for storing and formatting project plans.

Core Features & Use Cases

  • Standardized plan location: Save plan files in .cursor/plans/ using the .plan.md extension to ensure consistency across projects.
  • Structured plan format: Use Objective, Tasks, Dependencies, Acceptance Criteria, and Notes sections to capture clear, actionable work.
  • Plan lifecycle support: Create new plans and update existing ones, enabling iterative planning and alignment across teams.

Quick Start

Create a new plan named "my-feature" and save it as .cursor/plans/my-feature.plan.md.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a standardized project plan format for product and engineering tasks?

A standardized project plan format uses Objective, Tasks, Dependencies, Acceptance Criteria, and Notes sections to capture actionable work. This structure ensures consistent documentation across product, engineering, and research planning contexts.

What is the best way to manage project planning documentation without timelines?

Managing project planning documentation without timelines involves structuring files around objectives, tasks, dependencies, and acceptance criteria. This approach enforces a standard format and avoids timelines unless explicitly requested.

How do I store project plans consistently across different workflows?

Store project plans consistently by saving them in a dedicated directory with a standard markdown extension. This enforces a uniform location and file format, keeping planning documentation organized for iterative updates.

Can I update existing project plans or only create new ones?

You can update existing project plans as well as create new ones. This lifecycle support enables iterative planning and alignment across teams by allowing continuous modifications to the structured documentation.

Does this planning format work for research and engineering contexts?

Yes, this planning format works for research and engineering contexts. It applies to planning tasks across product, engineering, and research environments by enforcing a standard structure with objectives, tasks, dependencies, and acceptance criteria.

What sections should a task management plan include for clear acceptance criteria?

A task management plan should include Objective, Tasks, Dependencies, Acceptance Criteria, and Notes sections. This standard structure ensures clear, actionable work and captures the necessary criteria to determine task completion.