skills.rest
HexAI-inc
HexAI-incOFFICIAL
Explore all skills by this author →
GitHub

planning-mastery

Generate RFC-Lite implementation plans with file changes, logic strategy, and verification.

Updated Oct 30, 2025
Search Tags:#planning#architecture#documentation#dependency management#implementation plan#rfc-lite
One-click install
npx skills add https://github.com/HexAI-inc/v0-futuristic-website-design --skill planning-mastery-hexai-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-mastery
Source: https://github.com/HexAI-inc/v0-futuristic-website-design/tree/main/.agents/skills/maestro/skills/planning-mastery
Command: npx skills add https://github.com/HexAI-inc/v0-futuristic-website-design --skill planning-mastery-hexai-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create concise, architectural implementation plans using a strict RFC-Lite format, ensuring clarity and preventing overly verbose or code-heavy documentation.

Core Features & Use Cases

  • RFC-Lite Planning: Generates implementation plans adhering to a specific, minimalist format.
  • Dependency Forecasting: Mandates the identification of downstream effects and potential breaking changes.
  • Strict Verbosity Control: Enforces a strict line limit and prohibits pseudo-code or full file content.
  • Use Case: When proposing a new feature, use this Skill to generate a plan that clearly outlines the objective, technical strategy, file changes, execution sequence, and verification standards, all within a strict line limit.

Quick Start

Use the planning-mastery skill to create an RFC-Lite plan for implementing a user authentication module.

Frequently Asked Questions about planning-mastery

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

FAQPage Schema
What is an RFC-Lite format for software architecture planning?▼

RFC-Lite format is a minimalist architectural planning approach that strictly limits verbosity, focusing on WHAT files change, HOW logic strategy works, and SUCCESS verification to prevent overly verbose documentation.

How do I write a concise implementation plan without including pseudo-code?▼

Generate implementation plans using strict verbosity control that enforces a 300-line limit and prohibits pseudo-code or full file content, ensuring concise architectural documentation.

How do I identify downstream effects and dependency forecasting for a new feature?▼

Implementation plans mandate identification of downstream effects and dependency forecasting to prevent coupled module failures, ensuring breaking changes are recognized before execution.

Does this planning approach work for documenting complex module changes?▼

Yes, architectural implementation plans enforce dependency forecasting and mandate identification of downstream effects specifically to prevent coupled module failures in complex software engineering changes.

What are the limitations of using strict line limits for architectural documentation?▼

Plans adhere to a strict 300-line limit and prohibit pseudo-code or full file content, which means detailed code implementation must be handled separately outside the architectural documentation.

Related Skills

Explore More Software Engineering Skills→
The-RabakThe-Rabak

workflows-plan

Transform feature descriptions into structured project plans with acceptance criteria.

Community
Advanced
tizeetizee
3

script-bugfix

Isolate side effects and extract core logic to debug scripts.

Community
Advanced
meta-pytorchmeta-pytorch
2.5k

rfc-check

Determine if proposed changes require an RFC by applying criteria and checking conflicts.

Official
Intermediate
felix-howardfelix-howard

ck:plan

Generate technical implementation plans with phased documentation and architecture design.

Community
Advanced