# Workflow Bug

> Workflow Bug

- Skill: `mikhailkogan17/workflow-bug` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mikhailkogan17/workflow-bug`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mikhailkogan17/workflow-bug/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mikhailkogan17 (https://skillmd.com/u/mikhailkogan17)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mikhailkogan17/workflow-bug

---


# /workflow-bug — an alias for `/workflow-feature`, entered in fix mode

**This skill is not a second workflow.** It runs `/workflow-feature` end to end. It exists so that a
`Bug` label has a route of its own on the board, and so the run starts already knowing which mode it
is in.

## What to do

1. **Post the start comment first** — before anything else, exactly as `/workflow-feature` step 3
   does. A dispatched run that posts nothing is declared dead by the poller and re-dispatched, and
   the alias must not be the reason that happens:

```bash
"${CLAUDE_PLUGIN_ROOT}/poller/lin" issue comment list <KEY> | grep -q 'harness:<KEY>:dispatched' \
  || "${CLAUDE_PLUGIN_ROOT}/poller/lin" issue comment add <KEY> --body '<!-- harness:<KEY>:dispatched -->
Harness run started (fix mode) — contract → failing test → fix → audit → gate → PR → review. Next comment lands when the PR opens.'
```

2. **READ `${CLAUDE_PLUGIN_ROOT}/skills/workflow-feature/SKILL.md` and follow it from step 1**, with
   the same inputs you were given. Skip its step 3 — you have already posted the marker.
3. **Read `${CLAUDE_PLUGIN_ROOT}/harness/modes/fix.md`** and work in that mode. The contract's
   acceptance check is a test that **fails on the current code and passes after the fix**. A fix
   whose regression test passes before the change has not been shown to fix anything.

## Why an alias and not a workflow

The two would be the same file. Copying `workflow-feature` here to have a `Bug` route would mean
every later change to the lifecycle has to land in two places, and the copy that gets missed is the
one nobody runs interactively — it would drift silently and be found by a user. Routing is what
wanted to distinguish bugs, and routing is where the distinction lives: the label picks this skill,
this skill picks the mode.

If a bug ever needs a genuinely different lifecycle — a reproduction stage before contracting, say —
this is the file that grows it, and no route has to be renamed for that to happen.