ralplan

Design and validate software implementation plans with explicit approval workflows.

6|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Goblin1024/oh-my-kimi --skill ralplan-goblin1024
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralplan
Source: https://github.com/Goblin1024/oh-my-kimi/tree/main/skills/ralplan
Command: npx skills add https://github.com/Goblin1024/oh-my-kimi --skill ralplan-goblin1024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and gating of architecture decisions before implementation to align teams and reduce rework.

Core Features & Use Cases

  • Context review and requirement capture from existing docs
  • Architecture design with trade-off analysis and component interfaces
  • PRD generation and formal approval workflow with traceable evidence
  • State management across planning -> approved -> execution

Quick Start

Trigger a plan by using $ralplan <task description> and review the generated PRD for approval.

Frequently Asked Questions about ralplan

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

FAQPage Schema
How do I plan software architecture before coding to reduce team rework?

To plan software architecture before coding, review existing context and requirements, design components with trade-off analysis, and generate a PRD for formal approval. This enforces explicit gating and aligns stakeholders before implementation begins.

How do I generate a PRD with traceable evidence for stakeholder approval?

Generate a PRD with traceable evidence by capturing context from existing docs, documenting architecture alternatives, and submitting the design through an explicit approval workflow. This ensures stakeholders have full visibility before execution.

What is architecture trade-off analysis and when do I need it for feature planning?

Architecture trade-off analysis evaluates competing design alternatives and component interfaces for software features. You need it during feature planning to document alternatives, align teams, and secure explicit approvals before implementation.

How do I manage state transitions from planning to execution after architecture approval?

Manage state transitions from planning to execution by enforcing a formal approval workflow that moves projects from planning to approved states. This gating mechanism ensures no implementation begins without explicit stakeholder sign-off.

Can I use context-aware PRDs for complex software development projects?

Yes, you can use context-aware PRDs for complex software development by capturing requirements from existing docs and generating architecture plans. This validates end-to-end implementation designs before any coding occurs.