skills.rest
ianphil
ianphilCOMMUNITY
Explore all skills by this author →
Website𝕏@giantcomputercoGitHub

work-plan

Generate a structured feature work plan from tasks.md and spec.md.

Updated Jan 27, 2026
Search Tags:#git#execution#plan#phases#project-planning#feature-management
One-click install
npx skills add https://github.com/ianphil/prism --skill work-plan-ianphil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-plan
Source: https://github.com/ianphil/prism/tree/main/.claude/skills/work-plan
Command: npx skills add https://github.com/ianphil/prism --skill work-plan-ianphil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Work Plan skill helps product teams and engineers generate a structured execution plan for a feature, including current status, phase breakdown, recommended actions, and a concise next step. It automates the preparation of a living plan file and a brief console summary.

Core Features & Use Cases

  • Automatically derive phase status from {feature-path}/tasks.md and related docs.
  • Produce a ready-to-share work plan {feature-path}/work-plan.md and a compact console summary.
  • Support feature-level planning across branches, backlog items, and specs to streamline execution.

Quick Start

To generate a plan for a feature, run the work-plan command with the feature ID. If you are on a feature branch, omit the argument to auto-detect the ID. The plan is written to {feature-path}/work-plan.md and a summary is shown in the console.

Frequently Asked Questions about work-plan

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

FAQPage Schema
How do I generate a structured execution plan for feature development?▼

Generating a structured execution plan involves analyzing tasks.md and spec.md files to compute progress, producing a work-plan.md file with phase breakdowns and next actions for feature development.

Can I auto-detect feature planning parameters from a git branch?▼

Feature planning parameters can be auto-detected by omitting the feature ID argument when on a feature branch, allowing the system to automatically identify the relevant tasks.md and spec.md files.

What is the best way to track project status across backlog items?▼

The best way to track project status across backlog items is by deriving phase status and recommended actions from tasks.md files, outputting a living work-plan.md file alongside a concise console summary.

Does the feature work plan automatically compute progress from markdown specs?▼

The feature work plan automatically computes progress by reading feature-path tasks.md and spec.md files to determine current status and generate a recommended phase breakdown for the project.

Do I need a tasks.md file to use automated feature work planning?▼

A tasks.md file in the feature path is required because the automated feature work planning reads it alongside spec.md to compute progress and write the structured work-plan.md output.

Related Skills

Explore More Product & Management Skills→
ianphilianphil

planner

Generate planning artifacts, contracts, data models, specs, and test templates for backlog items.

Community
Intermediate
lee-tolee-to
1.1k

ai-factory.implement

Execute plan tasks with state updates and progress persistence.

Community
Advanced
akiojinakiojin
4

release

Automate version updates, changelog generation, and release pull requests from develop to main.

Community
Advanced
Pear-CommercePear-Commerce

gsd-progress

Summarize project progress and route GSD workflows to phase plans.

Official
Intermediate