planning

Create technical implementation plans and architecture designs with risk considerations.

105|12|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill planning-tmcfarlane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/planning
Command: npx skills add https://github.com/tmcfarlane/oh-my-cursor --skill planning-tmcfarlane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical implementation planning and architecture design to produce clear, maintainable roadmaps and design documents for complex projects.

Core Features & Use Cases

  • Plan and architect technical solutions
  • Break down requirements, evaluate trade-offs, and create implementation roadmaps
  • Documentation of decisions and rationale for long-term maintainability

Quick Start

Create a comprehensive plan for a new feature by outlining goals, constraints, architecture, timelines, and success criteria.

Frequently Asked Questions about planning

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

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

Create a technical implementation plan by outlining goals, constraints, architecture, timelines, and success criteria. This breaks down requirements, evaluates trade-offs, and produces a traceable roadmap for new features.

What is the best way to document architecture decisions for long-term maintainability?

Document architecture decisions by capturing the rationale, evaluated trade-offs, and risk considerations. This approach ensures long-term maintainability and provides traceable outputs for system redesigns.

How do I evaluate trade-offs when planning a system redesign?

Evaluate trade-offs during a system redesign by assessing technical approaches against constraints and risk considerations. The planning process structures this evaluation to produce clear architecture designs and roadmaps.

Can I use this for generating technical roadmaps from raw requirements?

Yes, you can generate technical roadmaps from raw requirements. The skill breaks down requirements, applies plan definitions, and outputs a structured implementation roadmap with clear milestones.

When do I need a formal architecture design document for a project?

You need a formal architecture design document when planning complex projects, new features, or system redesigns. It provides the plan definitions and traceable outputs required for clear, maintainable technical solutions.

What should be included in an implementation roadmap to ensure traceable outputs?

An implementation roadmap should include plan definitions, evaluated approaches, risk considerations, and documented decisions. These elements ensure the outputs are traceable and maintainable throughout the project lifecycle.