draft-fix-design

Convert root-cause analyses into design.yaml fix plans with file-level changes.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill draft-fix-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-fix-design
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/draft-fix-design
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill draft-fix-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a completed root-cause analysis into an actionable fix design that a builder can implement safely and consistently, including tradeoffs and verification steps.

Core Features & Use Cases

  • Minimal safe fix strategy: Chooses the least-scoped change that addresses the root cause and avoids unnecessary refactors.
  • Alternatives with explicit rejection reasons: Documents at least one competing approach and why it was not selected (risk/scope/compatibility/test complexity).
  • Affected-files change map: Produces a file-by-file plan with actions, specific change descriptions, and risk rationales.
  • Self-sufficient execution plan: Writes ordered steps with expected outcomes and self-tests, then emits design.yaml.
  • Use case: After draft-rca generates rca.yaml for a production bug, this skill designs the repair plan so the fix-it play can implement it without ad-hoc YAML authoring.

Quick Start

Ask the agent to run draft-fix-design with rca_path set to your generated rca.yaml and output_base set to the folder where you want design.yaml written.

Frequently Asked Questions about draft-fix-design

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

FAQPage Schema
How do I convert a root cause analysis into a software remediation fix design?

Converting a root cause analysis into a fix design involves processing RCA inputs to produce a minimal safe fix strategy, mapping affected files with specific actions and risks, and emitting a self-sufficient execution plan.

What is a minimal safe fix strategy in software remediation?

A minimal safe fix strategy selects the least-scoped change addressing the root cause while avoiding unnecessary refactors, ensuring deterministic development during enterprise software remediation.

How do I map affected files for a production bug fix?

Mapping affected files for a production bug fix requires generating a file-by-file change map detailing specific actions, change descriptions, and risk rationales to guide safe software remediation.

Can I generate alternative remediation approaches with explicit rejection reasons?

Yes, you can generate alternative remediation approaches by documenting at least one competing fix design and providing a concrete rejection_reason based on risk, scope, compatibility, or test complexity.

Does the fix design process require YAML authoring for execution plans?

The fix design process outputs a design.yaml file containing a self-sufficient execution plan with ordered steps and confidence levels, eliminating the need for ad-hoc YAML authoring during software remediation.

When do I need a fix design for enterprise software remediation workflows?

You need a fix design during enterprise software remediation workflows after rca.yaml is produced, ensuring the fix-it play can implement the repair safely without ad-hoc YAML authoring.