plan-project

Create phased project plans with scope, architecture, and feature sequencing.

41|15|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/foyzulkarim/skills --skill plan-project-foyzulkarim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-project
Source: https://github.com/foyzulkarim/skills/tree/main/dev-pipeline/skills/plan-project
Command: npx skills add https://github.com/foyzulkarim/skills --skill plan-project-foyzulkarim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures ambiguous project ideas or docs and turns them into a structured, phased project plan so developers can understand scope, system boundaries, and dependencies before feature-level work begins.

Core Features & Use Cases

  • Guided discovery: Lead a multi-phase conversation to clarify goals, constraints, and user journeys for large initiatives.
  • Feature mapping: Identify the major features, their relationships, and the architecture direction needed before diving into detailed design.
  • Delivery phasing: Recommend a phased rollout order with clear goals, riskiest work up front, and reusable foundations before consumer-facing experiences.
  • Use Case: When a product team needs to plan a cross-platform launch spanning multiple features, this skill collects context, defines the system, and delivers a PROJECT-*.md plan for downstream planning.

Quick Start

Use plan-project to guide a structured conversation and draft a phased project plan for your new multi-feature initiative.

Frequently Asked Questions about plan-project

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

FAQPage Schema
How do I structure a phased project plan for a multi-feature initiative?

To structure a phased project plan, you must clarify scope, map feature dependencies, and define delivery sequencing. This approach breaks ambiguous project ideas into milestone-focused phases with clear system boundaries before feature-level work begins.

What is the best way to decompose cross-platform features before detailed design?

Feature decomposition for cross-platform initiatives requires guided discovery to identify major features and their relationships. Mapping architecture direction early clarifies system boundaries and highlights reusable foundations needed before consumer-facing experiences.

How do I sequence delivery phases to prioritize riskiest work up front?

Sequencing delivery phases involves defining a phased rollout order that places the riskiest work up front. By capturing dependencies and establishing reusable foundations first, downstream plan-feature sessions can tackle consumer-facing experiences with reduced risk.

Can I use this for planning cross-feature initiatives when I only have an ambiguous spec?

Yes, you can use this for cross-feature initiatives when you only have an ambiguous spec. It captures ambiguous project ideas or docs and leads a multi-phase conversation to clarify goals, constraints, and user journeys before drafting a structured plan.

When do I need to define system boundaries before starting feature-level planning?

You need to define system boundaries before feature-level planning when a developer describes a large project requiring architecture direction. Establishing these boundaries early ensures downstream sessions know exactly which features to tackle first.