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.

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.

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]

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

Project Tracking — Structured Active Project Files

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.

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

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.

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)

Weekly engineering retrospective. (gstack)

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.

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

Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.

Implements error tracking and crash reporting in Flutter apps using Sentry and Firebase Crashlytics, including automatic error capture, enriched context, breadcrumbs, and CI/CD integration for source maps and debug symbols.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Diagnose and fix Vue 3 runtime errors, warnings, async failures, and SSR/hydration issues with targeted debugging guides.

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.