plan

Generate MVP-focused implementation plans with integrated test strategies.

1|Updated Nov 3, 2024
One-click install
npx skills add https://github.com/kingstinct/.github --skill plan-kingstinct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/kingstinct/.github/tree/main/planning/skills/plan
Command: npx skills add https://github.com/kingstinct/.github --skill plan-kingstinct

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create focused, minimal implementation plans for software development tasks, preventing scope creep and ensuring clarity on testing.

Core Features & Use Cases

  • MVP Planning: Generates plans adhering strictly to the Minimum Viable Product scope.
  • Test Strategy Definition: Includes a clear test plan tailored to the changes.
  • Context Gathering: Guides the process of gathering necessary issue context before planning.
  • Use Case: When assigned a new feature ticket, use this Skill to outline only the essential changes needed for the first release and define how to verify its functionality.

Quick Start

Generate an MVP plan for the new user authentication feature, including backend and frontend changes and integration tests.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an MVP plan that includes a test strategy for software development?

To create an MVP plan with a test strategy, gather issue context and filter by project scope to generate a concise implementation plan. This process defines backend integration tests, mobile E2E tests, and unit tests while strictly adhering to MVP scope to prevent feature creep.

What is the best way to prevent scope creep when planning a new feature ticket?

The best way to prevent scope creep is by generating a concise, MVP-focused implementation plan that filters project scope strictly. By adhering to strict planning principles, you outline only the essential changes needed for the first release and define how to verify functionality.

How do I define test strategies for backend integration and mobile E2E tests?

You define test strategies for backend integration and mobile E2E tests by integrating them directly into your MVP implementation plan. The planning process supports specifying these tests alongside unit tests where valuable, ensuring clarity on testing changes.

Can I use MVP planning for Scrum and project management tasks?

Yes, you can use MVP planning for Scrum and project management tasks to ensure clarity on testing and focused development. It generates concise implementation plans for software development, preventing scope creep by emphasizing only essential changes for the first release.

Do I need to gather issue context before generating an MVP implementation plan?

Yes, you need to gather issue context before generating an MVP implementation plan. The planning process guides context gathering and filters by project scope to ensure the resulting software development plan is accurate and strictly adheres to the Minimum Viable Product boundaries.