plan

Generate a layer-ordered implementation plan from a GitHub issue.

262|51|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/divinevideo/divine-mobile --skill plan-divinevideo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/divinevideo/divine-mobile/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/divinevideo/divine-mobile --skill plan-divinevideo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically translates a GitHub issue into a structured, actionable implementation plan that covers the UI, BLoC, repository, and client layers, including the required files, tests, and risk assessment.

Core Features & Use Cases

  • Fetch issue context from GitHub and determine issue type.
  • Analyze the codebase to map impact across UI, BLoC, Repository, and Client layers.
  • Produce a bottom-up plan detailing files to modify, steps, testing strategy, and risk assessment.
  • Works for bugs, features, and tasks to standardize planning workflows.

Quick Start

Invoke /plan with a GitHub issue number or URL to generate a structured implementation plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate an implementation plan from a GitHub issue?

You can generate an implementation plan from a GitHub issue by providing the issue URL or number. The tool extracts context via gh and outputs a bottom-up plan covering UI, BLoC, repository, and client layers.

What is a bottom-up implementation plan for software features?

A bottom-up implementation plan details files to modify, step-by-step actions, testing strategy, and risk assessment. It maps issue scope across architectural layers like UI, BLoC, repository, and client.

Can I use this to plan bug fixes and feature tasks across my codebase?

Yes, you can use this to plan bug fixes, features, and tasks across your codebase. It standardizes workflows by analyzing codebase impact and delivering concrete, layer-ordered implementation steps.

Does the generated plan include a testing strategy and risk assessment?

Yes, the generated plan includes a testing strategy and risk assessment. It produces concrete actions detailing files to modify, testing approaches, and risk mitigation for the identified issue.

What is the best way to standardize planning workflows for GitHub repository issues?

Standardize planning workflows for GitHub issues by translating them into structured, actionable plans. This ensures consistent coverage of UI, BLoC, repository, and client layers, including tests and risk assessment.