skills.rest
tektonlabs
tektonlabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

defect-log

Generates defect tracking templates, lifecycle workflows, and SLA metrics for bug management.

Updated Aug 26, 2026
Search Tags:#quality assurance#sdlc#triage#sla#bug management#defect tracking#qa process
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill defect-log-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defect-log
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/development/defect-log
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill defect-log-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent, signed-off process for logging, triaging, and resolving defects, but building defect tracking templates, severity classifications, and SLA tables from scratch is repetitive and error-prone. ## Core Features & Use Cases - Defect Log Generation: Produces a complete defect-log.md document with severity/priority classifications, lifecycle states, and reporting templates. - Metrics & SLA Tracking: Includes defect density, mean time to fix, reopen rate, and SLA compliance tables with escalation paths. - Governance Integration: Enforces validation rules, signature gating by the Technical Lead, and cross-references to prerequisite governance documents. - Use Case: During Phase 8 (Development) of a project, a QA lead invokes the skill to produce a signed defect management document that downstream test-report skills consume. ## Quick Start Ask the agent to create the defect log for your project after the governance document has been signed.

Frequently Asked Questions about defect-log

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

FAQPage Schema
How do I create a defect tracking process for my project?▼

Invoke the defect-log skill after the governance document is signed. It gathers your tracking tool, severity definitions, SLA requirements, and team structure, then generates a complete defect-log.md with templates, lifecycle workflows, and metrics tables.

What severity levels should a defect log define?▼

The generated template defines four severity levels: Critical (system unusable, 4-hour fix SLA), High (major feature broken, 1 day), Medium (workaround exists, 3 days), and Low (cosmetic, next release), each with examples and response targets.

What prerequisites are required before running the defect-log skill?▼

The governance-doc skill must be completed and signed before this skill runs. Validation rules block execution if prerequisites are unsigned, and the output must be written to documentation/08-development/defect-log.md.

Which tools does the defect log template support?▼

The template supports common bug tracking tools including JIRA, Azure DevOps, and GitHub Issues. You specify your primary tool and reporting dashboard during the input gathering step.

Who approves the defect log document?▼

The Technical Lead holds final approval authority and signs the document. The QA Lead and Project Manager review the defect process and SLAs, but their review does not gate the signature.

Related Skills

Explore More Software Engineering Skills→
SeaBrad72SeaBrad72
1

design

Enforce design-first approval gates before code generation in agentic development.

Community
Advanced
WebWakaHubWebWakaHub
20

Test Results Analyzer

Analyze test execution results to identify failure patterns and release readiness risks.

Official
Advanced
CENKSSSCENKSSS

qcsd-production-swarm

Assess post-release production health using DORA metrics, root cause analysis, and defect prediction.

Community
Advanced
goffitygoffity

focus

Create GitHub issues or Jira tickets and generate feature branches.

Community
Advanced