plan

Analyze project requirements, assess feasibility, define API contracts, and save plans as JSON.

1.2k|140|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/first-fluke/oh-my-agent --skill plan-first-fluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/first-fluke/oh-my-agent/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/first-fluke/oh-my-agent --skill plan-first-fluke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of analyzing requirements, breaking them down into actionable tasks, and defining API contracts, streamlining project planning.

Core Features & Use Cases

  • Requirement Analysis: Gathers and analyzes user requirements, target users, features, constraints, and deployment targets.
  • Technical Feasibility: Assesses technical feasibility by analyzing the codebase.
  • API Contract Definition: Defines API contracts and stores them in a structured format.
  • Task Decomposition: Breaks down work into agents, titles, acceptance criteria, priorities, and dependencies.
  • User Review & Plan Saving: Ensures user approval before saving the plan to .agents/plan.json and optionally to docs/exec-plans/active/.

Quick Start

Use the plan skill to analyze the requirements for a new user authentication feature and generate a detailed project plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose project requirements into actionable tasks with dependencies?

Requirement decomposition breaks down work into agents, titles, acceptance criteria, priorities, and dependencies. It analyzes constraints, assesses codebase feasibility, and saves the structured plan in JSON format for workflow execution.

What is the best way to define API contracts during project planning?

API contract definition structures interface specifications during project planning. It assesses technical feasibility by analyzing the codebase, defines contracts, and stores them in a structured format before saving the overall plan to a JSON file.

How do I assess technical feasibility before starting workflow automation?

Technical feasibility assessment uses code analysis tools to evaluate the codebase before workflow automation. It analyzes project requirements, deployment targets, and constraints to ensure the proposed tasks and API contracts are viable.

Can I save a generated project plan to a custom directory?

Project plans are saved to the `.agents/plan.json` directory by default, with an optional path to `docs/exec-plans/active/`. The skill facilitates user review and ensures approval before saving the task decomposition data.

Does task decomposition support priority assignment for workflow execution?

Task decomposition supports workflow execution by assigning priorities and mapping dependencies. It breaks down project requirements into actionable items with acceptance criteria, enabling structured and sequential development.

Why do I need to review a generated plan before it is saved?

Reviewing a generated plan ensures user approval before saving the JSON file for workflow execution. This validation step prevents incorrect task decomposition or API contract definitions from entering the active project pipeline.