09-REVIEW-planfixes

Design three architectural fix approaches for each code review finding.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/medtrics/medtrics-acumen --skill 09-review-planfixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 09-REVIEW-planfixes
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/shared/skills/09-REVIEW-planfixes
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 09-review-planfixes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically plan and prioritize fixes for issues identified during code reviews or user testing, ensuring the most effective and maintainable solutions are chosen.

Core Features & Use Cases

  • Systematic Issue Analysis: Catalogues findings from multiple sources (code review, clickthrough) into a unified list.
  • Multi-Solution Design: Generates three distinct architectural approaches for each identified issue.
  • Prioritized Fix Planning: Creates an actionable execution plan based on severity and selected solutions.
  • Use Case: After a user reports a bug and a code review flags several violations, this Skill will help the team decide on the best way to fix everything, ensuring architectural integrity and maintainability.

Quick Start

Use the 09-REVIEW-planfixes skill to design three fix approaches for the findings in FINDINGS.md and the code review report.

Frequently Asked Questions about 09-REVIEW-planfixes

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

FAQPage Schema
What is the best way to plan architectural fixes for code review findings?

To plan fixes for code review findings, you design three distinct architectural approaches for each issue, prioritize them by simplicity and maintainability, and generate a unified finding catalogue with an actionable execution plan.

How do I prioritize bug fixing tasks from user testing and code reviews?

You prioritize bug fixing tasks by cataloguing findings from multiple sources into a unified list, evaluating three solution approaches per issue based on severity and architectural integrity, and generating a prioritized fix execution plan.

Why design multiple solution approaches for a single bug finding?

Designing multiple solution approaches prevents premature commitment to one fix, allowing teams to compare trade-offs in simplicity, scalability, and maintainability before selecting the most effective architectural path for the specific bug.

Can I systematically catalogue issues from both code reviews and clickthrough testing?

Yes, you can systematically catalogue issues by consolidating findings from code reviews and clickthrough outputs into a unified finding catalogue before designing the three architectural fix approaches for each identified issue.

How do I ensure my bug fixes align with existing software architecture?

You ensure fixes align with existing architecture by evaluating each proposed solution against established architecture and schema conventions, prioritizing approaches that maintain system integrity while resolving the identified code review findings.