# Plan Product Versions

Product ideas often grow too large before teams know what to build first. This skill turns requirements into a staged MVP and version roadmap with clear validation points.

## Install

```bash
npx skillstore add yunshu0909/version-planner
```

## Metadata

- Status: approved
- Slug: yunshu0909-version-planner
- Skillstore revision: r1
- Version status: missing
- Tree hash: 08ed311a2ffbe91f8914871afc11e04ee155d31359ba80e6770a76f4885e0c92
- Author: yunshu0909
- GitHub username: yunshu0909
- License: MIT
- Repository: https://github.com/yunshu0909/yunshu\_skillshub/tree/master/version-planner
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/yunshu0909-version-planner
- Manifest: https://skillstore.pages.dev/api/skills/yunshu0909-version-planner/manifest

## Capabilities

- Ask clarifying questions about pain points, users, required features, constraints, and unknowns.
- Extract core value, target users, feature lists, and feature dependencies from a product idea.
- Split work into V0.1 MVP, iterative V0.2 to V0.5 releases, and V1.0 readiness.
- Define validation points and explicit out-of-scope items for each planned version.
- Generate a structured version planning document with next actions and open questions.

## Use Cases

- Shape a New Product MVP: Turn a broad product idea into the smallest version that can validate the main user problem.
- Prioritize a Feature Backlog: Group requested features into staged releases with dependencies, exclusions, and validation goals.
- Prepare Build Scope: Create a version plan that developers can use before architecture design or sprint planning.

## Prompt Templates

### Plan a Simple MVP

```
Help me split this product idea into versions. The idea is: [describe product]. Ask me any key questions first.
```

### Create a Roadmap from Requirements

```
Create a V0.1 to V1.0 version plan for these requirements: [feature list]. Include what each version will not do.
```

### Refine an Existing Roadmap

```
Review this version plan and improve the sequence, validation points, and dependency order: [draft plan].
```

### Plan Under Constraints

```
Build a staged roadmap for [product] with these constraints: [platform, team size, timeline, technical limits]. Identify risks and open questions.
```

## Limitations

- It does not perform market research or validate customer demand by itself.
- It does not estimate delivery dates with project management accuracy.
- It does not replace technical architecture, security review, or implementation planning.
- It depends on user-provided requirements and constraints for useful prioritization.

## Best Practices

- Provide the core pain point, target user, required features, and known constraints before asking for a roadmap.
- Keep each version focused on one clear outcome and one validation point.
- Review the out-of-scope list before starting implementation.

## Anti Patterns

- Asking for every feature to ship in the MVP without priority tradeoffs.
- Using the roadmap as a fixed delivery commitment before technical review.
- Skipping clarification when the product idea is still vague.

## Security Audit

- Audited at: 2026-07-08T11:15:05.66\+00:00
- Summary: The external command findings are false positives caused by Markdown code fences and inline filename formatting in SKILL.md. The high entropy heuristic is also a false positive because the file is readable Markdown with Chinese text, not binary or encrypted content. No prompt injection or malicious intent was found.

## Stats

- Views: 131
- Downloads: 19
- Favorites: 1
- Popularity score: 0