request-design-fix

Revise design documents to correct implementation-phase deficiencies and realign with requirements.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill request-design-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-design-fix
Source: https://github.com/takemo101/compose-workflow/tree/main/.pi/skills/request-design-fix
Command: npx skills add https://github.com/takemo101/compose-workflow --skill request-design-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This command formalizes the process of correcting design flaws discovered during implementation, ensuring that deviations from the design are addressed by returning to the design phase rather than making ad-hoc changes.

Core Features & Use Cases

  • Formalized Design Correction: Integrates design fixes into the development workflow, preventing "shadow fixes."
  • Impact Analysis: Automatically assesses the scope of changes and identifies related design documents.
  • Iterative Review: Incorporates automated review cycles to ensure the quality of design corrections.
  • Use Case: An implementer finds a logical inconsistency in the detailed design document while coding. They use this skill, providing the issue number, the design document path, and a description of the inconsistency, initiating a formal correction process.

Quick Start

Use the request-design-fix skill to correct an issue in the design document located at docs/designs/detailed/user-auth.md, referencing GitHub issue #123 and describing the problem as an incorrect password reset flow.

Frequently Asked Questions about request-design-fix

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

FAQPage Schema
How do I fix design flaws discovered during software implementation without making ad-hoc code changes?

To fix design flaws during software implementation, you formalize design corrections by revising design documents and re-aligning them with project requirements. This prevents ad-hoc code changes by returning the workflow to the design phase.

What is the best way to track and resolve logical inconsistencies found in detailed design documents while coding?

Resolving logical inconsistencies in detailed design documents involves an iterative review process that analyzes the impact of changes and updates test specifications. This maintains system integrity while formally correcting the identified design deficiencies.

How does impact analysis work when modifying design documents to resolve implementation issues?

Impact analysis for design document modifications automatically assesses the scope of requested changes and identifies related design documents. This ensures all affected system components are evaluated before formal revisions are applied.

Do I need user approval to correct large-scale design deficiencies in my software development workflow?

User approval is required to correct large-scale design deficiencies in your software development workflow. The formal correction process includes automated review cycles and sends notifications upon completion to ensure system integrity.

How do I initiate a formal design correction process for a specific GitHub issue?

To initiate a formal design correction process for a GitHub issue, you provide the issue number, the design document path, and a description of the inconsistency. This triggers the workflow to formally revise the design.