remediation-log

Generate security remediation tracking documentation for vulnerability fixes and SLA compliance.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill remediation-log-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remediation-log
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/security/remediation-log
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill remediation-log-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security findings often get lost after an assessment, with no structured record of who is fixing what, by when, and whether fixes were verified. This Skill produces a signed remediation log that tracks every vulnerability from discovery through verified closure. ## Core Features & Use Cases - Remediation Tracking: Generates a structured log with per-finding remediation plans, progress updates, blockers, and verification checklists keyed to vulnerability IDs. - SLA and Metrics Reporting: Produces severity-based SLA status tables, time-to-remediate metrics, weekly burndown, and exception tracking for accepted risks and deferred fixes. - Governed Sign-Off: Enforces validation rules, a sources file, and CISO approval before the document can gate downstream SDLC phases. - Use Case: After a penetration test produces a vulnerability report, use this Skill to create a remediation log assigning each finding to an owner with SLA deadlines, then track fixes to verified closure for audit evidence. ## Quick Start Ask the agent to run the remediation-log skill to create a remediation tracking document from the signed vulnerability report for your project.

Frequently Asked Questions about remediation-log

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

FAQPage Schema
How do I create a vulnerability remediation tracking document?▼

Run the remediation-log skill after your vulnerability report is signed. It gathers the findings, SLAs, and responsible teams, then generates a remediation log with per-finding plans, progress updates, and verification records.

What should a security remediation log include?▼

A remediation log should include severity-based progress summaries, SLA status tables, per-finding remediation plans with owners and target dates, verification evidence, exception tracking for accepted risks, and approval signatures.

What are the prerequisites for running the remediation-log skill?▼

The vulnerability-report document must exist and be signed before this skill runs. You also need the security assessment, SLA requirements, and assigned responsible teams as inputs.

How are remediation SLAs tracked by severity?▼

The generated log tracks SLAs per severity tier: Critical at 24 hours, High at 7 days, Medium at 30 days, and Low at 90 days. It reports on-track, at-risk, and breached counts plus average time-to-remediate against targets.

Who approves the remediation log document?▼

The CISO holds final approval authority and must sign the document. The Development Lead confirms fix completion, and the CISO also approves any risk exceptions or deferred remediations.