make

Generate structured implementation plans with task breakdowns and custom rules.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/mkoziy/skills --skill make-mkoziy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make
Source: https://github.com/mkoziy/skills/tree/main/.claude/skills/planning/make
Command: npx skills add https://github.com/mkoziy/skills --skill make-mkoziy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires revdiff, and includes scripts (resource) components.

What problem does it solve?

The skill streamlines the creation of detailed implementation plans by guiding you through intent parsing, rule-loading, and task decomposition to produce a ready-to-run docs/plans entry.

Core Features & Use Cases

  • Guided plan generation: prompts you to define scope, requirements, and milestones, producing a structured plan file.
  • Rule-aware planning: incorporates project-level and local planning rules to tailor the plan.
  • Reusable templates: outputs consistent plan templates that can be reused across tasks and teams.

Quick Start

Create a new plan by following the guided prompts to generate a dated plan file in docs/plans/.

Frequently Asked Questions about make

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

FAQPage Schema
How do I generate structured implementation plans for software projects?

Structured implementation plans are generated through guided prompts that parse project intent, load custom rules, and decompose tasks into a dated file under docs/plans/. This process ensures consistent plan generation across engineering teams.

What is rule-aware planning and how does it tailor task breakdowns?

Rule-aware planning incorporates project-level and local planning rules to customize task breakdowns and milestones. By loading these specific constraints during intent parsing, the generated plan templates align with established engineering workflows.

How do I create reusable plan templates for product planning workflows?

Reusable plan templates are created by defining your scope, requirements, and milestones through guided prompts. The skill outputs a consistent template file in the docs/plans/ directory that can be applied to future tasks and teams.

Can I automate task decomposition and milestone tracking for engineering workflows?

Task decomposition and milestone tracking are automated by guiding you through intent parsing and rule-loading to produce structured plan documents. This satisfies requirements for breaking down complex product planning into ready-to-run plan entries.

Does this approach work without manually formatting documentation for every new plan?

It eliminates manual documentation formatting by automatically generating dated plan files in the docs/plans/ directory. The skill applies reusable templates and custom rules to ensure every plan document is consistently structured.

What are the limitations of automating plan generation for product planning?

Plan generation automation depends on clearly defined scope and requirements provided during the guided prompts, meaning vaguely specified project intent will produce generic task breakdowns. It also relies on properly configured local planning rules to tailor the output effectively.