Results for “retrosynthesis”

Retro

Almost every downstream bug traces back to an index that was assumed regular and

Update old notes with new connections. The backward pass that /reflect doesn't do. Revisit existing notes that predate newer related content, add connections, sharpen claims, consider splits. Triggers on "/reweave", "/reweave [note]", "update old notes", "backward connections", "revisit notes".

Use the retrospective skill to generate a post-release blameless

Weekly engineering retrospective. (gstack)

Runs a full retrospective and dev cycle analysis, chaining /recall and /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings.

Generates a post-release blameless retrospective from project signals — synthesizing DORA-like metrics, WorkItem outcomes, session timeline, and drift deltas into a structured Artifact + LogEntry. Use at the end of a release cycle when asked to run a retro, "post-release review", "retrospective", or "post-mortem".

Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.

Weekly engineering retrospective. (gstack)

Applied Botany Synthesis Skill

Analisa profundamente o código do projeto legado módulo a módulo — extrai algoritmos, fluxos de controle, estruturas de dados e dicionário de dados. Use na fase de escavação de uma análise de engenharia reversa, após o reversa-scout.

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Provides structured reverse engineering techniques for analyzing compiled, obfuscated, packed, or virtualized targets including binaries, APKs, WASM, firmware, and custom VMs using static and dynamic analysis workflows.

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

Process and analyze mass spectrometry data: import spectra from MGF, mzML, MSP, and JSON formats; apply 40+ filters for metadata harmonization and peak cleaning; compute spectral similarities (cosine, modified cosine) for compound identification; build reproducible processing pipelines.

Mines git history and codebase to reconstruct the development lifecycle, identify sequential and parallel patterns, and produce actionable recommendations for future iterations.

Botany Synthesis Expert Skill

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

Botany Based Synthesis Skill

Hard Negative Mixing for Contrastive Learning

Weekly engineering retrospective. (gstack)

AI music generation with ACE-Step 1.5 — background music, vocal tracks, covers, stem extraction for video production. Use when generating music, soundtracks, jingles, or working with audio stems. Triggers include background music, soundtrack, jingle, music generation, stem extraction, cover, style transfer, or musical composition tasks.

Multi-perspective dialectical reasoning with cross-evaluative synthesis. Spawns parallel evaluative lenses (STRUCTURAL, EVIDENTIAL, SCOPE, ADVERSARIAL, PRAGMATIC) that critique thesis AND critique each other's critiques, producing N-squared evaluation matrix before recursive aggregation. Triggers on /critique, /dialectic, /crosseval, requests for thorough analysis, stress-testing arguments, or finding weaknesses. Implements Hegelian refinement enhanced with interleaved multi-domain evaluation and convergent synthesis.

Runs a disciplined diagnosis loop for hard bugs and performance regressions, from reproduction through hypothesis testing, instrumentation, fixing, and regression testing.

OpenCLIP: An Open Source Implementation of CLIP

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

Synthesize retrospectives into themes, root causes, decisions, and team improvements.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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.