plan-work

Guide planning conversations and generate structured GitHub issues.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/chriswickett/agentic-github --skill plan-work-chriswickett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/chriswickett/agentic-github/tree/main/skills/plan-work
Command: npx skills add https://github.com/chriswickett/agentic-github --skill plan-work-chriswickett

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-work helps teams structure early-stage work by guiding interactive questions and converting the results into a ready-to-action GitHub issue.

Core Features & Use Cases

  • Guided planning dialogue to clarify scope, acceptance criteria, dependencies, and success metrics.
  • Automatic issue creation with a structured body that captures problem statement, proposed plan, and next steps.
  • Works in issue comments or PR discussions to kick off work without leaving GitHub.

Quick Start

Start a planning session by typing /plan-work in a GitHub issue comment or PR discussion.

Frequently Asked Questions about plan-work

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

FAQPage Schema
How do I create structured GitHub issues from a planning dialogue?

You can create structured GitHub issues by initiating a guided planning session that asks questions to define scope, acceptance criteria, and dependencies, then automatically generates a formatted issue with a problem statement and proposed plan.

What is the best way to define project scope and acceptance criteria before development?

Defining project scope and acceptance criteria is best handled through a guided conversational workflow that parses your responses during discovery and planning phases to ensure all success metrics are captured before work begins.

Can I plan work directly within a GitHub PR discussion?

Yes, you can plan work directly within a GitHub PR discussion or issue comment by invoking the planning command, which kicks off the interactive scope definition process without leaving your repository context.

Does issue creation work without a connected GitHub repository context?

Issue creation requires access to a GitHub repository context to successfully parse user responses and format the structured issue body containing the problem statement, proposed plan, and success criteria.

How do I organize software work tasks across discovery and handoff phases?

To organize software work tasks across discovery and handoff, use a conversational workflow that coordinates questions to identify dependencies and formats the results into a single actionable issue for execution.