plan

Derive an executable implementation plan from exploration context and save it.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/tim-hub/powerball --skill plan-tim-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/tim-hub/powerball/tree/main/pbl/skills/plan
Command: npx skills add https://github.com/tim-hub/powerball --skill plan-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts exploratory research into a concrete, executable implementation plan, ensuring goals, decisions, risks, and open questions are captured and shareable.

Core Features & Use Cases

  • Derives goals, architectural decisions, risks, and open questions from an exploration context.
  • Generates a plan.md using a standardized template and fills in key metadata like NAME and DATE.
  • Coordinates generation of supporting artifacts (tasks.md and checklist.md) via parallel agents for implementation follow-through.
  • Saves artifacts under .powerball/specs/YYYY-MM-DD-{{name}}/ and enables traceability across planning work.

Quick Start

Provide your exploration context and run the plan workflow to generate and save a complete implementation plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert exploration research into an executable implementation plan?

Derive an executable implementation plan from exploration context by defining goals, architectural decisions, risks, and open questions. The plan is presented for confirmation and then saved into a versioned specs directory to ensure traceability.

How do I generate tasks and checklists that verify feature completion?

Generate tasks.md and checklist.md by coordinating separate writing skills as parallel agents. These artifacts verify feature completion and are saved alongside the plan in a versioned specs directory.

What is the best way to document architectural decisions and risks during feature planning?

Document architectural decisions and risks during feature planning by extracting them from an exploration context into a standardized plan.md template. This captures goals and open questions for shareable implementation tracking.

Do I need an exploration context to start the feature planning workflow?

Yes, an exploration context is required. The planning workflow derives goals, architectural decisions, risks, and open questions directly from that context to generate a concrete implementation plan.

How are planning artifacts structured and saved for version control?

Planning artifacts are structured and saved under a versioned specs directory using a YYYY-MM-DD-{{name}} format. This ensures traceability across planning work and persists the plan alongside generated tasks and checklists.