pro-plan

Extract project objectives, constraints, and success criteria into a strategic plan document.

7|Updated Jun 19, 2025

Search Tags:#project management #software development #strategic planning #project vision #objective definition

Ready to run

npx skills add https://github.com/Cassiiopeia/projectops --skill pro-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pro-plan
Source: https://github.com/Cassiiopeia/projectops/tree/main/skills/pro-plan
Command: npx skills add https://github.com/Cassiiopeia/projectops --skill pro-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers clarify the 'WHY' and 'WHAT' of a project before implementation, ensuring a clear direction without getting bogged down in implementation details.

Core Features & Use Cases

Strategic Planning: Assist in defining the strategic plan for a project, focusing on the 'WHY' and 'WHAT' without delving into 'HOW'.
User Interaction: Engage with users to extract the core requirements and objectives of the project.
Output Document: Generate a structured plan document that outlines the objectives, constraints, and success criteria of the project.

Quick Start

To initiate a strategic plan for a new feature, run the pro-plan skill with the project details.

Frequently Asked Questions about pro-plan

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

FAQPage Schema

How do I define a strategic project vision before starting software development?▼

Strategic planning eliminates unnecessary implementation details by focusing on the 'WHY' and 'WHAT' of a project. It extracts core requirements and objectives to generate a structured plan, ensuring a clear direction before any software development starts.

What is the best way to define project objectives without getting bogged down in implementation details?▼

The best way to define project objectives without implementation details is to focus strictly on the 'WHY' and 'WHAT'. By engaging users to extract constraints and success criteria, you generate a structured plan document that leaves the 'HOW' for later.

How do I extract project constraints and success criteria for a new software feature?▼

You extract project constraints and success criteria by engaging in strategic planning focused on the project vision. This involves user interaction to clarify the core requirements, resulting in a structured document that outlines the project's fundamental objectives.

Does strategic planning work for software development projects that lack a clear vision?▼

Yes, strategic planning is designed specifically for software development projects where a clear vision is crucial. It helps clarify the project's direction by defining the 'WHY' and 'WHAT' before committing to any implementation steps.

What limitations exist when defining a strategic plan focused only on the WHY and WHAT?▼

A limitation of defining a strategic plan focused only on the 'WHY' and 'WHAT' is that it does not specify the 'HOW'. Users must resolve implementation methods separately, as this process strictly outputs objectives, constraints, and success criteria without technical steps.