nxf-workflow

A Claude Code plugin that bundles the nexus-flow development-loop skills: plan the next task → do the work → review the PR → mitigate the findings → report to the PM.

The review skills are stack-agnostic — they work in Node, React, Rust, Python, Go, or any other codebase by discovering the project's own quality gates and conventions rather than assuming a language. The planning and reporting skills use nexus-flow (nxf) as the issue tracker.

Skills

• pm-next-task — Turn the last PM session report plus the current nexus-flow board into one well-scoped, self-contained task brief for a fresh coding assistant — what was last achieved, the task, and why this one over the alternatives. Writes it as a dated Markdown file into the target repo's .nxf/next-task/ folder (derived from the report's path) and replies with a two-line pointer — built for a central coordinator session planning work across several repos.
• pm-session-report — Write a concise, PM-readable session summary: what landed, what went sideways, what to do next (tracked or not), and how to verify it. Saves it as a dated Markdown file in this repo's .nxf/session-report/ folder and replies with a two-line pointer, so the path can be handed to a coordinator session to plan the next task.
• review-pr — Run three parallel reviews (code quality, test quality, integrity & robustness) against your local changes or branch diff, using the project's own quality gates as a baseline signal. Always shown in chat; when a tracked work order resolves, also saves the report to a dated file under .nxf/review/ and records its path in the status log, so it can be picked up later without pasting it.
• mitigate-pr-review-findings — Work through a review report finding by finding: fix it in the code, or record a grounded reason for leaving it. Two ways to invoke: /mitigate-pr-review-findings <pasted report>, or just say "mitigate the PR review findings" with nothing pasted — it then finds the latest completed review for this repo's active work order via the status log. Logs the outcome and closes by recommending what to do next.
• pm-work-status — Shared, mostly-invisible utility the other skills call into: appends one JSON line per phase change (task received, PR opened/ merged, review requested/completed, findings mitigated, released — with version and beta/stable channel, PM report filed) to this repo's .nxf/status.jsonl, an append-only work-order status log.
• pm-project-status — Coordinator-side "what's going on where": reads the tracked-repos registry plus every tracked repo's .nxf/status.jsonl and renders one concise cross-repo status summary in the chat. Use when asking about the state of the projects worked on recently. Also runnable manually via /pm-project-status.
• pm-cycle-status — Where does this repo stand in the loop? Reads only the presence and filesystem timestamps of .nxf/next-task/, .nxf/review/ and .nxf/session-report/ and answers in two to four lines whether the newest task brief has already been reviewed and reported — in the language the question was asked in, with local times (the filenames mix local time and UTC, so the filesystem timestamp is the authority). No file written, no report contents, this repo only. Also runnable manually via /pm-cycle-status.
• session-handover — When you wrap up a session, write a short handover note to .nxf/session-handover.md. A bundled SessionStart hook loads that note into the next session's context and then clears it, so work resumes exactly where it left off. Self-contained — no other plugin required.
• remote-control-session — Start a new clauded (claude --dangerously-skip-permissions --remote-control <name>) session in its own Terminal window so it shows up, controllable, in the Claude iOS app. Avoids the macOS Automation permission wall by launching an executable .command file via open instead of driving Terminal with osascript. Optionally resumes an existing session with history via --resume <id> --fork-session, and can hand the new session a first task as its opening prompt. Marks the project folder as trusted in ~/.claude.json first (an unwatched trust dialog would hold the session), and strips the launching session's Claude Code markers from the new window's environment so the new session is not taken for a child — which would save no transcript and write no session record. Verifies the Remote Control bridge came up (bridgeSessionId in ~/.claude/sessions/<pid>.json) instead of assuming it. macOS only.

The .nxf/ folder

Every skill in this plugin reads/writes under a project-root .nxf/ folder, kept out of version control (a .gitignore with * is created on first use — by the SessionStart hook for .nxf/session-handover.md, and by the writing skill itself for everything else, since that skill may be running in a different repo than the one whose session started it):

• .nxf/session-handover.md — this session's handover note (session-local, consumed on next start).
• .nxf/session-report/*.md — dated PM session reports (pm-session-report), meant to be copied into a coordinator session.
• .nxf/next-task/*.md — dated task briefs (pm-next-task), written into the target repo the task belongs to, meant to be copied into a fresh session there.
• .nxf/review/*.md — dated PR review reports (review-pr), written only when a tracked work order resolves; its path is recorded in the status log so mitigate-pr-review-findings can find it without a paste.
• .nxf/status.jsonl — the append-only work-order status log for this repo (pm-work-status), one JSON line per phase change.
• .nxf/tracked-repos.jsonl — coordinator-only: every target repo pm-next-task has ever dispatched a brief to, so pm-project-status knows where to look.

SessionStart hook

The plugin ships one hook (hooks/session-start.sh, registered via hooks/hooks.json). At the start of every session it prints any pending .nxf/session-handover.md into context and blanks the file. .nxf/ is kept out of version control automatically (a .gitignore with * is created on first run); handover notes are session-local.

Install

/plugin marketplace add nxsflow/plugin-marketplace
/plugin install nxf-workflow@nxsflow

Requirements

The planning/reporting skills and the issue-filing steps use the nexus-flow CLI (nxf). Run nxf prime inside a workspace to bootstrap it and see the current board.