Implementation-conformance gate. Checks the implemented code against the epic's acceptance criteria, success metrics, and the decision record's invariants — does the build do what the planning said. Refuses to run while the epic's decision-record sub-issue is unapproved, and stamps which record it checked against.…
Close an epic. Emits a human-prose close record beside the resolved epic.md — under the gitignored .nexus/tmp/ for an issue-sourced local close, in the committed entry for an old-contract one — (key decisions + deferred-scope pointer + deviation rationale from a close-from-diff pass), files deferred scope as backlog…
Product council facilitator that synthesizes PM and Architecture perspectives into actionable recommendations. Invoke for feature decisions, build-vs-buy evaluations, scope trade-offs, or when you need balanced product/technical analysis.
Add the architectural decision record to a planned epic — the focused "why" (key decisions + refuted alternatives, invariants, risks), tiered by complexity. Reads the epic and its stories; files the record as a sub-issue of the epic issue (its durable home) and moves the epic from needs-design to in-progress, with…
Run pre-epic discovery on a foggy initiative as a multi-session loop over a committed store. Starts a discovery by naming its destination and writing one decision ticket per open decision, resumes it one decision at a time, and closes it when the resolutions conclude that no build follows. Writes nothing to GitHub — a…
Drain the queue — committed entries and same-sitting ephemeral .nexus/tmp entries alike — into the concept store via a reviewed distillation-PR. Reads each closed queue entry (epic + close record) plus the epic's decision record — fetched from its record sub-issue and verified against the hash stamped at close — plus…
Turn a natural-language capability description into a right-sized epic with user stories and acceptance criteria, then — on approval at a decision-grade digest — file the epic and one GitHub issue per story together. Takes intent directly — no feature brief required. Oversized scope decomposes to backlog stub issues…
One-time project bootstrap. Auto-detects the stack, generates system docs/standards, scaffolds the Nexus surfaces, then runs an interactive interview (via the nxs-setup skill) to build the product context. Replaces the old nxs.init + nxs.product-context.
Fetch a GitHub issue and implement it via the nxs-dev agent. Posts implementation summary and closes issue on success. Supports --yolo flag for auto-approval mode.
Generate a High Level Design Document from an epic specification. Invoke for: new feature epics, major refactoring initiatives, system integrations, or any work requiring architectural planning before implementation.
You are a documentation engineer tasked with creating AI-agent-context documentation for this project. Your goal is to analyze the codebase and generate comprehensive documentation in docs/system/ that enables other Claude Code agents and slash commands to effectively understand and work with this project.
Interactively build your product context file (docs/product/context.md) through a guided conversation. Asks at most 5 strategic questions, then uses PM expertise to infer the rest.
Three-phase QA workflow via single command and mode flag. Run after nxs.tasks (design), after nxs.dev (implement), or to perform comprehensive QA verification.