rune-plan

Generates master plans and self-contained phase files from requirements for phased implementation.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-plan-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-plan
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-plan
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-plan-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large implementation tasks planned as a single monolithic document overflow context windows and cause coding agents to miss details, invent file paths, or skip error handling. This Skill decomposes requirements into a concise master plan plus self-contained phase files that any model can execute accurately. ## Core Features & Use Cases - Master Plan + Phase Files: Produces an overview plan under 80 lines plus detailed phase files under 200 lines each, with mandatory sections for data flow, code contracts, failure scenarios, and rejection criteria. - Wave-Based Task Grouping: Organizes tasks into parallel-safe waves with explicit dependency metadata, file-overlap detection, and cycle checks before execution. - Multiple Planning Modes: Supports implementation planning, feature specification (PRD-style specs), and roadmap planning with ICE scoring. - Use Case: Given a requirements document for a new authentication feature, the Skill scans the codebase, produces a 3-phase master plan, and writes phase files with exact file paths, test tasks, and acceptance criteria that a coding agent executes one phase per session. ## Quick Start Ask the agent to plan the implementation of your feature, for example: create a phased implementation plan for adding user authentication with email verification.

Frequently Asked Questions about rune-plan

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

FAQPage Schema
How do I break a large feature into phases for an AI coding agent?

Classify complexity first: tasks with 3+ phases, 5+ files, or 100+ lines of change need a master plan plus separate phase files. Each phase file must be self-contained with data flow, code contracts, tasks, and acceptance criteria so the executing agent needs no other context.

What should an implementation plan for a coding agent include?

Each phase needs exact file paths, function signatures as code contracts, a failure scenarios table, explicit rejection criteria listing anti-patterns to avoid, test tasks for every code change, and cross-phase context describing what prior phases provide.

When is a single inline plan enough instead of multiple phase files?

Inline plans are acceptable only for trivial tasks: 1-2 phases, fewer than 5 files touched, and under 100 lines of estimated change. If any threshold is exceeded, the task requires a master plan plus separate phase files.

How do I prevent parallel tasks from conflicting on the same files?

Group tasks into waves where same-wave tasks have no dependencies, and require every task to declare touches, provides, requires, and depends_on metadata. Run pre-dispatch validation to block file overlaps, missing dependencies, and dependency cycles.

What are the limitations of monolithic implementation plans?

Monolithic plans overflow context windows, causing agents to miss details and make mistakes on large tasks. They also prevent session isolation, since each execution session should load only the relevant phase rather than the entire plan.