plan-project

Guide structured conversations to produce PROJECT-*.md project plans.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Utchash007/TermTales --skill plan-project-utchash007
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-project
Source: https://github.com/Utchash007/TermTales/tree/main/.agents/skills/plan-project
Command: npx skills add https://github.com/Utchash007/TermTales --skill plan-project-utchash007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan the work of new projects or epics by guiding a structured conversation to define scope, boundaries, and phased delivery.

Core Features & Use Cases

  • Structured planning: Visualize system boundaries, architecture direction, phase breakdown, and feature relationships to produce a comprehensive project plan artifact.
  • Domain exploration: Facilitate discussion to map domains, identify stakeholders, and capture requirements at the project level.
  • Plan generation: Output a PROJECT-*.md plan that downstream plan-feature will expand into feature-level plans.

Quick Start

Describe the project concept and goals to begin the phased project planning session.

Frequently Asked Questions about plan-project

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

FAQPage Schema
How do I create a phased delivery roadmap for a new project?▼

A project plan is generated by guiding a structured conversation to define scope and boundaries, mapping domains and architecture direction to output a phased delivery roadmap artifact.

What is the best way to plan system boundaries and architecture direction for an epic?▼

Planning system boundaries requires mapping domains and capturing project-level requirements through structured discussion, which visualizes architecture direction and phase breakdown for the epic.

How do I break down a brownfield initiative into a phased project plan?▼

To break down a brownfield initiative, guide a structured conversation to define scope and boundaries, mapping existing feature relationships to produce a phased delivery roadmap plan artifact.

Can I use this project planning approach for both greenfield and brownfield initiatives?▼

Yes, this project planning approach supports both greenfield and brownfield initiatives by guiding a structured conversation to define scope and map system boundaries for a phased delivery roadmap.

Does this project planning process generate feature-level plans or code?▼

No, this project planning process produces a top-level project plan artifact for downstream feature decomposition work, and does not dive into feature-level details or code.

Do I need a defined project concept before starting the phased project planning session?▼

Yes, you need to describe the project concept and goals to begin the phased project planning session, which then facilitates the structured conversation to define scope and boundaries.