Implementation-conformance gate. Runs only for an epic entry; a fix or an intake entry has no acceptance criteria, no success metrics and no decision record to check against, so the gate stops rather than degrading into a pass. Checks the implemented code against the epic's acceptance criteria, success metrics, and…
Relay to nexus close, the plain command that closes an epic over its merged pull requests. Runs only when its arguments name the epic — --epic , a bare , or --pr , which close resolves to its epic; otherwise it refuses at once and names nexus close --epic . Given one, it runs nexus close with the same arguments, shows…
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, approval contract first: how the design works in the epic's own words, an approval brief of what needs a decision and what each choice costs, the guarantees the build must keep, and the risks, with each decision's reason and refuted alternative in an appendix.…
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…
Move the closed 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…
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 is required. Oversized scope decomposes to epic 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.
The lightweight lane. Records why a small change that has already landed mattered, by creating a drainable fix entry under the gitignored .nexus/tmp/ — one GitHub reference in, two files out. Writes nothing to GitHub, cuts no branch, opens no pull request and commits nothing; /nxs.distill drains the entry later, under…
Record a design change that already landed, whose reasoning lives in its merged pull request. One reference in; a drafted close record read from the pull request's body, review threads and commit messages; one approval gate; a drainable intake entry out. Writes nothing to GitHub before approval, cuts no branch, opens…
★not rated 10
changed 4d agoA105 tokens
GPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: