plan-export

To generate an implementation plan for a GitHub issue, this Skill reads project-specific rules and context to outline objectives, files to modify, implementation details, and verification steps for each phase. It outputs a structured Markdown document guiding developers through the task.

A phased implementation plan breaks down a GitHub issue into structured steps, detailing objectives, code modifications, unit tests, and verification procedures. It ensures junior developers understand project conventions and complete tasks systematically with linting and formatting checks.

Yes, you can integrate project-specific conventions when generating an implementation plan. The Skill reads applicable rules directly from specified directories like `.cursor/rules/` to ensure the exported plan adheres to your established code workflow and guidelines.

To ensure unit tests and linting checks are included in your code workflow plan, the Skill mandates the addition of verification steps for each phase. It automatically generates instructions for running formatting checks and tests alongside implementation details.

Yes, plan-export works without configuring external dependencies because it operates autonomously to parse GitHub issue context and local rules. It relies solely on reading your project directories to generate the required Markdown output.

You should use automated plan generation when assigning complex GitHub issues to junior developers. It provides structured developer guidance by translating high-level feature discussions into actionable, phased implementation plans with specific files to modify and test.