One-click install
npx skills add https://github.com/KMakayee/playbook --skill issue-plan-kmakayee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-plan
Source: https://github.com/KMakayee/playbook/tree/main/.claude/skills/issue-plan
Command: npx skills add https://github.com/KMakayee/playbook --skill issue-plan-kmakayee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an issue’s research artifact into an implementation-ready, phased plan that’s reviewed by Codex for feasibility, completeness, and risks.

Core Features & Use Cases

  • Builds a plan from the research artifact: Uses tasks/research-issue-$ARGUMENTS.md (the ## Recommended Approach section) plus the acceptance criteria from tasks/issues.md.
  • Cross-checks with Codex: Runs a structured review that classifies findings as CORRECTION, TRADE-OFF, or RISK, then absorbs corrections and decisions back into the plan.
  • Produces a handoff artifact only: Writes tasks/plan-issue-$ARGUMENTS.md, cleans up Codex temp output, and updates issue status to In Review without implementing code changes.

Quick Start

Ask your AI agent to generate the plan for issue 12 by running: /issue-plan 12

Frequently Asked Questions about issue-plan

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

FAQPage Schema
How do I generate an implementation plan from issue research artifacts?

To generate an implementation plan, this skill synthesizes the recommended approach from research artifacts and acceptance criteria into phased, success-verifiable steps. It creates a handoff document in your tasks directory for engineering use.

What is a Codex review classification rubric for engineering workflows?

A Codex review classification rubric evaluates an implementation plan by categorizing findings as CORRECTION, TRADE-OFF, or RISK. The workflow then absorbs corrections and decisions back into the plan document to ensure feasibility and completeness before implementation.

Do I need a research artifact before planning phased implementation?

Yes, phased implementation planning requires validating the existence of a research artifact containing the recommended approach and acceptance criteria. Planning cannot proceed without this foundational research document stored in your tasks folder.

How do I validate readiness and update issue status before coding?

To validate readiness before coding, the planning process checks the finalized plan artifact and updates the issue status to In Review. This ensures the engineering workflow only advances when the plan has successfully passed feasibility checks.

What are the limitations of generating a plan with issue research?

The limitation of this planning process is that it produces a handoff artifact only and does not implement code changes. It cleans up temporary review outputs and leaves the actual coding to a subsequent workflow step.