plan-generator

Generate structured implementation plans for vertical slices with validation gates.

2|Updated Jun 3, 2021

Search Tags:#automation #planning #architecture #documentation #validation #plan #software

Ready to run

npx skills add https://github.com/kalindudc/shell --skill plan-generator-kalindudc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-generator
Source: https://github.com/kalindudc/shell/tree/main/home/.config/opencode/skills/plan-generator
Command: npx skills add https://github.com/kalindudc/shell --skill plan-generator-kalindudc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates structured implementation plans for vertical slices of working software, embedding research, codebase context, and a stable plan you can execute.

Core Features & Use Cases

Context-rich planning: Plans include precise file paths, library versions, and relevant code snippets to guide implementation.
Implementation Strategy: Specifies libraries, patterns, repo conventions, and architectural decisions tailored to the target feature.
Validation Gates: Defines deterministic checks (build, test, lint) with clear acceptance criteria for quality control.
Use Case: When planning a new feature, produce a plan that outlines the end-to-end steps, starting context, and expected deliverables.

Quick Start

Request a plan that delivers a vertical slice of working software with embedded context, implementation strategy, and validation gates.

Frequently Asked Questions about plan-generator

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

FAQPage Schema

How do I generate a software implementation plan with validation gates?▼

Software implementation plans with validation gates are generated by structuring vertical slices of working software, embedding codebase context, and defining deterministic build, test, and lint checks for predictable outcomes.

What is a vertical slice plan for software development?▼

A vertical slice plan structures software development by outlining end-to-end steps, starting context, and expected deliverables, ensuring each slice produces working software with embedded research and architectural decisions.

How do I create an implementation strategy that includes specific file paths and library versions?▼

Implementation strategies are created by specifying precise file paths, library versions, relevant code snippets, and repo conventions tailored to the target feature, ensuring context-rich planning and maintainability.

Can I use automated planning for software features requiring thorough codebase context?▼

Automated planning fits software projects needing thorough research and codebase context, producing structured plans with beginning and ending context, low-level tasks for file creation or updates, and explicit validation gates.

What's the best way to ensure software plans have deterministic checks across build, test, and integration stages?▼

Deterministic checks across build, test, and integration stages are ensured by defining explicit validation gates with clear acceptance criteria, enforcing a plan format that guarantees maintainable and predictable outcomes.

Does structured planning work for features needing architectural decisions and repo convention adherence?▼

Structured planning works for features needing architectural decisions by specifying libraries, patterns, and repo conventions tailored to the target feature, embedding implementation strategy within the generated plan.