create_plan

Generate phase-based implementation plans with milestones and success criteria.

2|Updated May 8, 2026

Search Tags:#automation #planning #codebase #requirements #implementation #phases #artifact

Ready to run

npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill create-plan-brightblock

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create_plan
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/create_plan
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill create-plan-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The create_plan skill helps teams build comprehensive, implementable plans for complex changes by guiding interactive research, capturing dependencies, and outlining step-by-step work with measurable criteria.

Core Features & Use Cases

Interactive research-driven plan creation that surfaces risks, milestones, and resource needs.
Phase-based plan generation with concrete changes, verification steps, and testing criteria.
Generates a structured artifact suitable for review, sharing, and storage.

Quick Start

Start a new plan by providing task context or a ticket reference; the assistant will read related files, perform parallel research, and present a draft outline for review.

Frequently Asked Questions about create_plan

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

FAQPage Schema

How do I create an implementation plan for a complex codebase change?▼

To create an implementation plan, provide task context or a ticket reference to initiate interactive research that reads related files and generates a structured, phase-based artifact with explicit milestones and success criteria.

What is phase-based planning for cross-team architecture changes?▼

Phase-based planning breaks down non-trivial codebase changes into sequential execution steps with concrete modifications, testing criteria, and measurable milestones to guide cross-team design and architecture implementation.

Can I generate a structured plan artifact from a single ticket reference?▼

Yes, you can generate a structured plan artifact from a ticket reference by using it as input context to trigger parallel research, dependency capture, and draft outline generation suitable for review and storage.

Does interactive research-driven planning work for non-trivial software engineering tasks?▼

Interactive research-driven planning is designed specifically for non-trivial software engineering tasks, applying structured workflows to surface risks, resource needs, and measurable criteria for complex codebase modifications.

What is the best way to document phased execution milestones for architecture changes?▼

The best way to document phased execution milestones is to generate a structured artifact that captures concrete changes, verification steps, and both automated and manual success criteria for each implementation phase.

What are the limitations of automated planning for cross-team design tasks?▼

Automated planning for cross-team design requires manual review of the draft outline and success criteria, as the generated artifact surfaces risks and dependencies but cannot validate domain-specific architectural decisions without human input.