plan

Converts user task requests into structured PRDs and sprint plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Plan skill helps teams automatically translate vague requests into well-scoped PRDs and sprint plans, reducing miscommunication and rework.

Core Features & Use Cases

  • Contract-First planning: mirrors understanding back to the user to confirm scope before committing.
  • Correctness Discovery: uses a structured framework to define audience, risk, and verification to ensure high-quality plans.
  • PRD templating and habitat creation: outputs a ready-to-fill docs structure under docs/tasks/<area>/<category>/ with references to templates and required artifacts.
  • Sprint decomposition & artifact generation: creates sprint specs, progress tracking, and invariants in a formalised workflow.

Quick Start

Describe a new task and say plan to trigger PRD planning; the system will generate a PRD draft and sprint plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I translate a vague product request into a sprint plan and PRD?

To translate vague requests into a sprint plan and PRD, describe your task and trigger the planning workflow. It mirrors understanding back to confirm scope, applies correctness discovery, and outputs structured documentation with sprint-ready artifacts.

What is the Contract-First pattern in product management planning?

The Contract-First pattern in product management planning mirrors your task understanding back to you to confirm scope before committing. This reduces miscommunication and rework by ensuring requirements are validated before sprint decomposition begins.

How do I structure PRD documentation for multi-file features and refactors?

Structuring PRD documentation for multi-file features uses a templated habitat under docs/tasks/<area>/<category>/. This formalized structure references required templates and artifacts, ensuring comprehensive coverage for features, bugs, and refactors.

Does this PRD planning approach work for roadmap planning and bug fixes?

Yes, this PRD planning approach works for roadmap planning and bug fixes. It applies a structured correctness discovery framework to define audience, risk, and verification, ensuring high-quality plans across multi-file features and refactoring tasks.

What is the best way to decompose a product task into sprint specs?

The best way to decompose a product task into sprint specs is using a formalized workflow that generates sprint specs, progress tracking, and invariants. This follows PRD templating and correctness discovery to produce sprint-ready artifacts.

Why use a correctness discovery framework for product planning?

Use a correctness discovery framework for product planning to define audience, risk, and verification systematically. This structured approach ensures high-quality plans by validating scope and requirements before development starts, minimizing rework.