skills.rest
aleister1102
aleister1102COMMUNITY
Explore all skills by this author →
GitHub

create-plan

Generate structured coding plans with discovery, changes, tests, and rollout.

Updated Aug 23, 2026
Search Tags:#workflow#planning#checklist#strategy#coding#plan#task-management
One-click install
npx skills add https://github.com/aleister1102/skills --skill create-plan-aleister1102
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/aleister1102/skills/tree/main/create-plan
Command: npx skills add https://github.com/aleister1102/skills --skill create-plan-aleister1102

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert a user prompt for a coding task into a compact, actionable plan that outlines discovery, changes, tests, and rollout.

Core Features & Use Cases

  • Generate a structured, stepwise plan that can be reviewed and approved
  • Align stakeholders and expectations with a clear checklist
  • Use for feature requests, bug fixes, or refactors in software projects

Quick Start

Provide a concise, stepwise plan for a given coding task when prompted.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I generate a structured coding plan from a prompt?▼

To generate a structured coding plan, input your feature request or bug fix prompt to receive a concise checklist covering discovery, changes, tests, and rollout. This actionable plan provides a stepwise workflow for software projects without manual formatting.

What is the best way to create a task checklist for a software refactor?▼

Creating a task checklist for a software refactor involves converting your prompt into a structured plan with discovery, changes, tests, and rollout phases. This checklist approach clarifies refactoring strategies and handles optional edge cases to align stakeholder expectations.

Can I use this for both bug fixes and new feature requests?▼

Yes, you can use this for both bug fixes and new feature requests across software projects. The generated plan applies to any coding task, satisfying requirements for a structured workflow that includes discovery, changes, tests, rollout, and optional edge-case handling.

How do I write an actionable plan that covers testing and rollout?▼

To write an actionable plan covering testing and rollout, transform your coding prompt into a stepwise checklist. The resulting plan explicitly separates code changes from tests and rollout strategies, ensuring all deployment requirements and optional edge cases are systematically addressed.

What should a coding plan include for handling edge cases?▼

A coding plan for handling edge cases should include a structured checklist with discovery, changes, tests, and rollout phases. Incorporating optional edge-case handling within the plan ensures the software strategy anticipates unexpected behaviors during refactoring or feature implementation.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

planning-requirements-extraction

Extract verifiable requirements and acceptance criteria from user requests.

Community
Basic
kkestellkkestell
1

kwork

Execute repository implementation plans with code changes, tests, and reviews.

Community
Advanced
lucasFR2lucasFR2

requesting-code-review

Automate code review by dispatching a subagent against defined requirements.

Community
Advanced
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate