Skip to content
Skills Library
Programming · Learning & explanation

Domain Knowledge

/Domain Knowledge

NXTG-Forge product domain knowledge — the mission, core concepts (project spec, agent orchestration, state, Clean Architecture, drift/gap analysis, MCP), the real `forge` CLI surface, and the 3-repo workspace layout. Use when onboarding to what NXTG-Forge IS and why, when a spec/task/agent-orchestration question needs product framing, or before describing forge CLI/state behavior (avoids repeating retired Python-prototype commands).

Licence
MIT
Last repository change
15.10.2026

Assessment and security

90/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

NXTG-Forge product domain knowledge — the mission, core concepts (project spec, agent orchestration, state, Clean Architecture, drift/gap analysis, MCP), the real `forge` CLI surface, and the 3-repo workspace layout. Use when onboarding to what NXTG-Forge IS and why, when a spec/task/agent-orchestration question needs product framing, or before describing forge CLI/state behavior (avoids repeating retired Python-prototype commands).

Original author description

NXTG-Forge product domain knowledge — the mission, core concepts (project spec, agent orchestration, state, Clean Architecture, drift/gap analysis, MCP), the real `forge` CLI surface, and the 3-repo workspace layout. Use when onboarding to what NXTG-Forge IS and why, when a spec/task/agent-orchestration question needs product framing, or before describing forge CLI/state behavior (avoids repeating retired Python-prototype commands).

How it works

  1. What NXTG-Forge is
  2. The 3-repo workspace (real, not a monorepo)
  3. Core concepts (at a glance)
  4. The real forge CLI surface
  5. Gotchas
  6. Additional resources
Original SKILL.md headings · 104 lines, 611 words
SKILL.md preview
---
name: Domain Knowledge
description: >-
  NXTG-Forge product domain knowledge — the mission, core concepts (project
  spec, agent orchestration, state, Clean Architecture, drift/gap analysis, MCP),
  the real `forge` CLI surface, and the 3-repo workspace layout. Use when
  onboarding to what NXTG-Forge IS and why, when a spec/task/agent-orchestration
  question needs product framing, or before describing forge CLI/state behavior
  (avoids repeating retired Python-prototype commands).
when_to_use: >-
  Onboarding to the NXTG-Forge product/vision; explaining the specification →
  plan → run → verify → ship lifecycle; mapping the specialized agent roles;
  clarifying where state lives (.forge/state.json) and which `forge` subcommands
  actually exist; any "what is NXTG-Forge / how does forge work at a concept
  level" question.
disable-model-invocation: true
allowed-tools: Read, Grep, Glob
---

# NXTG-Forge Domain Knowledge

## What NXTG-Forge is

A **self-deploying AI development infrastructure** for Claude Code. Not just a
code generator — an intelligent scaffolding + orchestration system that reads a
project's specification, plans tasks, dispatches specialized agents, and tracks
state across the development lifecycle.

**Mission:** "From specification to production in minutes, not days."

It bridges idea → implementation by: (1) turning a natural-language spec into a
task plan, (2) orchestrating specialized agents, (3) persisting state for
recovery, (4) surfacing quality gaps, (5) integrating natively with Claude Code.

**Problem it solves:** static templates don't adapt; ordinary scaffolds have no
context memory, no orchestration, no state, and no quality signal. NXTG-Forge
adds AI-native intelligence to all four.

## The 3-repo workspace (real, not a monorepo)

```
forge-ui/            React 19 + Vite dashboard (:5050)
forge-orchestrator/  Rust CLI + MCP server — binary: `forge`
forge-plugin/        Claude Code plugin (commands/agents/skills/hooks) — this repo
```

Integration is **MCP-only**; there are no cross-repo code imports.

## Core concepts (at a glance)

1. **Project Specification** — natural-language build description. `forge plan
   --generate` reads `SPEC.md` (or `PRD.md`/`REQUIREMENTS.md`/`README.md`).
2. **Agent Orchestration** — work split across specialized roles (Lead
   Architect, Backend Master, CLI Artisan, Platform Builder, Integration
   Specialist, QA Sentinel), each backed by an `agent-*` sibling skill.
3. **State Management** — persisted to **`.forge/state.json`** with an
   append-only audit log at **`.forge/events.jsonl`**.
4. **Clean Architecture** — Domain → Application → Infrastructure → Interface,
   dependencies pointing inward only.
5. **Drift / Gap Analysis** — health + gap signals via MCP tools
   (`forge_get_health`, `forge_check_drift`, `forge_get_governance_health`).
6. **MCP Integration** — plugin registers governance-mcp (Node) +
   orchestrator-mcp (Rust); semgrep-mcp optional.

