product-planner

Transform natural language product goals into structured execution plans with artifacts.

2|1|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/lpding888/aiygw4.0 --skill product-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-planner
Source: https://github.com/lpding888/aiygw4.0/tree/main/skills/product_planner_skill
Command: npx skills add https://github.com/lpding888/aiygw4.0 --skill product-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Product Planner Skill acts as the central AI product manager that converts vague, natural language requirements into a complete, executable product plan. It orchestrates cross-team collaboration by producing standardized artifacts and ensures MVP delivery through contract-first governance.

Core Features & Use Cases

  • Generate clarifications: identify business goals, technical boundaries, and acceptance criteria.
  • Decompose work into department-specific task cards (Backend/Frontend/SCF/QA/Reviewer/Deploy/Billing Guard) with 4–12 hour granularity.
  • Produce OpenAPI/UI/event contracts to enable parallel development and traceability.
  • Create weekly milestones, timelines, and handoff documentation for stakeholder communication.
  • Use cases: a founder describes a CMS configurator; the Skill returns a full planning package ready for execution.

Quick Start

Tell me a product goal in plain language, for example: "Build a CMS configuration system in 4 weeks with a $1500 budget." I will return a complete planning package including clarifications, product spec, task cards, timeline, and handoff.

Frequently Asked Questions about product-planner

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

FAQPage Schema
How do I turn a vague product idea into an executable development plan?▼

To turn a vague product idea into an executable development plan, provide a natural language product goal to generate structured artifacts including clarifications, product spec, task cards, and timeline for cross-team MVP delivery.

What is contract-first governance in cross-team workflow planning?▼

Contract-first governance in cross-team workflow planning means producing OpenAPI, UI, and event contracts upfront. This enables parallel development across Backend, Frontend, and QA teams while ensuring traceability and standardized MVP delivery.

How do I generate department-specific task cards from a natural language product spec?▼

You generate department-specific task cards by inputting a plain language product goal. The system decomposes work into Backend, Frontend, SCF, QA, Reviewer, and Deploy task cards with 4 to 12 hour granularity for execution.

Can I use this workflow planning approach for a 4-week MVP project with a tight budget?▼

Yes, you can use this workflow planning approach for a 4-week MVP project with a tight budget. It accepts parameters like timeline and budget in plain text and returns a complete planning package with weekly milestones and handoff documentation.

What is the best way to create handoff documentation for stakeholder communication?▼

The best way to create handoff documentation for stakeholder communication is to define a product goal in natural language. The system automatically generates handoff.md alongside weekly milestones and timeline.md to align cross-team stakeholders.

Why do I need clarifications.yaml when planning an MVP delivery?▼

You need clarifications.yaml when planning an MVP delivery to explicitly identify business goals, technical boundaries, and acceptance criteria before development begins, preventing scope creep and ensuring cross-team alignment.