papi-sdlc-fix

Create defect fix tasks with evidence capture and root-cause analysis.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/stainsby/papi --skill papi-sdlc-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: papi-sdlc-fix
Source: https://github.com/stainsby/papi/tree/main/skills/papi-sdlc-fix
Command: npx skills add https://github.com/stainsby/papi --skill papi-sdlc-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill provides a structured approach to defect management by guiding evidence capture, root-cause analysis, task planning, and synchronized artefact updates across specifications, code, tests, and documentation.

Core Features & Use Cases

  • Evidence-first: capture exact observed behaviour before planning fixes to enable verifiable conclusions.
  • Root-cause and improvement emphasis: document root causes and targeted improvements beyond a patch.
  • SDLC alignment: ensure changes are consistently reflected in specs, code, tests, and documentation across tasks.
  • Use Case: when a defect is detected, generate a complete fix task using the fix-task template to drive resolution.

Quick Start

Create a complete defect fix task by capturing evidence, identifying root cause, and outlining goals using the fix-task template.

Frequently Asked Questions about papi-sdlc-fix

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

FAQPage Schema
How do I plan and execute a defect fix across code, specs, and documentation?

Apply a structured defect fix task template that requires capturing exact observed evidence, documenting root causes, and enforcing synchronized updates across code, specifications, tests, and documentation.

What is evidence capture in root-cause analysis for software defects?

Evidence capture in root-cause analysis records exact observed behaviour before planning fixes, enabling verifiable conclusions and targeted improvements beyond a simple patch.

Can I use a structured fix-task template for non-code issues like tooling and process defects?

Yes, the structured fix-task template handles defects across code, specifications, documentation, tooling, and processes, guiding evidence capture and root-cause analysis for any SDLC workflow.

What's the best way to ensure documentation and specs stay aligned during a code fix?

The best way to ensure alignment is to enforce SDLC synchronization, which requires explicit updates to specifications, code, tests, and documentation as part of the defect fix task.

Do I need to document root causes for every defect fix task?

Yes, documenting root causes is required for every defect fix task to ensure targeted improvements beyond the immediate patch and maintain verifiable resolution within the SDLC workflow.

When do I need a structured defect fix task in the SDLC?

You need a structured defect fix task when a defect is detected and requires a complete resolution process, driving the workflow from evidence capture through to synchronized artefact updates.