Forge-Defect-Management

Records, triages, tracks, and verifies defects through the software development lifecycle.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-defect-management-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Defect-Management
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/04-Quality/Forge-Defect-Management
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-defect-management-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of bugs when defects are reported informally, closed without verification, or never prioritized against impact. This Skill provides a single accountable process that captures every defect, assesses severity and priority, tracks it to resolution, and verifies the fix against the original failure evidence. ## Core Features & Use Cases - Structured Defect Recording: Capture defects with reproduction steps, evidence, environment details, and severity using the Work-Item template. - Triage and Prioritization: Assess severity by user and business impact separately from priority, using a prioritisation matrix for consistent decisions. - Verified Closure and Trend Reporting: Close defects only after fix verification against original failure evidence, and report defect trends to inform testing strategy and release readiness. - Use Case: A QA engineer discovers a checkout failure during test execution. Use this Skill to record the defect with evidence, triage it as high severity, assign it for resolution, track it through the fix, and verify closure before the release readiness review. ## Quick Start Use the Forge-Defect-Management skill to record a newly discovered defect with its reproduction steps, severity, and priority, then track it through to verified closure.

Frequently Asked Questions about Forge-Defect-Management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record and track a software defect?▼

Record the defect using the Work-Item template with reproduction steps, evidence, and environment details. Then assess severity, assign priority, track status through analysis and fix, and verify closure against the original failure evidence.

What is the difference between defect severity and priority?▼

Severity reflects user and business impact of the defect, while priority reflects the agreed response urgency. This Skill assesses them separately so triage decisions stay consistent across teams and iterations.

When should a defect be marked as closed?▼

A defect is closed only when the fix is verified against the original failure evidence. A fix without verification is not closure; unverified defects are returned with clear rationale.

When should I not use a defect management process?▼

Do not use it for executing tests, performing root-cause analysis in code, debugging, assessing release readiness, or managing feature backlogs and technical debt. Those activities belong to their respective dedicated skills.

How do defect trends inform testing strategy?▼

Defect data is analyzed for patterns across iterations and reported as quality indicators. These trends feed back into test strategy, development practices, and release readiness assessments.