Menú
Use when fixing a bug in a production project. Full cycle: diagnose, fix, regression test, review, docs.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Full-cycle bug fix: diagnose → fix → test → review → merge → update docs. Orchestrates superpowers skills in the right order with project-specific reminders.
Type: Architect
Apply the verify-working-directory contract from <plugin>/skills/_shared/references/verify-pwd.md: confirms CLAUDE.md exists, derives the canonical MemPalace wing name, warns on stale-wing duplicates, and establishes the mandatory path-validation rule for the rest of this skill's MemPalace reads.
Read these files before anything else (independent reads — fetch them in one parallel batch). For subagent dispatch, model tiers, and parallelism-safety rules used throughout this skill, see _shared/references/orchestration-conventions.md.
CLAUDE.mddocs/architecture/system.mddocs/architecture/api.md (if exists)docs/product/user-stories.mddocs/plans/tasks.mdAsk the user to describe the bug. Accept:
Invoke superpowers:using-git-worktrees to create an isolated branch for the fix. Branch name: fix/<short-bug-description>.
Invoke superpowers:systematic-debugging skill. Follow it exactly — it will:
Respect the Blast Radius Rule (see ~/.claude/CLAUDE.md): the fix must be the smallest justified change that addresses the root cause. If a larger restructuring would genuinely be better, STOP and ask the user before expanding scope — don't silently refactor.
Invoke superpowers:test-driven-development skill:
git diff --stat — confirm the change footprint matches the declared scopebash <plugin>/scripts/quality-gate.sh --pwd . --test-cmd "<project test command>" (add --base <ref> if the fix spans commits). Fix and re-run until it exits 0 — do not proceed to review with a red gate.Invoke superpowers:requesting-code-review to verify:
If feedback is received, invoke superpowers:receiving-code-review to process it with technical rigor — verify before implementing suggestions.
Invoke superpowers:finishing-a-development-branch — it will guide merge, PR, or cleanup.
After merge:
docs/product/user-stories.md — add note about the fix or update affected story statusdocs/testing/manual-qa.md — add regression check for this bugdocs/plans/tasks.md — mark bug task as done (if it was tracked)Print architect report:
✓ Architect report:
- Bug: <description>
- Root cause: <what was wrong>
- Fix: <what was changed>
- Regression test: <test file and test name>
- Merged to: <branch>
Updated:
- docs/product/user-stories.md
- docs/testing/manual-qa.md
- docs/plans/tasks.md
Do NOT add translations — wait for pre-release-check phase.
Next steps:
- /vladyslav:write-test-docs — update test documentation for the fix
- /vladyslav:pre-release-check — run pre-release verification before shipping
Use when adding a feature to a production project. Full cycle: brainstorm, plan, implement, docs.
Use to batch-validate all skills in this plugin. Runs deterministic repo-wide static checks (frontmatter, command delegation, cross-references, Architect model= rule, orphan references, README<->MemPalace sync) and reports pass/fail per skill.
Use when creating a new project. Bare AI shell by default; interactive menu adds docs / backend-infra / agents on demand.
Use after init-project to fill docs/product/start-project.md with AI research on competitors, monetization, valuation, and marketing.
Use when unsure which skill to use. Lists all vladyslav skills, workflow, and integration.
Quick-save the latest decision/problem/milestone to MemPalace with zero questions — derives everything from the current conversation. Use for a fast mid-session capture, or accept it when offered at task completion.