planner

Create phase-based plans with JSON templates for software and product work.

1|Updated Feb 13, 2026

Search Tags:#planning #investigation #migration #refactor #feature #workflows

Ready to run

npx skills add https://github.com/aronpc/ai --skill planner-aronpc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/aronpc/ai/tree/main/skills/planner
Command: npx skills add https://github.com/aronpc/ai --skill planner-aronpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex implementation work with clear workflows to coordinate features, refactors, investigations, and migrations across teams.

Core Features & Use Cases

Structured workflows including feature, refactor, investigation, migration, and simple tasks to standardize planning
Pre-defined phases and subtasks templates to speed up planning and reduce ambiguity
JSON-based plan structure (spec_id, workflow_type, phases, verification, and context) to enable repeatable planning across projects

Quick Start

Create a new plan by selecting a workflow type and filling in phases and subtasks

Frequently Asked Questions about planner

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

FAQPage Schema

How do I create structured workflows for software migration and refactoring plans?▼

Structured workflows for migration and refactor planning use predefined phases and subtask templates to standardize complex implementation work. You select a workflow type, fill in phases, and generate a JSON-based plan to coordinate tasks across teams.

What is a JSON-based plan structure for feature planning?▼

A JSON-based plan structure for feature planning uses a metadata format containing spec_id, workflow_type, phases, verification, and context. It enables repeatable planning across projects by tracking subtask IDs, dependencies, and risks.

Can I use predefined workflow templates for investigation tasks across teams?▼

Yes, you can use predefined workflow templates for investigation tasks across teams. The system supports standardized workflow types including feature, refactor, investigation, migration, and simple tasks to reduce planning ambiguity.

How do I track dependencies and risks in a phase-based product plan?▼

You track dependencies and risks in a phase-based product plan by utilizing the metadata section of the JSON plan structure. This section captures subtask IDs, dependency mappings, and risk indicators for cross-team coordination.

What's the best way to standardize planning for complex software implementation work?▼

The best way to standardize planning for complex software implementation work is applying repeatable, workflow-driven plans. Using predefined phases and subtask templates reduces ambiguity and creates actionable plans for features, refactors, investigations, and migrations.

Does this planning approach support simple tasks or only complex migrations?▼

This planning approach supports both simple tasks and complex migrations. It includes predefined workflow types for feature, refactor, investigation, migration, and simple tasks to standardize planning across varying levels of implementation complexity.