specialist-planner

Draft implementation plans with phases, dependencies, risks, and testing strategy.

42|1|Updated Mar 24, 2026

Search Tags:#planning #documentation #architecture-review #risk-analysis #implementation-plan #requirements-analysis

Ready to run

npx skills add https://github.com/VenTheZone/pi-dots --skill specialist-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specialist-planner
Source: https://github.com/VenTheZone/pi-dots/tree/main/pi-dotfiles-specialist-skills/skills/specialist-planner
Command: npx skills add https://github.com/VenTheZone/pi-dots --skill specialist-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This planning specialist guide helps teams convert vague feature requests into comprehensive, actionable implementation plans with clear steps, dependencies, and risk considerations to guide delivery.

Core Features & Use Cases

Structured Implementation Plan formats that organize requirements, architecture changes, and success criteria.
Phase-by-phase breakdowns optimizing task ordering, dependencies, and incremental delivery.
Architecture and risk awareness: identifies affected components, constraints, and potential failure modes.
Best practices and planning guardrails to improve estimation, testing strategy, and documentation.
Use Case: for a feature request, generate a plan that includes milestones, required artifacts, and testing plans.

Quick Start

Provide an end-to-end implementation plan for the requested feature using the Plan Format, including milestones, risks, and testing strategy.

Frequently Asked Questions about specialist-planner

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

FAQPage Schema

How do I turn feature requirements into a phased implementation plan?▼

Implementation planning converts high-level feature requests into structured phases with dependency mapping, incremental delivery steps, and clear milestones. This process organizes architecture changes and success criteria into a comprehensive, actionable format for product teams.

What is the best way to document architecture decisions and risk analysis for a software refactor?▼

Architecture decision documentation identifies affected components, constraints, and potential failure modes during software refactoring. It provides structured risk analysis and best-practice guardrails to improve estimation, testing strategy, and technical documentation.

How do I create an end-to-end implementation plan that includes milestones and a testing strategy?▼

End-to-end implementation plans phase task ordering by mapping dependencies and defining incremental delivery milestones. They integrate a dedicated testing strategy and required artifacts to guide software feature development from requirements to final delivery.

Can I use structured planning for vague feature requests before development starts?▼

Structured planning transforms vague feature requests into comprehensive, actionable implementation plans before development. It applies phase-based breakdowns and planning guardrails to clarify requirements, constraints, and success criteria for product teams.

What should be included in an implementation plan format for product development teams?▼

An implementation plan format should include phase-based implementation steps, dependency mapping, risk analysis, testing strategy, and best-practice guidance. It organizes requirements, architecture changes, and success criteria to guide incremental delivery.

When do I need a detailed implementation plan with dependency mapping and risk considerations?▼

You need a detailed implementation plan when converting high-level requirements into actionable phases for software development or refactoring. It ensures dependency mapping and risk considerations are addressed to optimize task ordering and guide delivery.