planner

Generate Markdown implementation plans for software features without modifying the codebase.

Updated May 6, 2026

Search Tags:#design #planning #architecture #scoping #documentation #refactoring

Ready to run

npx skills add https://github.com/lucidfrontier45/my-opencode-settings --skill planner-lucidfrontier45

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/lucidfrontier45/my-opencode-settings/tree/main/skills/planner
Command: npx skills add https://github.com/lucidfrontier45/my-opencode-settings --skill planner-lucidfrontier45

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of disorganized or poorly scoped development by forcing a structured, thoughtful planning phase before any code is written, preventing scope creep and architectural debt.

Core Features & Use Cases

Structured Planning: Generates comprehensive implementation plans in Markdown format within a dedicated .plan/ directory.
Iterative Clarification: Guides the user through a structured discovery process to define scope, constraints, and trade-offs before committing to an approach.
Use Case: When tasked with a complex refactor or a new feature, the skill explores the existing codebase, outlines the design, and produces a detailed roadmap including risks, alternatives, and acceptance criteria.

Quick Start

Ask the planner to design a system for a new user authentication module by analyzing the current project structure.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I create an implementation plan for a complex software feature without writing code yet?▼

To create an implementation plan without writing code, use a structured planning phase that explores the codebase, clarifies scope iteratively, and documents design decisions in Markdown. This prevents scope creep and architectural debt before development begins.

What is the best way to scope a system design and refactoring task in an existing repository?▼

Scoping a system design and refactoring task involves a multi-phase workflow of codebase exploration and iterative clarification. This structured discovery process defines constraints and trade-offs, producing a detailed roadmap with risks, alternatives, and acceptance criteria.

Does this planning workflow generate documentation for architectural changes directly in the project?▼

Yes, this planning workflow generates documentation for architectural changes directly in the project. It creates comprehensive implementation plans in Markdown format within a dedicated .plan/ directory to ensure design decisions are structured and accessible.

Can I use this approach to outline a new user authentication module by analyzing current project structure?▼

Yes, you can use this approach to outline a new user authentication module. The skill explores the existing project structure, outlines the system design, and produces a detailed roadmap including risks, alternatives, and acceptance criteria for the new module.

When do I need a dedicated planning phase for software architecture and feature development?▼

You need a dedicated planning phase for software architecture and feature development when facing complex refactoring or new feature scoping. It forces a thoughtful design process before coding, preventing disorganized development and architectural debt.

What are the limitations of using a systematic planning skill for codebase refactoring?▼

A key limitation of this systematic planning skill is that it generates documentation and design roadmaps without modifying the codebase. It focuses entirely on scoping and architectural design, so it does not execute the actual refactoring or code changes.