메뉴
Small bug-fix lane with bounded diagnosis, agent-owned verification, and escalation. Use when the user reports a bug, failing test, broken behavior, or asks for a narrow fix that should not require a full brainstorm or plan unless it grows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | kb-fix |
| description | Small bug-fix lane with bounded diagnosis, agent-owned verification, and escalation. Use when the user reports a bug, failing test, broken behavior, or asks for a narrow fix that should not require a full brainstorm or plan unless it grows. |
| argument-hint | [bug description, failing command, or issue path] |
Fix narrowly, verify yourself, and escalate when the bug is not actually small.
todo.md, docs/context/PROJECT.md, and relevant handoff/subsystem docs.docs/context/research/ and docs/solutions/ for related failures.todo.md, handoff files if needed, and learning docs when the fix teaches something reusable.kb-map refresh when the fix changes behavior, architecture, run/test commands, integrations, sharp edges, or "do not repeat" knowledge. Skip with a note when the fix is cosmetic or isolated.Do not tell the user to test normal app behavior if the agent can test it.
The micro-plan is not a kb-plan manifest. Escalate to kb-plan only when the
bug becomes multi-slice, crosses several owning surfaces, or needs dependency
ordering. For a narrow fix, the micro-plan exists to freeze the failing signal
and verification target before the code changes.
Default ceiling:
Progress can extend the ceiling. Progress means the failure narrows, reproduction improves, evidence points to a subsystem, or one verification layer now passes.
No progress means the same failure persists after unrelated edits, hypotheses change without evidence, or the next attempt cannot say what it proves.
Escalate to:
kb-research when external/framework behavior is unclear.kb-brainstorm when product behavior or scope is unclear.kb-plan when the fix becomes multi-slice.kb-map refresh when architecture docs changed.When stuck, produce:
## Bug Escalation Report
### Symptom
### Expected Behavior
### Reproduction
### Attempts
| Attempt | Hypothesis | Change/Test | Result |
|---|---|---|---|
### Evidence
### Current Best Theory
### Why I Am Stuck
### Recommended Route
Park only the blocked slice or handoff; continue unrelated runnable work when possible.
Inspect live routes and manage optional user-local OpenAI-compatible/LiteLLM extra routes through the kbrouter CLI.
Single user-facing KB completion command. Takes a feature, plan, or manifest from its current state through planning, work, post-work finalization, and configured delivery: local completion, pushed PR, or explicitly configured direct integration and sync.
Configure optional portable per-project lower-tier-attempt and delivery policy.
Large-initiative coordinator for KB workflows. Use for app migrations, framework rewrites, major architecture changes, multi-subsystem initiatives, multiple brainstorms/manifests, long backlogs, or queued execution across related workstreams.
Internal post-work quality and learning phase. Runs kb-review -> resolution gate -> follow-up resolution -> proof/demo evidence -> compound -> learn -> evolve -> memory refresh/compact -> cleanup after kb-work finishes all slices. Normally invoked by kb-work or kb-complete; not the primary user-facing completion command.
Deprecated compatibility alias for kb-complete. Use when an older prompt or workflow says 'kb finish'; delegate the same input to kb-complete and report the kb-complete result.