---
title: What is NexusArchitect
description: >-
  An overview of what NexusArchitect, a tool that runs on Claude Code, does for
  you
seo:
  image: /ogp.png
---
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).

<CardGroup cols={1}>
  <Card title="product" icon="compass" href="/skills/product-pipeline">
    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
  </Card>
  <Card title="architect" icon="hammer" href="/skills/architect-pipeline">
    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
  </Card>
  <Card title="scalardb" icon="database">
    The part that is only involved when ScalarDB/ScalarDL is used as the database. Handles data design, code generation, and consultation when issues arise
  </Card>
  <Card title="infra" icon="server" href="/skills/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
  </Card>
</CardGroup>

:::tip[For those who want to try it first]
[Quick Start](/getting-started/first-run) lists the commands to run after installation, in order.
:::

The product and architect components are connected through the `reports/` folder, and scalardb/infra are components that branch off from it conditionally.

```mermaid
flowchart LR
  P["product<br/>(Vision→Scope→…→Architecture)"] --> R[("reports/")]
  R --> AR["architect<br/>(設計・実装・レビュー・マージ)"]
  AR -. ScalarDB/ScalarDL使用時 .-> S["scalardb<br/>(データ設計・コード生成・相談)"]
  AR -. クラウド基盤を使用時 .-> I["infra<br/>(基盤設計・実装・レビュー)"]
```

## Design Philosophy

NexusArchitect is built around three core principles.

1. **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.

2. **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.

3. **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

<CardGroup cols={2}>
  <Card title="Getting Started" icon="rocket" href="/getting-started/installation">
    Review the setup required before you begin (installation, prerequisites, and output folder structure)
  </Card>
  <Card title="Core Concepts" icon="brain" href="/concepts">
    Understand the mechanisms that underpin the whole system: execution-order rules, confirmation steps, and shared knowledge packs
  </Card>
  <Card title="Skill Reference" icon="list" href="/skills/product-pipeline">
    Explore the product and architect pipelines in detail, along with the full backlog management workflow
  </Card>
  <Card title="Tutorial" icon="graduation-cap" href="/tutorial">
    Walk through an end-to-end flow from planning to implementation using the sample product "EASE"
  </Card>
</CardGroup>

The plugin source code is at [wfukatsu/nexus-architect](https://github.com/wfukatsu/nexus-architect).
This site covers documentation only, so please direct bug reports and feature requests to the main repository.