plan-features

Translate validated product ideas into structured implementation plans with prioritized tasks.

Updated May 16, 2026
One-click install
npx skills add https://github.com/aryaxt/aryaxt-skills --skill plan-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-features
Source: https://github.com/aryaxt/aryaxt-skills/tree/main/skills/plan-features
Command: npx skills add https://github.com/aryaxt/aryaxt-skills --skill plan-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in translating validated product ideas into a comprehensive implementation plan, ensuring a structured approach to development.

Core Features & Use Cases

  • Implementation Planning: Breaks down product ideas into actionable tasks with detailed specifications.
  • Prioritization: Organizes tasks into MVP, V1, and V2 categories based on priority.
  • Documentation: Generates a markdown document outlining the plan, including infrastructure, data models, and UI components.

Quick Start

Run the plan-features skill with the project path, product name, and feature list to generate an implementation plan.

Frequently Asked Questions about plan-features

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

FAQPage Schema
How do I create an implementation plan for validated product ideas?

An implementation plan breaks down validated product ideas into actionable tasks with detailed specifications. It organizes tasks into MVP, V1, and V2 priority categories and generates a markdown document outlining infrastructure, data models, and UI components.

What is the best way to break down software development tasks for a new feature?

Breaking down software development tasks involves translating feature requirements into prioritized MVP, V1, and V2 categories. This structured approach ensures tasks have detailed specifications and are documented alongside necessary infrastructure and data models.

How does product planning prioritize tasks into MVP, V1, and V2 categories?

Product planning prioritizes tasks by organizing them into MVP, V1, and V2 categories based on feature requirements and project priority. This ensures a structured implementation plan that documents infrastructure, data models, and UI components sequentially.

Do I need existing project infrastructure details to generate a feature implementation plan?

Yes, generating a feature implementation plan requires analyzing existing project infrastructure and feature requirements. This analysis ensures the resulting markdown documentation accurately reflects data models, UI components, and task specifications.

What documentation format is generated for project management and task breakdown?

Project management and task breakdown documentation is generated as a markdown document. This file outlines the complete implementation plan, including infrastructure details, data models, UI components, and prioritized task specifications.

Can I use task breakdown planning for software development without prior feature validation?

Task breakdown planning for software development is designed specifically for validated product ideas. Without prior feature validation, the implementation plan may lack the necessary infrastructure analysis and accurate task specifications required for structured development.