create_plan

Generate detailed iterative implementation plans from codebase research and user requirements.

4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/visualitypl/visuality-humanlayer --skill create-plan-visualitypl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create_plan
Source: https://github.com/visualitypl/visuality-humanlayer/tree/main/.github/skills/create_plan
Command: npx skills add https://github.com/visualitypl/visuality-humanlayer --skill create-plan-visualitypl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive, actionable implementation plans by guiding users through research, design options, and detailed documentation.

Core Features & Use Cases

  • Interactive Planning: Collaboratively develop detailed technical specifications.
  • Codebase Research: Leverages agents to analyze existing code and gather context.
  • Structured Output: Generates plans in a standardized Markdown format with clear phases and verification steps.
  • Use Case: When starting a new feature, use this Skill to generate a plan that outlines the necessary code changes, testing procedures, and potential risks, ensuring alignment before development begins.

Quick Start

Use the create plan skill to start planning a new feature based on the ticket in thoughts/allison/tickets/eng_1234.md.

Frequently Asked Questions about create_plan

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

FAQPage Schema
How do I create a detailed implementation plan for a new software feature?

You can build a detailed implementation plan by providing feature requirements and ticket context, which the Skill analyzes against your codebase to produce structured Markdown documentation with development phases and verification criteria.

What is codebase research and how does it improve technical planning?

Codebase research uses agents to analyze existing code and gather context, ensuring your implementation plans account for current architecture and necessary code changes before development begins.

Can I generate technical specifications that include testing procedures and risk assessment?

Yes, you can generate technical specifications that outline necessary code changes, testing procedures, automated and manual verification criteria, and potential risks to ensure alignment before development.

Does this implementation planning tool work with existing documentation and tickets?

Yes, it works with existing documentation by reading ticket files like markdown documents, using that input to collaboratively develop structured technical specifications tailored to your software engineering workflow.

What is the best way to structure a software development plan for iterative feature execution?

The best way to structure iterative plans is using standardized Markdown output with clear phases, design options, and automated verification steps, ensuring actionable task execution throughout the development workflow.