メニュー
Use when asked to work on, read, or implement a GitHub issue - structured understand, plan, verify, implement, verify workflow with developer approval gates and mandatory verification
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when setting up a new Claude Code project, when a repo has no CLAUDE.md, or when starting work on an empty codebase - interviews the user and authors a CLAUDE.md covering project purpose, tech stack, TDD rules, and development practices
Use when the user asks for an architecture diagram, says 'show me the system architecture' or 'diagram the components', or during project planning - generates GitHub-compatible Mermaid flowcharts showing components, layers, subgraph boundaries, and data flows
Use when asked about project health, stale or blocked issues, deadline risk, or scope creep - scans GitHub issues and PRs with heuristics (staleness, blocked labels, milestone dates, size, unassigned high-priority) and produces a severity-ranked at-risk report
Use when building or updating an FAQ from closed GitHub issues, documenting recurring support questions, or reducing repeat questions - extracts common questions from resolved issues and generates a categorized FAQ document with synthesized answers and source links
Use when knowledge on a topic is scattered across multiple project notes and someone asks to consolidate, synthesize, or summarize what has been documented - searches notes by topic and produces a single summary with key points, timeline, cross-references, and documentation gaps
Use when asked 'what am I missing?', reviewing an issue or draft before submission, or checking documentation completeness - detects requirement, spec, and doc gaps and generates prioritized actionable questions
| name | working-on-an-issue |
| description | Use when asked to work on, read, or implement a GitHub issue - structured understand, plan, verify, implement, verify workflow with developer approval gates and mandatory verification |
Announce at start: "I'm using the working-on-an-issue skill to implement this GitHub issue."
A structured workflow for implementing GitHub issues with verification.
Core Principle: Understand → Plan → Verify → Implement → Verify Again
Before starting:
setting-up-a-project first)Get the issue content via:
gh issue view <number>Clarify before proceeding:
Do not assume or invent requirements not in the issue.
Use the superpowers:writing-plans skill (if available) or create a brief plan covering:
Save to docs/plans/issue-<number>-plan.md and get developer approval before proceeding.
Use the writing-verification-plans skill to create acceptance tests for the issue.
TDD.rules.md is present (a project-level TDD rules file, if the repo defines one)Run the verification plan. Report results using the verification log format from the writing-verification-plans skill.