skills.rest
DYAI2025
DYAI2025COMMUNITY
Explore all skills by this author →
GitHub

SDLC-fix

Plan user-reported software fixes with design alignment and traceability.

2|Updated Feb 23, 2026
Search Tags:#testing#documentation#sdlc#code-review#bug-fix#design-decisions#issue-elicitation
One-click install
npx skills add https://github.com/DYAI2025/Astro-Noctum --skill sdlc-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SDLC-fix
Source: https://github.com/DYAI2025/Astro-Noctum/tree/main/.claude/skills/SDLC-fix
Command: npx skills add https://github.com/DYAI2025/Astro-Noctum --skill sdlc-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured, interactive SDLC fix workflow: capturing the user-reported issue, clarifying scope, and aligning with design documents and decisions before any code is touched.

Core Features & Use Cases

  • Phase validation to determine the project's current state and the appropriate next action.
  • Issue elicitation and context gathering to understand problem scope, affected components, and constraints.
  • Contextual review of design artifacts, decisions, requirements, and potential tensions to ensure alignment.
  • Execution planning and validation including test strategy, traceability to decisions, and risk assessment.

Quick Start

Describe the user-reported issue and context to begin the elicitation workflow.

Frequently Asked Questions about SDLC-fix

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

FAQPage Schema
How do I scope and plan a software bug fix before writing code?▼

To scope a software bug fix, you need to capture the user-reported issue, gather context on affected components, and align with design decisions before coding. This ensures traceability to requirements and surfaces potential tensions early.

What is the best way to align software changes with existing design decisions?▼

Aligning software changes requires reviewing design artifacts and requirements to identify tensions or gaps. Structured issue elicitation ensures the planned fix traces back to current environment constraints and documented decisions.

How do I trace user-reported issues to testing and execution plans?▼

Tracing user-reported issues involves validating the project phase, gathering context, and creating an execution plan. This plan enforces traceability to design decisions, requirements, and a specific test strategy to validate the fix.

Can I use a structured SDLC workflow for both frontend and backend corrections?▼

A structured SDLC workflow applies to bug corrections and feature changes across frontend, backend, and documentation. It guides phase validation, issue elicitation, and execution planning regardless of the affected technical layer.

Why should I elicit issue context before starting a code review or fix?▼

Eliciting issue context before a code review clarifies the problem scope and environment constraints. This process surfaces design tensions early, ensuring the subsequent execution plan and test strategy align with actual requirements.

What are the limitations of fixing software bugs without design alignment?▼

Fixing bugs without design alignment risks introducing gaps between code and documented requirements. Skipping context gathering and phase validation ignores environment constraints, leading to untraceable execution plans and unresolved tensions.

Related Skills

Explore More Software Engineering Skills→
RoxabiRoxabi
9

frame

Captures core issues, affected users, constraints and scope into a draft document file with tier detection.

Official
Advanced
dfrysingerdfrysinger
36

test

Run acceptance tests against implemented code and present pass/fail results.

Community
Advanced
dhaneshdhanesh
8

manifold-m2-tension

Surface and resolve constraint conflicts between competing requirements in workflows.

Community
Advanced
mxnyawimxnyawi

architect

Design and govern software system architectures across multi-project environments.

Community
Advanced