Nexent Spec Coding
Run Nexent requirements and bugfixes through SPEC acceptance, traditional UT and...
Install
npx skills add ModelEngine-Group/nexent --skill nexent-spec-coding -g -a claude-code -y- Repository
- ModelEngine-Group/nexent6.1k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
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.
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 siblingnexent-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, andtest/ext_componentsas 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.
