skills.rest
wangrenzhu-ola
wangrenzhu-olaCOMMUNITY
Explore all skills by this author →
GitHub

gh:plan

Create structured implementation plans with scope, risks, dependencies, and test guidance.

2|1|Updated Apr 17, 2026
Search Tags:#workflow#planning#requirements#execution#docs#plan#software
Ready to run
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-plan
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: gh:plan
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-plan
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

gh:plan creates a durable, implementation-focused plan from a brainstorm or a requirements document, guiding multi-step software work without writing code.

Core Features & Use Cases

  • Define scope, decisions, dependencies, and risk for complex software tasks.
  • Break work into implementable units with clear ownership and test guidance.
  • Deepen existing plans with a structured, evidence-based review flow and origin decisions anchoring.

Quick Start

Describe your task or choose a requirements document, then run gh:plan to generate a structured plan.

Frequently Asked Questions about gh:plan

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

FAQPage Schema
How do I create a structured plan for a multi-step software project?▼

To create a structured plan for a multi-step software project, you can define scope, decisions, dependencies, and risks from origin requirements to output concrete plan artifacts and verification guidance without writing code.

What is the best way to break down software requirements into implementable units?▼

The best way to break down software requirements into implementable units is to execute a structured planning workflow that transforms requirements documents into discrete tasks with clear ownership and test guidance.

Can I deepen an existing software project plan without starting over?▼

Yes, you can deepen an existing software project plan without starting over by applying a structured, evidence-based review flow that anchors origin decisions and expands implementation details upon request.

Do I need a requirements document to generate software implementation plans?▼

You do not strictly need a formal requirements document to generate software implementation plans; you can operate directly from brainstorm results to define scope, risks, dependencies, and implementation units.

Does structured planning for software projects write the actual code?▼

Structured planning for software projects does not write the actual code; it outputs concrete plan artifacts and verification guidance to guide implementation, focusing on defining scope and decisions.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
jaydubya818jaydubya818

ce:work-beta

Execute work plan documents end-to-end with task generation and quality gates.

Community
Advanced
haposofthaposoft
54

hapo:brainstorm

Transforms raw ideas into validated, spec-ready designs for software architecture.

Official
Advanced
cloudaura-iocloudaura-io
8

conductor:new-track

Generates formal spec & business plan for software projects.

Official
Advanced