Menü
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-review-local-changes, merge back, full suite once at the end.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | nv-implement |
| description | Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-review-local-changes, merge back, full suite once at the end. |
| disable-model-invocation | true |
Implement the work described (plan file, spec, or ticket) as vertical slices, one subagent per slice, each on its own worktree. Use /tdd where possible, at pre-agreed seams. Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Invoking this skill authorizes the commits it produces (slice commits, review refactor commits, merge commits, and integration fixes).
- [ ] 1. Cut the work into seams
- [ ] 2. Resolve feature branch + one worktree per seam
- [ ] 3. Fan out subagents (TDD → commit → /nv-review-local-changes)
- [ ] 4. Merge slices back into the feature branch
- [ ] 5. Integration pass (typecheck + cross-slice fallout)
- [ ] 6. Full suite once + teardown
Split the plan into slices that touch disjoint files — each slice independently committable and testable. Typical Novu cuts: policy/backend logic, create-path + migration, copy/DTO/docs, dashboard UI.
For each seam decide upfront: is it TDD-able (public function, use case, resolver → yes) or verify-by-lint (dashboard UI with no unit harness → no)? Tell the subagent which.
Done when: every plan item is owned by exactly one seam, and no two seams edit the same file. If two seams must touch the same file, merge them into one slice — do not parallelize a conflict.
Detect the integration target first (git branch --show-current):
next / main / master): treat the current branch as <feature-branch>. Do not create a new branch from origin/next. Slice worktrees branch from this HEAD; all merges go back here.next / main / master (or detached): create a new feature branch from origin/next, then proceed.git fetch origin next
# only when starting fresh from next/main/master:
git checkout -b <feature-branch> origin/next
# always — slice branches from current feature-branch HEAD:
git worktree add -b <feature-branch>-<seam> ../wt-<seam> HEAD
Symlink dependencies into each worktree (no install needed):
ln -s <main-checkout>/node_modules ../wt-<seam>/node_modules
Done when: <feature-branch> is set (existing or newly created), and git worktree list shows one worktree per seam, all at that feature branch HEAD.
Launch all slice subagents in one message (parallel Task calls, run_in_background: true). Each prompt must carry full context — subagents see nothing of this conversation. Include:
/tdd instruction for TDD-able seams: vertical slices, one behavior at a time, with the prioritized behavior listtype(scope): why, then run /nv-review-local-changes from the worktreeDone when: every subagent reports commits + test results + review triage. Read each summary; a subagent that skipped review or left tests red gets resumed, not merged.
From the main checkout, on <feature-branch> (the same branch resolved in step 2 — never merge slices into next directly):
git merge --no-ff <feature-branch>-<seam> -m "merge: <slice summary>"
Merge in dependency order (backend policy before tests that rely on it). Then remove worktrees and delete slice branches.
Done when: all slice branches merged into <feature-branch>, git worktree list shows only the main checkout, slice branches deleted.
Slices were reviewed in isolation — the seams between them were not. Expect cross-slice fallout: one slice changed copy while another slice's spec asserts the old string; one slice widened a type another slice consumes.
pnpm exec nest build in apps/api; ReadLints on dashboard filesDone when: typecheck is clean and all touched spec files pass in one run.
Run the full relevant suite once (e.g. all src/app/agents/**/*.spec.ts). Report genuinely-related failures fixed; unrelated environmental failures named as such — not silently ignored, not chased.
Done when: suite result reported with pass/fail counts and any unrelated failures explained.
# API typecheck (catches what TS_NODE_TRANSPILE_ONLY hides)
cd apps/api && pnpm exec nest build
# Single spec file(s) — mocha, from apps/api
TS_NODE_PROJECT=tsconfig.spec.json TS_NODE_TRANSPILE_ONLY=true NODE_ENV=test \
NOVU_ENTERPRISE=true CLERK_ENABLED=true NEW_RELIC_ENABLED=false \
NODE_OPTIONS=--no-experimental-strip-types \
npx mocha --timeout 15000 --require ts-node/register --exit --no-config 'src/path/to/file.spec.ts'
Dashboard has no unit harness for most components — verify via ReadLints; do not invent a test harness.
origin/next or merge slices into next./nv-review-local-changes); never amend or squash them during merge./novu-prepare-pr when implementation is done./tdd — the red-green loop each TDD-able slice runs/nv-review-local-changes — each slice's closing reviewBuild or refactor a Tool-channel provider (PagerDuty, Opsgenie, future incident/alerting tools) to be endpoint-routed: per-subscriber secrets encrypted on the channel endpoint resource, a stateless provider that resolves routing from channelData at send time, SKIPPED steps when no endpoint exists, and the full API/worker/dashboard/docs/playground surface. Starts with a mandatory provider-docs discovery gate. Use when refactoring Opsgenie to the PagerDuty model, adding a new tool provider, or touching pagerduty_service channel endpoints.
Post-implementation PR prep for Novu feature branches — quality passes, commit/PR hygiene, CI triage, and review feedback. Use after feature work is done, when the user asks to prepare a PR, ship a branch, fix CI, address review comments, or babysit a pull request before merge.
Create and publish Novu changelog entries in Sanity (changelogPost documents), including feature posts, "improvements & fixes" roundups built from Linear releases, and the Changes (changeBlock) component. Use when asked to write a changelog entry, announce a shipped feature on the changelog, roll up improvements/bug fixes since the last release, or work with Sanity changelog content for the Novu website.
Commit local changes as a baseline, hop into a lightweight review worktree, run a thermo-nuclear code quality review scoped to ONLY that commit, commit the resulting refactor as a separate follow-up commit, then land it back and tear the worktree down. Use when the user asks to review their local/uncommitted changes for AI slop and redundant code, or invokes nv-review-local-changes.
Build a new channel Connect button (e.g. WhatsApp, Discord, LINE) in @novu/js and @novu/react following the existing SlackConnectButton, MsTeamsConnectButton, and TelegramConnectButton pattern. Use when adding connect/disconnect UI for a new chat channel/provider to the SDK — covering the SolidJS core component, the React wrapper, the channelConnections (OAuth) vs channelEndpoints (deep-link) data layer, the component registry, and package exports.
Add a new chat channel's layer-1 setup guide — the in-dashboard <Channel>SetupGuide that walks a developer through connecting the channel itself (create app/bot → save credentials → install/verify → send first message) with live connection detection — in apps/dashboard, following the existing Slack, MS Teams, and Telegram guides. Use when a new agent channel needs its numbered setup stepper, credential drawer wiring, and connectedAt polling under components/agents.