plan-work

Fetch GitHub issue data, validate readiness, and post an implementation plan comment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams convert GitHub issues into concrete, reviewable implementation plans, reducing ambiguity and speeding up onboarding.

Core Features & Use Cases

  • Fetch issue data (title, body, labels, comments) and determine readiness.
  • Analyze requirements and generate a structured implementation plan.
  • Post the plan as a GitHub issue comment for maintainer review.
  • Update issue labels to reflect status and prevent duplicate work.
  • Audit trail: track plan references and changes for idempotency.

Quick Start

Provide the issue_number input and run plan-work to generate and post an implementation plan for maintainer review.

Frequently Asked Questions about plan-work

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

FAQPage Schema
How do I generate an implementation plan from a GitHub issue automatically?

To generate an implementation plan from a GitHub issue, you provide the issue number to trigger automated fetching, requirements analysis, and the posting of a structured plan comment for maintainer review.

What is the best way to automate issue triage and readiness validation in GitHub?

Automating issue triage involves fetching issue data like titles, bodies, and labels to determine readiness, then generating a structured plan and updating status labels to prevent duplicate work.

Can I generate implementation plans for GitHub issues without modifying the repository code?

Yes, generating implementation plans for GitHub issues is a non-mutating process that only posts a plan comment, manages status labels, and returns a canonical plan artifact without altering the repository code.

How does issue readiness validation work when generating an implementation plan?

Issue readiness validation works by fetching the issue's title, body, labels, and comments to determine if the requirements are sufficient to produce a structured implementation plan.

Does the plan generation workflow support audit trails for idempotency?

Yes, the plan generation workflow supports idempotency by maintaining an audit trail that tracks plan references and changes, ensuring duplicate plans are not generated for the same issue.

How do I post a structured implementation plan as a comment on GitHub?

To post an implementation plan as a comment on GitHub, the skill analyzes the issue requirements, generates the plan, and submits it directly to the issue thread for maintainer review.