Skip to content

renzrollon/shippable-skills / skills/productivity/session-retro

session-retro

Verified

Retro the current session. Score it against session shapes, flag token waste with next-turn fixes, and propose wire-ins into the skills this conversation actually called.

evals/cases/focus-wiring.yaml

View on GitHub
id: focus-wiring
title: Wiring focus stays honest about what this session actually called
description: |
  Natural-language --focus wiring. This eval turn did not run tdd or write a
  new skill, so the reply must not paste the SKILL.md example row. It should
  still close with the handoff index line.

input:
  prompt: |
    /session-retro what should we wire into the skills we called

expect:
  must_not_contain:
    - "Re-ran the full suite after each one-line edit"
    - "the tdd skill's SKILL.md"
    - "## Procedure to Encode"

judge:
  type: rule_based
  failure:
    - output_contains:
        any:
          - "Re-ran the full suite after each one-line edit"
          - "the tdd skill's SKILL.md"
          - "## Procedure to Encode"
          - "Next-turn fix"
  success:
    - output_contains:
        all:
          - "Hand wire-ins"
    - output_contains:
        any:
          - "No skills / workflows invoked this session"
          - "session-retro"
          - "wire-in"
          - "No new skill candidates from this session"
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall