skills.rest
maksutovic
maksutovicCOMMUNITY
Explore all skills by this author →
Website𝕏@max_maksutovicGitHub

joycraft-bugfix

Triage bugs and guide teams through diagnosis, discussion, and specification before implementation.

14|1|Updated Mar 23, 2026
Search Tags:#workflow#handoff#spec#diagnose#triage#bugfix
One-click install
npx skills add https://github.com/maksutovic/joycraft --skill joycraft-bugfix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: joycraft-bugfix
Source: https://github.com/maksutovic/joycraft/tree/main/.agents/skills/joycraft-bugfix
Command: npx skills add https://github.com/maksutovic/joycraft --skill joycraft-bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Bug Fix Workflow provides a repeatable, user-guided process to triage, diagnose, discuss with the user, and write focused specs before handing off to implementation, reducing drift and rework.

Core Features & Use Cases

  • Phase-driven workflow: Triage, Diagnose, Discuss, Spec, Hand Off
  • User-facing collaboration: ensures validation before coding and minimizes back-and-forth
  • Documentation-driven: creates a bug-fix spec and traceability for future audits

Quick Start

Describe the bug and begin Phase 1: Triage to start the workflow.

Frequently Asked Questions about joycraft-bugfix

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

FAQPage Schema
What is a spec-driven bugfix workflow and when do I need it?▼

A spec-driven bugfix workflow guides teams through triage, diagnosis, discussion, and specification before implementation. You need it for collaborative software projects to reduce drift and rework by enforcing validation before coding begins.

How do I triage bugs and write a bugfix spec before implementation?▼

To triage bugs and write a bugfix spec, follow a phase-driven workflow: collect symptoms, perform root cause analysis, discuss with the user, and write a formal specification with acceptance criteria and a reproducible test plan before handing off.

Can I use this bugfix workflow for collaborative projects spanning multiple files and services?▼

Yes, this bugfix workflow applies to collaborative software projects of any size, handling symptom collection, root cause analysis, and proposed fixes across multiple files and services safely and verifiably.

What's the best way to ensure bug fixes are safe and verifiable across a team?▼

The best way to ensure bug fixes are safe and verifiable is to enforce a formal bugfix spec, acceptance criteria, and a reproducible test plan, minimizing back-and-forth through user-facing collaboration and validation before coding.

Why does my team experience drift and rework during bug fixes?▼

Teams experience drift and rework during bug fixes when skipping diagnosis and specification phases, jumping straight to implementation without a formal bugfix spec, acceptance criteria, and user-facing validation to ensure aligned understanding.

Related Skills

Explore More Software Engineering Skills→
tropekstropeks

investigate

Guide engineers through structured four-phase root-cause debugging from symptoms to verification.

Community
Advanced
opsMachineopsMachine
1

plan-tests

Generate a structured Test Plan from an approved spec by mapping acceptance criteria to test types.

Official
Intermediate
dangelesdangeles
6

completion-verifier

Verify task completion against acceptance criteria and generate a verification report.

Community
Advanced
OliverOuyangOliverOuyang
1

ultraqa

Automate iterative QA cycles to detect, diagnose, and fix failing tests and build issues.

Community
Advanced