planning

Guide teams to gather requirements, define MVP scope, and break down tasks.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/poko8nada/honox-sample --skill planning-poko8nada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/poko8nada/honox-sample/tree/main/.github/skills/planning
Command: npx skills add https://github.com/poko8nada/honox-sample --skill planning-poko8nada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning phase guidelines that help teams gather requirements, define MVP scope, and break work into actionable tasks to avoid ambiguity and scope creep during feature development.

Core Features & Use Cases

  • Structured development methodology with an incremental path from MVP to product iterations.
  • Standardized templates and documentation layout to unify planning artifacts.
  • Clear workflow for requirement gathering, MVP scope definition, and task breakdown with required approvals.

Quick Start

Define your feature requirements, outline MVP scope, and break work into tasks, then obtain approvals before implementation.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I define MVP scope and break down tasks for a new feature?

Task breakdown for new features uses structured templates to map requirements into incremental MVP paths and actionable tasks. This standardized documentation layout unifies planning artifacts across teams to prevent scope creep.

What is the best way to gather requirements and avoid scope creep during feature development?

Gathering requirements through standardized templates and a defined approval workflow prevents scope creep. This structured methodology ensures teams define clear MVP scope and obtain required approvals before implementation.

Do I need to follow a specific approval workflow before implementing new feature specifications?

Yes, a defined approval workflow is required before implementation. You must submit feature requirements, MVP scope, and task breakdown using standardized templates to obtain necessary approvals across teams.

Can I use standardized templates to unify planning artifacts across multiple teams?

Standardized templates unify planning artifacts across multiple teams by providing a consistent documentation layout for requirement gathering, MVP scope definition, and task breakdown. This ensures clear communication and reduces ambiguity.

When should I use an MVP-driven planning workflow instead of building full feature specifications?

An MVP-driven planning workflow is ideal when starting new features, creating specifications, or breaking down work across teams. It establishes an incremental path from MVP to product iterations, minimizing scope creep and ambiguity.