rb-create-implementation-plan

Generate structured implementation plans with phases, risks, and testing architectures.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-create-implementation-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-create-implementation-plan
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-create-implementation-plan
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-create-implementation-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill addresses the ambiguity of turning high-level product goals into actionable, verifiable implementation plans, preventing scope creep and ensuring testing requirements are defined early.

Core Features & Use Cases

  • Structured Planning: Generates comprehensive plans covering phases, risks, success criteria, and testing architecture.
  • Execution Routing: Provides clear choices between standard, constrained static-only, or undecided execution paths.
  • Use Case: Use this when you have a well-understood feature idea and need to define the technical approach, testing strategy, and safety boundaries before writing any code.

Quick Start

Invoke the skill by typing rb-create-implementation-plan to begin drafting a new project plan based on your current repository context.

Frequently Asked Questions about rb-create-implementation-plan

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

FAQPage Schema
How do I turn a feature idea into a structured implementation plan with testing requirements?

To turn a feature idea into a structured implementation plan, this skill generates phases, risk assessments, and testing architectures, ensuring testing requirements and success criteria are defined early to prevent scope creep.

What is the best way to align project planning with existing CI/CD and architectural standards?

Aligning project planning with existing CI/CD standards requires integrating the plan generation with your repository context, ensuring the technical specifications match your current testing and architectural boundaries.

How do I define execution routes and safety boundaries before writing code for a new feature?

Defining execution routes and safety boundaries is handled by providing clear choices between standard, constrained static-only, or undecided execution paths, establishing technical safety parameters before code implementation.

Do I need a fully understood feature idea before generating an actionable technical specification?

Yes, you need a well-understood feature idea to generate an actionable technical specification, as this skill facilitates the transition from conceptual goals to verifiable implementation plans rather than ideating concepts.

Can I use this planning approach for static-only or constrained software development workflows?

Yes, this planning approach supports static-only or constrained workflows by offering specific execution routing choices that tailor the implementation strategy and testing architecture to constrained environments.