planning

Convert planning conversations into tracked GitHub issues mapped to a single PR.

29|1|Updated Jul 18, 2015
One-click install
npx skills add https://github.com/joshmanders/dotfiles --skill planning-joshmanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/joshmanders/dotfiles/tree/main/claude/skills/planning
Command: npx skills add https://github.com/joshmanders/dotfiles --skill planning-joshmanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating engineering work using GitHub issues to create a lightweight, end-to-end workflow where each session maps to a single issue and PR, helping teams start work with clear scope and traceability.

Core Features & Use Cases

  • Plan-driven issue creation and tracking
  • Plan mode with draft planning, approval, and execution
  • Scope management and handling of mid-session changes

Quick Start

Begin planning by drafting your first issue in plan mode and obtain approval before creating the GitHub issue.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I map GitHub issues to pull requests for feature planning?

Map GitHub issues to pull requests by drafting a plan in plan mode, defining requirements and acceptance criteria, then creating a tracked issue that corresponds to exactly one PR for end-to-end traceability.

What is the best way to handle scope changes mid-session in GitHub?

Handle mid-session scope changes by entering plan mode to redefine requirements and contexts, adjusting the existing GitHub issue workflow to ensure the work still maps cleanly to a single PR.

How do I draft GitHub issues with clear acceptance criteria before coding?

Draft GitHub issues with acceptance criteria by using plan mode to define requirements, contexts, and workflows first, obtaining approval before creating the issue and starting execution on the PR.

Does enforcing one issue per PR workflow work for lightweight engineering coordination?

Yes, enforcing one issue per PR provides lightweight engineering coordination by turning planning conversations into tracked GitHub issues, ensuring clear scope and traceability within a single session.