Analyze harness workflow and application code to generate improvement proposals.
npx skills add https://github.com/jstoup111/ai-conductor --skill retro-jstoup111
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
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.
Run the retro skill after finishing a feature to analyze the harness workflow and application code.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
FriendlyInternetAnalyze Claude Code harness context size, redundancy, and usage traces.
geekdesign27Apply elicitation methods to refine and improve recent LLM-generated content.
KrismithReddy12Calculate a weighted 0-10 code quality score from linters and test runners.
tonombCompare HEAD against a fixed point to review code standards and spec alignment.
