skills.rest
yy1588133
yy1588133COMMUNITY
Explore all skills by this author →
GitHub

plan

Analyze codebases and produce RALPLAN-DR and ADR decision artifacts.

2|1|Updated Jul 9, 2026
Search Tags:#planning#codebase analysis#consensus#decision-making#execution gate
One-click install
npx skills add https://github.com/yy1588133/oh-my-snow --skill plan-yy1588133
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/yy1588133/oh-my-snow/tree/main/assets/skills/oms/plan
Command: npx skills add https://github.com/yy1588133/oh-my-snow --skill plan-yy1588133

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of jumping into code without a clear plan, leading to rework, scope creep, and missed edge cases. It provides structured requirements gathering, expert consensus validation, and quality-gated decision artifacts to ensure execution starts from a solid foundation.

Core Features & Use Cases

  • Strategic Planning: Analyzes the codebase and drives a Planner→Architect→Critic loop.
  • Decision Artifacts: Produces RALPLAN-DR + ADR decision artifacts mapped to PRD stories.
  • Execution Gate: Gates execution behind explicit user approval before any code is written.
  • Use Case: Before implementing a new feature, use this Skill to analyze the requirements, gather expert consensus, and create a detailed plan before writing any code.

Quick Start

To plan a new feature, run the command: /oms:plan

Frequently Asked Questions about plan

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

FAQPage Schema
How do I prevent scope creep when implementing new features in a codebase?▼

To prevent scope creep, use structured strategic planning to analyze the codebase and drive a consensus loop before execution. This approach gathers requirements, validates edge cases through expert feedback, and gates code writing behind explicit user approval.

What is the best way to gather consensus before starting software execution?▼

Gather consensus by using a structured planning workflow that drives a Planner, Architect, and Critic loop. This method analyzes your codebase, produces decision artifacts like RALPLAN-DR and ADR, and ensures all stakeholders approve the plan before execution begins.

How do I generate decision artifacts for AI-driven workflows?▼

You can generate decision artifacts by running a structured strategic planning command that analyzes your codebase and drives a consensus loop. This produces RALPLAN-DR and ADR artifacts mapped to PRD stories, providing a clear foundation for AI-driven execution.

When do I need an execution gate before writing code?▼

An execution gate is needed before writing code to prevent rework and missed edge cases in new features. It enforces explicit user approval after strategic planning and consensus validation, ensuring the codebase implementation starts from a solid, agreed-upon foundation.

Does strategic planning for codebase analysis require specific dependencies?▼

No specific external dependencies are required for strategic planning and codebase analysis. The workflow relies on internal consensus-building and decision-making capabilities to analyze requirements and produce decision artifacts without needing additional tools.

Related Skills

Explore More Software Engineering Skills→
DuongMQuangDuongMQuang
6

0-init

Automate project setup by generating CONTEXT.md and OPEN_QUESTIONS.md.

Community
Intermediate
MohammedSaudAlsahliMohammedSaudAlsahli

omc-plan

Create detailed work plans with consensus and review modes.

Community
Advanced
safzanpiranisafzanpirani
1

to-prd

Generate a Product Requirements Document from conversation context and publish it to an issue tracker.

Community
Advanced
kollaboraikollaborai
1

architecture-mapping

Reverse-engineer undocumented Python, JavaScript, and Java systems into architecture documentation.

Community
Advanced