메뉴
Fixes all bugs listed in a bugs.md file with root-cause analysis and regression tests. Use after QA has identified bugs that need fixing. Don't use for new features, code review, or QA testing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | run-bugfix |
| description | Fixes all bugs listed in a bugs.md file with root-cause analysis and regression tests. Use after QA has identified bugs that need fixing. Don't use for new features, code review, or QA testing. |
You are an AI assistant specialized in bug fixing.
You MUST fix ALL bugs listed in the bugs.md file For EACH fixed bug, create regression tests that simulate the original problem and validate the fix DO NOT apply superficial fixes or workarounds -- resolve the root cause of each bug The task is NOT complete until ALL bugs are fixed and ALL tests pass at 100% success START IMPLEMENTATION IMMEDIATELY after planning -- do not wait for approval
./tasks/prd-[feature-name]/bugs.md./tasks/prd-[feature-name]/prd.md./tasks/prd-[feature-name]/techspec.mdtasks/prd-[feature]/).tasks/prd-[feature]/bugs.md exists.run-qa) or create the file manually."run-qa to identify the bugs."tasks/prd-[feature]/prd.mdtasks/prd-[feature]/techspec.mdbugs.md fully.CLAUDE.md for project conventions.bugs.md marking each bug as fixed.Generates a Product Requirements Document (PRD) from a feature prompt. Use when planning a new feature, starting a project, or when asked to create a PRD. Don't use for technical specifications, task breakdowns, or implementation.
Breaks down a PRD and Tech Spec into an ordered list of implementable tasks. Use when PRD and Tech Spec are ready and the next step is planning the implementation sequence. Don't use for creating PRDs, writing specs, or implementing code.
Generates a Technical Specification from an existing PRD. Use when a PRD is ready and the next step is to define architecture, APIs, data models, and implementation strategy. Don't use for requirements gathering, task breakdown, or implementation.
Performs Quality Assurance on implemented features including E2E testing, accessibility checks, and requirements verification. Use after implementation and code review are done. Don't use for code review, implementation, or bug fixing.
Performs a structured code review of implemented features against the PRD and Tech Spec. Use after tasks are implemented and code needs quality validation. Don't use for QA testing, bug fixing, or implementation.
Implements a single task from the task list, including code, tests, and checks. Use when tasks have been created and the next step is writing code. Don't use for creating PRDs, specs, task lists, or code review.