Results for “remediation-tracking”

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements, and regulatory follow-up. Provides a systematic approach to preventing breach recurrence and demonstrating accountability to supervisory authorities. Keywords: post-breach, remediation, lessons learned, root cause, control gap, policy update, training.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Implement bounded remaining work for an issue-driven repository change after an authoritative verifier reports concrete gaps. Use when a workflow supplies an issue brief or assessment plus materialized gate-result and remaining-work evidence, and the existing candidate must be corrected without creating a MoonSpec feature packet.

Define and enforce vulnerability remediation SLAs based on severity, asset criticality, and exploit availability to drive accountability and track compliance.

Generates specific, implementable fixes for each vulnerability finding, producing code patches, configuration changes, dependency updates, and IaC fixes with before/after code and verification steps.

Audit Trail

Progress Tracking

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Monitor a live model for data quality, input and prediction drift, performance decay, and fire retraining triggers.

Mines git history to compute development quality, velocity, and stability metrics, compares them against stored baselines, and tracks improvement over time.

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

Detect and fix stale chunks (files that changed or were deleted since last indexing)

Project Tracking — Structured Active Project Files

Audit Trail

Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]

Diagnose and repair failing CI for an existing pull request without reopening the implementation pipeline.

Imported skill redlining from anthropic

Use to find the causes behind a complaint population and track whether remediation actually stopped them recurring. Trigger for "root cause analysis on our complaints", "why do we keep getting the same complaints", "complaint themes and remediation", recurring complaint categories, complaint reduction programmes, or a remediation that was signed off and did not work.

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

Tracks the dates of skills in the repository, with details maintained in a separate document.

Identify, categorize, and prioritize technical debt into a ranked, defensible backlog that ties each remediation to impact and effort — a register, not a wish list.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

Weekly engineering retrospective. (gstack)

CICD Fleet

Track code changes with structured JSON records, an enforced state machine, and a session handoff format for AI continuity.

Apply findings from a document-health-review report by updating, merging, splitting, moving, archiving, deleting, and repairing references for repository documents. Use when a user wants to execute approved document cleanup recommendations.

Debug agent execution by querying trace and metric tables, analyzing tool calls, durations, errors, and performance trends.

Diagnose and fix a bug through a disciplined reproduce, isolate, diagnose, fix, verify loop driven by evidence and one hypothesis at a time — not guesswork.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Investigates slow responses, tool failures, and guardrail rejections by querying agent trace logs and performance metrics.

Tracks media progress, reviews, collections, analytics, and calendar in Ryot, with automation support.

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.

Weekly engineering retrospective. (gstack)