nadavushka-dev/nadavushka-plugs

处理问题追踪系统中的工单（例如 RND-123）：Bug → 复现失败场景并做最小修复；功能 → 按 PRD 实现。可独立使用，也可作为 autonomous-squad 的第三步。

nadavushka-plugs 是什么？

该技能用于高效处理问题追踪系统中的工单，支持 Bug 修复和功能实现两种场景。对于 Bug，首先复现问题并捕获失败证据（如测试结果、curl 输出、数据库查询等），然后进行最小化的代码改动来修复；若无法在任何介质上捕获失败，则标记为“qa clar”。对于功能需求，严格遵循 PRD 文档，遇到歧义或与现有功能冲突时，在评论中标记并进入“prod clar”状态。在提交前，会启动一个全新的子智能体进行对抗性审查，强制尝试找出变更中的问题（区分阻塞性和非阻塞性），并要求针对阻塞性问题提供证据而非争辩，若两轮后仍有未解决的阻塞问题，则标记为“dev clar”。该技能可独立运行，也可作为 autonomous-squad 流程的第三步，自动化程度高，适合需要严谨代码质量控制的开发环境。

兼容平台✓Claude Code~Codex CLI~Cursor

npx skills add https://github.com/nadavushka-dev/nadavushka-plugs/tree/HEAD/squad/skills/tkt-work

文档

User input: $ARGUMENTS

Config

Before anything else: read ${CLAUDE_SKILL_DIR}/../squad-config.md

Before you start

No tkt context in this conversation → invoke the squad:tkt-context skill with the ticket key first
No worktree for this tkt → create it (see Rules)

Bug?

Reproduce → red

Reproduce the bug and capture the red artifact in the bug's medium (see the squad:tkt-evidence skill). Not screenshot-able is never a reason to stop — switch medium (test / curl / db shell / log). No red artifact in any medium → qa clar.

Solve

Minimal changes to fix the bug

Feature?

The PRD must be followed
Ambiguous, contradicts or conflicts with existing features → flag it in a comment, move to prod clar

Adversarial review (before green / `squad:tkt-evidence`)

Spawn a fresh subagent (not a fork). Give it: tkt key, diff, red artifact (bug) or PRD (feature). Its job is to break the change, not approve it. Each finding is labeled blocking or nit.

Bug: does the red reproduce the reported bug? Root cause or symptom? Minimal? Regressions nearby?
Feature: every PRD point covered and tested? Anything beyond the PRD? Conflicts with existing behavior? Blocking → fix → re-review. Dismiss a blocking finding only with evidence, not argument. Still blocking after 2 rounds → dev clar with the open question. Nits → fix or list in the PR.