ngmthaq/bugfix-plan-template
skills/bugfix-plan-template/SKILL.md
Bug-Fix Plan Template — Structured plan template for debugging and fixing bugs, focused on diagnosis, impact analysis, and task breakdown without requiring a feature doc.
$ install --global
skillsauthnpx skillsauth add ngmthaq/my-copilot bugfix-plan-templateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:13 PM119.2s1 file scanned
SKILL.md
- name:
- bugfix-plan-template
- description:
- Bug-Fix Plan Template — Structured plan template for debugging and fixing bugs, focused on diagnosis, impact analysis, and task breakdown without requiring a feature doc.
Bug-Fix Plan Template
When to Use
- Before implementing any bug fix, especially for classified bugs from agent
Location & Naming Convention
Follows the same location as plan documents, with a agent-plan-fix- prefix:
{doc_directory}/<date-time>-agent-plan-fix-<bug-summary>.md
Examples:
{doc_directory}/20260405-1715-agent-plan-fix-cors-in-user-creation-form.md{doc_directory}/20260406-0930-agent-plan-fix-null-pointer-in-auth-service.md
Rules
- Always create the plan file.
Template
# Fix: <Bug Summary>
---
## 1. Diagnosis
- **Error**:
- **Root Cause**:
- **Affected Code**:
- **Reproduction Steps**:
---
## 2. Impact Analysis
- Affected features:
- User impact:
- Severity: (Low / Medium / High / Critical)
---
## 3. Purpose
<Why this fix is needed and expected outcome>
---
## 4. Fix Strategy
- Approach:
- Alternative approaches considered:
- Why this approach:
---
## 5. Task Breakdown
---
### T1
- **Name**: Identify and isolate faulty logic
- **Agent**: debugger
- **Description**:
- **Dependencies**: []
- **Acceptance Criteria**:
- Root cause confirmed in code
---
### T2
- **Name**: Implement fix
- **Agent**: relevant developer
- **Description**:
- **Dependencies**: [T1]
- **Acceptance Criteria**:
- Bug no longer reproducible
---
### T3
- **Name**: Add/Update tests
- **Agent**: qa-engineer
- **Description**:
- **Dependencies**: [T2]
- **Acceptance Criteria**:
- Test covers bug scenario
---
### T4
- **Name**: Regression testing
- **Agent**: qa-engineer
- **Dependencies**: [T3]
- **Acceptance Criteria**:
- No existing functionality broken
---
### T5
- **Name**: Code review
- **Agent**: code-reviewer
- **Dependencies**: [T2, T3]
- **Acceptance Criteria**:
- Code quality and security validated
---
## 6. Parallel Execution Notes
- T2 and T3 can partially overlap (if safe)
- T4 MUST wait for T2 & T3
- T5 can run after implementation but before full regression completion
---
## 7. Validation Criteria (Definition of Done)
- Bug cannot be reproduced
- Automated test added
- No regression issues
- Code reviewed and approved
---
## 8. Risks
| Risk | Impact | Mitigation |
| ----------- | ------ | ------------------- |
| Regression | High | Add tests |
| Partial fix | Medium | Validate edge cases |
---
## 9. Agent Assignments Summary
| Task | Agent | Skills |
| ---- | ----- | ------ |
| T1 | ... | ... |
| T2 | ... | ... |
| T3 | ... | ... |
| T4 | ... | ... |
| T5 | ... | ... |
> **Note**: Always list all skills required for each task to ensure proper agent assignment.
---
## 10. Progress Tracking
- [ ] T1
- [ ] T2
- [ ] T3
- [ ] T4
- [ ] T5
> Update as tasks complete
Related Skills
ngmthaq/technical-leader-job-protocols
documentation
VerifiedTrustedCommunity
Guidelines and protocols for Technical Leaders to manage and oversee technical projects effectively while adhering to the core mandate of being the central orchestration layer for all engineering work.
1SKILL.mdUpdated May 4, 2026
ngmthaq/sql-optimization
data-ai
VerifiedTrustedCommunity
Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance.
1SKILL.mdUpdated May 4, 2026
ngmthaq/solid-principle
development
VerifiedTrustedCommunity
SOLID — Enforces the SOLID principle of object-oriented design (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for maintainable and scalable code.
1SKILL.mdUpdated May 4, 2026
ngmthaq/separation-of-concerns
development
VerifiedTrustedCommunity
Separation of Concerns (SoC) — Enforces the Separation of Concerns principle by ensuring each module, layer, and component addresses exactly one well-defined concern. Use when writing, reviewing, or refactoring code that mixes UI with business logic, business logic with data access, presentation with formatting, or cross-cutting concerns (auth, logging, validation) with core logic.
1SKILL.mdUpdated May 4, 2026