retro

Analyze harness workflow and application code to generate improvement proposals.

5|1|Updated Mar 30, 2026

Search Tags:#code quality #code analysis #retrospective #improvement proposals #harness performance

Ready to run

npx skills add https://github.com/jstoup111/ai-conductor --skill retro-jstoup111

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/retro
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill retro-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps analyze and improve both the harness workflow and the application code produced after completing a feature or milestone, providing actionable proposals for enhancement.

Core Features & Use Cases

Dual Retrospective Analysis: Analyze both the harness workflow and the application code.
Improvement Proposals: Generates concrete proposals for improving the harness and code quality.
Use Case: After finishing a feature, use this Skill to assess how well the harness performed and the health of the code produced, then generate proposals for improvement.

Quick Start

Run the retro skill after finishing a feature to analyze the harness workflow and application code.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I conduct a retrospective on both my workflow and application code after finishing a feature?▼

A dual retrospective analyzes both the harness workflow and the application code produced after completing a feature, assessing performance, code quality, and context efficiency. It then generates concrete improvement proposals for both harness and code enhancements.

What is a code quality retrospective and when should I run one?▼

A code quality retrospective evaluates the health of application code and harness performance after a milestone. You should run it immediately after finishing a feature to assess how well the harness performed and generate actionable improvement proposals.

How do I generate improvement proposals for harness performance and code analysis?▼

Improvement proposals are generated by conducting a dual retrospective that analyzes harness workflow performance, application code quality, and context efficiency. This provides concrete, actionable proposals for enhancing both the harness and the codebase.

Can I analyze context efficiency and harness workflow without external dependencies?▼

Yes, you can analyze context efficiency and harness workflow performance without external dependencies. The retrospective skill operates independently using internal scripts and references to assess code quality and generate improvement proposals.

What's the best way to assess code health and harness performance after a milestone?▼

The best way to assess code health and harness performance after a milestone is running a dual retrospective. This approach evaluates both the application code produced and the harness workflow simultaneously, generating concrete improvement proposals for future enhancements.

Why does my harness workflow need a retrospective after feature completion?▼

A harness workflow retrospective is needed after feature completion to evaluate how well the harness performed during development. It analyzes performance and context efficiency, producing concrete proposals to improve future harness workflows and application code quality.