What is NexusArchitect
An overview of what NexusArchitect, a tool that runs on Claude Code, does for you
NexusArchitect is a development-assistance tool that runs on Claude Code. It connects everything from product planning through code implementation, review, and merge into a single continuous flow (pipeline).
Internally it is divided into four components (sub-plugins).
product
The part that determines product direction. Proceeds in sequence through Vision (what to aim for) → Scope (what to build) → Personas → User flows → Screen mockups → Feature definitions → Data model → Domain organization → API design → NFRs (non-functional quality requirements such as performance) → Architecture
architect
The part that drives design, implementation, review, and merge. Handles both greenfield development and legacy system modification, covering task management, code generation, review, and merge
scalardb
The part that is only involved when ScalarDB/ScalarDL is used as the database. Handles data design, code generation, and consultation when issues arise
infra
The part that is only involved when a cloud platform (Terraform/Kubernetes/CI) is used. Assumes a multi-cloud setup and handles platform design, implementation into the actual infrastructure repository, and review
The product and architect components are connected through the reports/ folder, and scalardb/infra are components that branch off from it conditionally.
Design Philosophy
NexusArchitect is built around three core principles.
Make the reports folder the single source of truth
The output of each task is organized into numbered folders such as reports/00_core/, reports/01_ux/, reports/02_spec/,
reports/03_domain/, and reports/04_quality/. All subsequent tasks always read from this reports/ folder before proceeding, so information never falls out of sync.
Connect every phase with IDs
IDs such as VIS-, NSM-, SCP-, FEAT-, ENT-, CTX-, API-, NFR-, and KN- are issued for each decision.
By following these IDs, you can later verify which document and which decision a given piece of code originated from.
Validate hypotheses first (validation-driven)
Particularly on the product side, rather than checking after the fact whether what was built is correct, the approach is to ask upfront: “What hypothesis are we currently betting on, and what is the cheapest way to validate it?” (There is a dedicated validation step called /product:validate-assumptions.)
NexusArchitect is built on top of Claude Code’s Skill mechanism. Each command (/product:define-vision,
/architect:export-backlog, etc.) is implemented as a single Skill and is executed either by Claude itself calling the Skill tool or by the user entering a slash command directly.
How to Read This Documentation
Getting Started
Review the setup required before you begin (installation, prerequisites, and output folder structure)
Core Concepts
Understand the mechanisms that underpin the whole system: execution-order rules, confirmation steps, and shared knowledge packs
Skill Reference
Explore the product and architect pipelines in detail, along with the full backlog management workflow
Tutorial
Walk through an end-to-end flow from planning to implementation using the sample product “EASE”
The plugin source code is at wfukatsu/nexus-architect. This site covers documentation only, so please direct bug reports and feature requests to the main repository.