# Nexent Spec Coding

Run Nexent requirements and bugfixes through SPEC acceptance, traditional UT and...

- Repository: https://github.com/ModelEngine-Group/nexent (6109 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ModelEngine-Group/nexent --skill nexent-spec-coding -g -a claude-code -y`
Codex: `npx skills add ModelEngine-Group/nexent --skill nexent-spec-coding -g -a codex -y`
Cursor: `npx skills add ModelEngine-Group/nexent --skill nexent-spec-coding -g -a cursor -y`
Gemini CLI: `npx skills add ModelEngine-Group/nexent --skill nexent-spec-coding -g -a gemini-cli -y`

## Description

Run Nexent requirements and bugfixes through SPEC acceptance, traditional UT and applicable D1-D5 test design, product/test implementation, local verification, and delivery evidence. Use for features, fixes, refactors and post-development test backfill across APIs, UI, model and Agent behavior.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Nexent SPEC Coding

Develop Nexent from an evidence-backed SPEC while keeping product behavior, formal D1-D5 test assets, implementation, and verification synchronized.

## Repository boundaries

- Treat `nexent/` as the Git-managed product repository and its sibling `nexent-doc/` as the document repository.
- Never run Git commands in the document repository or move SPEC documents into the product repository.
- Preserve unrelated changes. Record the initial branch/status, applicable repository instructions, build configuration, and test layout.
- Keep the existing tests under `test/backend`, `test/sdk`, and `test/ext_components` as Legacy UT. Do not map them into the formal D1-D5 registry.
- Traditional UT is a permanently maintained PR obligation, not a temporary baseline. Assess it for every product-code change, using nexent-python-tests. Preserve all existing D1 Cases/scripts; new D1 focuses on component evidence beyond UT, while D3 proves actual runtime integration. Do not force new Cases at all five stages.

## Read the right references

The rest: https://github.com/ModelEngine-Group/nexent/blob/HEAD/.agents/skills/nexent-spec-coding/SKILL.md