skills.rest
galz10
galz10COMMUNITY
Explore all skills by this author →
GitHub

implementation-planner

{ { { { { { { { { { { { { { { { { {

454|45|Updated Jan 9, 2026
Search Tags:#planning#implementation#roadmap#software-engineering#requirements-analysis#ticket-management
One-click install
npx skills add https://github.com/galz10/pickle-rick-extension --skill implementation-planner-galz10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-planner
Source: https://github.com/galz10/pickle-rick-extension/tree/main/skills/implementation-planner
Command: npx skills add https://github.com/galz10/pickle-rick-extension --skill implementation-planner-galz10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams translate vague requirements into precise, step-by-step implementation plans, reducing ambiguity and accelerating delivery.

Core Features & Use Cases

  • Iterative planning: Generate atomic plan phases (Context, Plan, Implementation, Review) tailored to a ticket.
  • Structured templates: Provide a reusable plan skeleton with clear milestones and success criteria.
  • Interactive refinement: Update the plan through an iterative dialogue, saving progress to the session ticket.

Quick Start

Use the implementation-planner skill to draft an initial plan for a given ticket. The tool will guide you to gather context, define phases, and produce a structured plan ready for review.

Frequently Asked Questions about implementation-planner

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

FAQPage Schema
What is the best way to turn vague software requirements into an actionable roadmap?▼

Implementation planning translates vague software requirements into precise, actionable roadmaps by breaking down tickets into atomic phases with clear milestones and success criteria. This structured approach reduces ambiguity and accelerates software delivery.

How do I structure an implementation plan for a software engineering ticket?▼

You structure an implementation plan by guiding the tool through four atomic phases: Context, Plan, Implementation, and Review. This iterative process generates a reusable plan skeleton with clear milestones tailored to your specific ticket.

Can I refine a project plan iteratively and save progress for my engineering team?▼

Yes, you can refine a project plan iteratively through interactive dialogue. The planning tool supports iterative refinement and saves your updated progress directly to the session ticket for your engineering team to review.

Does structured implementation planning work for complex software projects with unclear scope?▼

Structured implementation planning is designed for complex software projects with unclear scope. It enforces a structured planning approach that translates ambiguous requirements into concrete, step-by-step phases suitable for engineering teams.

What are the limitations of using atomic plan phases for requirements analysis?▼

Using atomic plan phases for requirements analysis requires a structured planning approach and may not suit highly dynamic environments where immediate, unstructured execution is prioritized over generating detailed milestones and success criteria.

Related Skills

Explore More Software Engineering Skills→
adobecomadobecom
1

start-ticket

Gather Jira context and analyze codebase structures for ticket work.

Official
Advanced
gihwan-devgihwan-dev
1

milestone

Parse SPEC.md and plan.md to generate phased milestones with completion criteria.

Community
Intermediate
mthinesmthines
7

batch-linear-tickets

Automate investigation, correlation, planning, approval, and execution of multiple Linear tickets.

Community
Advanced
batFormatbatFormat

aif-roadmap

Generate and manage project roadmaps with milestone progress tracking.

Community
Intermediate