Implements planned work via parallel subagents on isolated git worktrees with TDD and staged merges.
npx skills add https://github.com/novuhq/novu --skill nv-implement
Please help me install this Agent Skill. Skill: nv-implement Source: https://github.com/novuhq/novu/tree/main/.cursor/skills/nv-implement Command: npx skills add https://github.com/novuhq/novu --skill nv-implement
Large implementation tasks in the Novu monorepo are slow and error-prone when done serially in a single checkout, and parallel edits often collide on the same files. This Skill coordinates the whole implementation: it cuts a plan into disjoint vertical slices, runs one subagent per slice on its own git worktree, and merges everything back with a single integration pass.
Ask the agent to implement the current plan or ticket using nv-implement, splitting the work into parallel slices on separate worktrees.
High-intent search queries and answers about installing and using this skill.
Cut the plan into vertical slices that touch disjoint files, then launch one subagent per slice on its own git worktree in a single parallel batch. Each subagent implements, tests, commits, and reviews its slice before the slices are merged back into the feature branch in dependency order.
Create one worktree per slice with git worktree add -b <feature-branch>-<seam> ../wt-<seam> HEAD, and symlink node_modules into each worktree to avoid reinstalling. Each agent works only inside its own worktree so sibling slices never corrupt each other.
Slices with public functions, use cases, or resolvers are TDD-able and should follow a red-green loop one behavior at a time. Dashboard UI slices without a unit test harness are verified via lint checks instead, since inventing a test harness is out of scope.
The two slices are merged into a single slice rather than parallelized, because concurrent edits to the same file guarantee a conflict. The seam-cutting step is done when every plan item is owned by exactly one seam with no shared files.
Slices run typechecks and individual spec files regularly during development, which catches most issues cheaply. The full suite runs once after merging and the integration pass, since cross-slice fallout is only visible on the combined diff and repeated full runs are slow.
No. Slices always merge into the feature branch, either the existing one detected at startup or a new one created from origin/next. Merging slices directly into next is explicitly prohibited by the guardrails.
loianePlan Epic-level architecture and vertical-slice roadmaps for large features.
bradtaylorsfSynchronizes Linear ticket statuses with Git workflow events via API and gh CLI.
alasdairncDecomposes feature specs into slices with tests and parallel subagents.
aslaiiExecute trivial tasks directly without spawning subagents or creating PLAN.md files.
