plan

Generate detailed implementation plans with task breakdowns and dependencies.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/mguilarducci/vrau --skill plan-mguilarducci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/mguilarducci/vrau/tree/main/skills/plan
Command: npx skills add https://github.com/mguilarducci/vrau --skill plan-mguilarducci

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of translating an approved brainstorm into a concrete, actionable implementation plan, ensuring all necessary details for execution are captured.

Core Features & Use Cases

  • Structured Planning: Generates detailed plans including task breakdown, dependencies, and execution steps.
  • Workflow Integration: Seamlessly integrates into the Vrau workflow, ensuring prerequisites are met before planning begins.
  • Use Case: After a design is approved in the brainstorm phase, this Skill will create a step-by-step plan for developers, outlining each task, its dependencies, and when to commit code during the execution phase.

Quick Start

Use the plan skill to create a detailed implementation plan for the approved brainstorm.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a detailed implementation plan from an approved software design?

To create an implementation plan from an approved design, you need to break down tasks, identify code dependencies, and specify commit points. This ensures the approved brainstorm is translated into actionable execution steps for developers.

What is the best way to break down development tasks and define commit points?

The best way to break down development tasks is to structure the implementation plan sequentially, identifying dependencies and specifying exact commit points. This prevents integration conflicts and ensures code is committed at logical execution intervals.

How do I ensure prior workflow phases are approved before starting the implementation planning process?

To ensure prior workflow phases are approved before planning, you must integrate into a phased approach where prerequisites are met. The implementation planning process strictly requires prior phases to be approved and merged before proceeding.

Can I commit my implementation plan directly to the main branch?

No, you cannot commit your implementation plan directly to the main branch. Strict safety rules dictate never committing to the main branch and require utilizing separate reviewers for plan validation.

How does task dependency identification work during software development planning?

Task dependency identification during software development planning works by analyzing the approved brainstorm and structuring execution steps sequentially. It specifies exactly when to commit code, ensuring all prerequisite tasks are completed before dependents begin.