Full detail: [reference/concepts.md](reference/concepts.md).

## The real `forge` CLI surface

Verbs in the shipped Rust binary (`forge-orchestrator/src/cli/mod.rs`):

```
init · plan · status · run · start · sync · mcp · dashboard · verify · uat · ship · config · uninstall
```

Worked lifecycle:

```bash
forge init my-app        # scaffold + create .forge/state.json
# author SPEC.md
forge plan --generate    # spec → task plan
forge run                # agents execute planned tasks
forge verify             # governance / quality gate
forge ship --dry-run     # preview SemVer bump + CHANGELOG entry
```

Full workflows: [reference/workflows.md](reference/workflows.md).

## Gotchas

- **Retired Python-prototype commands.** Older docs (and prior versions of this
  skill) show `forge spec generate`, `forge generate`, `forge recovery`, `forge
  health`, `forge gap-analysis`, `forge checkpoint`. **None exist in the shipped
  binary.** Use the real verbs above; grep `forge-orchestrator/src/cli/mod.rs`
  before quoting any `forge` subcommand.
- **State path is `.forge/state.json`, NOT `.claude/state.json`.** The
  orchestrator's `StateManager` (`src/core/state.rs`) owns `.forge/`. `.claude/`
  holds Claude Code assets (governance.json, skills, hooks) — a different store.
- **Health/gap is an MCP surface, not a CLI verb.** There is no `forge
  gap-analysis`. Gap and drift signals arrive through MCP tools; the closest CLI
  verbs are `forge verify` and `forge status`.
- **`forge ship` needs a `CHANGELOG.md` to fully land.** If none exists it only
  prints the changelog instead of appending it (`src/cli/ship.rs`). Version-bump
  suggestion is derived from `.forge/events.jsonl`, so an empty event log yields
  a weak suggestion.
- **Concept role ≠ literal agent file name.** "Backend Master" the concept maps
  to the `agent-backend-master` skill / `builder`-family agent — don't quote the
  prose label as an invocable agent id.
- **Overlaps with `core-nxtg-forge`.** That sibling skill covers platform
  internals (agent system, governance, plugin architecture). This skill is the
  product/vision + concept layer. Route implementation-internals questions
  there; keep this one conceptual.

## Additional resources

- [reference/concepts.md](reference/concepts.md) — the six core concepts in
  depth, with the concept→sibling-skill agent map and state shapes.
- [reference/workflows.md](reference/workflows.md) — real-verb workflows
  (init/plan/run/verify/uat/ship) + the retired-command note.
- [reference/architecture-and-glossary.md](reference/architecture-and-glossary.md)
  — component map, workspace + per-project layout, value proposition, use cases,
  roadmap, glossary, and the living lessons-learned log.
Files in this package (4)
  • SKILL.md 6 KB
  • reference/architecture-and-glossary.md 4 KB
  • reference/concepts.md 3 KB
  • reference/workflows.md 2 KB

Versions

The database has no other skills named Domain Knowledge.

Database snapshot: 13.11.2026 · package version c65b96278101 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Core NXTG-Forge
    Ground truth for the NXTG-Forge platform — the real forge CLI subcommands, the /nxtg-forge:* slash commands, the .forge/state.json + events.jsonl model, both MCP servers (Rust orchestrator + Node governance), the agent roster, and the security hooks. Use when working inside or…
  • 90Documentation
    Documentation standards and code-to-docs sync conventions for Forge projects — JSDoc/TSDoc annotations, README/CHANGELOG structure, auto-generated API reference, doc-tree layout, and staleness detection. Use when writing or reviewing docs, adding JSDoc to exported functions,…
  • 100forge-cli
    Use when an agent needs to call a running three.ws Forge desktop instance from the terminal to generate/export image-to-3D assets through canonical JSON-first automation commands.
  • 100forge-onboarding
    Guide a first-time Forge builder through building Forge Guru, a Rovo Agent that answers Forge questions. Use for Forge onboarding, a first Forge or Rovo app, or resuming this tutorial. Route unrelated existing-app changes, debugging, reviews, and connector work to the specialist skills.
  • 95forge-app-builder
    Guides building, deploying, troubleshooting, and installing Atlassian Forge apps — custom extensions built with the Forge CLI (forge create, forge deploy, forge install). Use when the user wants to create a Forge app (issue panels, dashboard gadgets, Confluence macros, global…
  • 100forge
    Route every GitHub or GitLab action through the CLI's forge verbs, as the remembered account and only after the user says yes. Use when the user asks to open a PR, merge the PR, create an issue, create a tag, publish a release, edit a PR, resolve a review thread, or read a PR,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.