How to describe a goal so PYNGYN plans it well

The plan PYNGYN generates is only as good as the goal you give it. A specific goal produces a specific plan, a vague one produces a generic starting point you'll spend more time reshaping.

What makes a goal specific

A well-written goal usually includes three things:

• The outcome: what "done" actually looks like
• Any hard date: a filing deadline, a launch date, a client commitment
• Relevant constraints: budget, team size, or dependencies on someone outside the project

Example

Weak: "Redesign the client onboarding process."

Stronger: "Redesign client onboarding to cut time-to-first-invoice from 3 weeks to 1, ready to pilot with two clients by June 15."

You can always refine after

You don't need a perfect goal on the first try. Generate a plan, then use "Editing and refining an AI-generated plan" to reshape it, adding detail is often easier once you can see a draft to react to.