nadavushka-dev/nadavushka-plugs

Work an issue-tracker ticket (e.g. RND-123): bug → reproduce red, then minimal fix; feature → implement per PRD. Use standalone or as step 3 of autonomous-squad.

What is nadavushka-plugs?

nadavushka-plugs is a Claude Code agent skill that work an issue-tracker ticket (e.g. RND-123): bug → reproduce red, then minimal fix; feature → implement per PRD. Use standalone or as step 3 of autonomous-squad.

Works with✓Claude Code~Codex CLI~Cursor

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

Documentation

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.