planning

Create phased implementation plans with YAML frontmatter and success criteria.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lukebaze/forex-rebate-bot --skill planning-lukebaze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/lukebaze/forex-rebate-bot/tree/main/.opencode/skill/planning
Command: npx skills add https://github.com/lukebaze/forex-rebate-bot --skill planning-lukebaze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan implementations, design architectures, and technical roadmaps with clear phase-based guidance to transform rough requirements into actionable plans.

Core Features & Use Cases

  • Technical planning capabilities to create phased plans, architectures, and implementation strategies with rationale.
  • Synthesis of research, codebase understanding, and design guidelines into a structured plan document.
  • Plan documentation and governance, including phase breakdowns, milestones, and success criteria.

Quick Start

Provide project context, goals, and constraints, and I will generate a comprehensive, phased plan in the plans/ directory.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a phased implementation plan from rough requirements?

To create a phased implementation plan, you provide project context, goals, and constraints. The system then synthesizes research and codebase understanding into a structured plan document with phase-level tasks, milestones, and clear success criteria.

What is the best way to structure technical roadmap documentation?

Technical roadmap documentation is structured using YAML frontmatter, phase-level tasks, and clear success criteria. This governance approach transforms architectural decisions and implementation strategies into actionable, phased activities.

How do I plan architectural decisions during product discovery?

Planning architectural decisions during product discovery involves applying structured reviews to synthesize design guidelines. This process breaks technical implementations into phased activities with documented rationale and milestones.

Can I use this for phase management and roadmap creation at the same time?

Yes, you can use this for phase management and roadmap creation simultaneously. It structures work into phased activities while ensuring plan documentation includes milestones and success criteria for both processes.

What format does the generated plan documentation use?

Generated plan documentation uses a structured format with YAML frontmatter. It synthesizes research and codebase understanding directly into the plans directory, ensuring phase breakdowns and success criteria are clearly documented.

When do I need structured governance for implementation planning?

You need structured governance for implementation planning when transforming rough requirements into actionable plans. Governance ensures documentation includes phase breakdowns, milestones, and clear success criteria for technical architectures.