メニュー
Converts a GitHub issue into a structured implementation plan. Use when starting work on a feature request, bug fix, or refactoring task. Produces a step-by-step plan with files to modify, tests to write, and acceptance criteria.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | issue-to-plan |
| description | Converts a GitHub issue into a structured implementation plan. Use when starting work on a feature request, bug fix, or refactoring task. Produces a step-by-step plan with files to modify, tests to write, and acceptance criteria. |
Read the issue carefully. Extract:
Explore the codebase to understand:
Create the plan as a checklist in this format:
## Implementation Plan for #[issue-number]
### Summary
[One paragraph describing what needs to be done and why]
### Files to Modify
- [ ] `path/to/file.ext` — [what changes and why]
- [ ] `path/to/other.ext` — [what changes and why]
### Files to Create
- [ ] `path/to/new-file.ext` — [purpose]
### Steps
1. [ ] [First concrete step]
2. [ ] [Second step, depends on #1]
3. [ ] [Write tests for X]
4. [ ] [Update documentation]
### Tests Needed
- [ ] [Test case description]
- [ ] [Edge case description]
### Acceptance Criteria
- [ ] [Criterion from issue]
- [ ] [Inferred criterion]
- [ ] All existing tests pass
- [ ] New tests cover the changes
Full WCAG 2.2 AA accessibility audit procedure. Goes beyond the reference checklist with step-by-step testing methodology, tooling, and remediation guidance.
Design a RESTful API from requirements. Use when creating a new API, adding endpoints, or restructuring an existing API. Produces endpoint specifications, schemas, and implementation guidance.
Assess system architecture, identify risks and bottlenecks, document decisions with ADRs. Covers modular monolith, microservices, event-driven, and serverless patterns.
Shift Left quality gates, feature flag pipelines, and deployment automation. Use when setting up or modifying build and deploy pipelines, or when establishing quality gates for a project.
Perform a thorough code review with structured feedback. Use when reviewing pull requests, code submissions, or when you want a quality check on your code. Covers correctness, security, performance, readability, and maintainability.
Reduce complexity while preserving exact behavior. Use when code works but is harder to read or maintain than it should be. Applies Chesterton's Fence — understand the code before simplifying it.