Technical architecture expert for system design, scalability, and implementation feasibility. Invoke for: technical feasibility assessment, comparing implementation approaches, architecture reviews, performance/security deep-dives, or evaluating scope changes from a technical perspective.
Epic-level planning gate. Checks one epic.md for acceptance-criteria quality by storytype and internal consistency, before its story issues are filed. Invoke from /nxs.epic (at the approval gate) or standalone against any epic.md. Returns inline findings; makes no edits and files no issues.
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.
Rebuild a planned epic from its GitHub issue number — the epic body, its story sub-issues, and the native blockedby graph — into a deterministic, gitignored epic.md. The single producer of the materialized epic every downstream stage reads when nothing was committed at planning.
Create a GitHub issue from an Epic document. Use when the user wants to create a GitHub issue from an epic.md file, sync an epic to GitHub, or link an epic document to a GitHub issue. The skill extracts the epic title and type from YAML frontmatter, creates an issue via gh issue create, and updates the frontmatter…
Create GitHub issues from STORY-.md work-item files. Use to bulk-create one issue per user story from markdown files whose frontmatter carries title, labels, parent (epic), and project. Extracts frontmatter, creates issues via gh CLI, links each as a sub-issue of the parent epic, and adds them to a project.
Resolve a PR's merge state and SHAs and manage the git worktree for the --pr flow of /nxs.analyze (before the merge) and /nxs.close (after it). Single-repo and hub only; rejects member repos.
Compute the canonical digest of an epic's decision-record sub-issue — the one implementation every stage that stamps or verifies the record hash invokes. Fetches the record body from GitHub, applies the stated canonicalisation rule, and prints the full hexadecimal digest plus the record's approval state. Use from…
Interactive product-context interview. Asks at most 5 strategic questions one at a time, applies PM pattern-recognition to infer the rest, and writes the product context under the resolved docs root (docs/product/context.md in a single-repo checkout). Invoked by /nxs.setup during project bootstrap, or run standalone…
Print the workspace status read-out — the hub, each declared member, and each member's checkout state — resolved from the current checkout. Use to verify a new or changed multi-repo workspace before a downstream stage depends on it, or to confirm a repo is in single-repo mode.
Senior implementation engineer for hands-on software development. Invoke for: implementing features from designs/issues, writing tests, building out specified functionality, or making code changes with clear requirements. Writes tests first, consults standards, and executes in logical chunks with human checkpoints.
★not rated 10 3d agoA0 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: