postmortem-and-learning-extractor
Extracts reusable lessons after incidents, failures, or project milestones. Use to update skills and prevent future mistakes.
Browse published AI skills maintained by hohai99. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
36Repository stars across indexed skills
0Repository forks
36Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Extracts reusable lessons after incidents, failures, or project milestones. Use to update skills and prevent future mistakes.
Validates that changes maintain parity with previous system behavior and don't introduce regressions. Use after implementation or migration.
Captures existing system behavior before migration to ensure parity. Use at the start of any migration project.
Orchestrates the correct skills automatically across project creation and migration workflows. Use as the default controller.
Extracts architectural, business, and operational context from existing systems. Use to build mental models of unfamiliar codebases.
Analyzes user prompt behavior over time to infer stable intent patterns and preferences. Use continuously to minimize friction.
Monitors overall project health across time, specifically looking for spec drift and debt. Use during regular project reviews.
Builds and enforces a shared domain vocabulary for the project to prevent terminology drift and confusion. Use when specs or code involve domain terms.
Prevents MVP scope creep based on this project's constraints. Use during early design.
Implements tasks strictly according to specification without invented behavior. Use during coding.
Ensures new designs align with existing project architecture patterns to prevent drift and technical debt. Use when proposing or reviewing architecture.
Defines observable system behavior independent of implementation details. Use before refactoring, migrating, or rewriting legacy systems.
Converts ambiguous requirements into strict, implementable specifications. Use before any coding.
Prevents implementers from crossing spec or task boundaries. Use during coding.
Ensures that system changes don't break existing API consumers or persistent data structures. Use during feature modifications.
Tracks, classifies, and prioritizes technical debt (code, spec, and process) over time. Use to prevent silent rot.
Proposes creation, modification, or retirement of skills based on recurring user needs and system friction.
Determines whether documentation is sufficient to proceed without human clarification. Use before implementation to prevent rework.
Applies project-specific regression criteria to ensure existing functionality remains intact. Use during testing and review.
Fixes implementation bugs detected by tests while preserving spec intent. Use only after test failures classified as implementation bugs.
Generates tests directly from specifications and tasks. Use immediately after implementing a task.
Executes generated tests and interprets results without human input. Use after tests are generated.
Detects mismatches between implementation and specification. Use when tests fail but behavior seems intentional.
Ensures changes respect security, privacy, and compliance constraints. Use before release.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.