cc-nexs

Plugin cc-nexs from marketplace cc-nexs in TANAGELEEE/cc-nexs. Commands read from the repo's manifest — 2 days ago.

Skills (34)

• cc-nexs-approve-plan

  /cc-nexs:approve-plan Codex mirror skill. Use when $cc-nexs-approve-plan is explicitly invoked. Approve the Lean requirements and plan scope, binding the gate to their hashes.

• cc-nexs-approve-release

  /cc-nexs:approve-release Codex mirror skill. Use when $cc-nexs-approve-release is explicitly invoked. Record Gateway B approval for an exact candidate and its test evidence or authorized environment exception.

• cc-nexs-brainstorm

  /cc-nexs:brainstorm Codex mirror skill. Use when $cc-nexs-brainstorm is explicitly invoked. Optional requirements clarification entry point: completes requirements.md; when requirements are complete, proceeds directly to the planning step of the current mode.

• cc-nexs-build

  /cc-nexs:build Codex mirror skill. Use when $cc-nexs-build is explicitly invoked. Run only changed modules with exact-candidate success caching and dependency-aware bounded parallelism.

• cc-nexs-compound

  /cc-nexs:compound Codex mirror skill. Use when $cc-nexs-compound is explicitly invoked. Compound role entry point. Read all-docs/doc/<id>/* for the completed requirement and distill \"non-obvious lessons\" into docs/solutions/<topic>.md, so the Lean Planner picks it up for the next similar requireme

• cc-nexs-doctor

  /cc-nexs:doctor Codex mirror skill. Use when $cc-nexs-doctor is explicitly invoked. Validate workspace repositories, private overlay, and progress.json v2 files without changing project state.

• cc-nexs-execute

  /cc-nexs:execute Codex mirror skill. Use when $cc-nexs-execute is explicitly invoked. Lean implementation entry point. Implements in parallel by plan task and path ownership; not responsible for Git mutation.

• cc-nexs-git-custodian

  /cc-nexs:git-custodian Codex mirror skill. Use when $cc-nexs-git-custodian is explicitly invoked. Sole Git mutation boundary for multi-repository worktrees, candidate commits, merge verification, and safe cleanup.

• cc-nexs-hotfix

  /cc-nexs:hotfix Codex mirror skill. Use when $cc-nexs-hotfix is explicitly invoked. Hotfix — independent fix branch and BUG document, local verification, independent Review, test acceptance, and Gateway B.

• cc-nexs-init

  /cc-nexs:init Codex mirror skill. Use when $cc-nexs-init is explicitly invoked. Initialize a new requirement directory from a template. Automatically continues numbering from existing numbers under all-docs/doc/, and automatically generates a slug from the requirement description. By default, create

• cc-nexs-lean-review

  /cc-nexs:lean-review Codex mirror skill. Use when $cc-nexs-lean-review is explicitly invoked. Lean: one consolidated Review by the review panel and a Judge, and at most one delta closure check.

• cc-nexs-lean-verify

  /cc-nexs:lean-verify Codex mirror skill. Use when $cc-nexs-lean-verify is explicitly invoked. Lean test environment black-box acceptance, aggregating AC evidence directly into plan.md.

• cc-nexs-migrate-feature-config

  /cc-nexs:migrate-feature-config Codex mirror skill. Use when $cc-nexs-migrate-feature-config is explicitly invoked. Safely migrate an existing Lean/Hotfix config.json to automatic risk-based model routing without removing explicit overrides.

• cc-nexs-plan

  /cc-nexs:plan Codex mirror skill. Use when $cc-nexs-plan is explicitly invoked. Lean default-mode planning entry point. Drafts or normalizes requirements.md and plan.md, runs the independent plan review for high/critical plans, and stops at Gateway A unless --auto-plan authorized it.

• cc-nexs-release-base

  /cc-nexs:release-base Codex mirror skill. Use when $cc-nexs-release-base is explicitly invoked. Integrate exact approved candidates into configured base branches and clean worktrees after proof.

• cc-nexs-release-test

  /cc-nexs:release-test Codex mirror skill. Use when $cc-nexs-release-test is explicitly invoked. Integrate final feature candidates into test, run the project release driver, then hand deployed evidence to the black-box Verifier.

• cc-nexs-render-plan

  /cc-nexs:render-plan Codex mirror skill. Use when $cc-nexs-render-plan is explicitly invoked. Render the Lean plan Markdown as a human-friendly temporary HTML page.

• cc-nexs-request-release-changes

  /cc-nexs:request-release-changes Codex mirror skill. Use when $cc-nexs-request-release-changes is explicitly invoked. Record Gateway B feedback and route evidence-only, implementation, or scope changes safely.

• cc-nexs-resolve-test-conflict

  /cc-nexs:resolve-test-conflict Codex mirror skill. Use when $cc-nexs-resolve-test-conflict is explicitly invoked. Continue test delivery after a real test branch merge conflict.

• cc-nexs-revise-hotfix

  /cc-nexs:revise-hotfix Codex mirror skill. Use when $cc-nexs-revise-hotfix is explicitly invoked. Record authorized Hotfix scope revisions in place, or promote the same repair to Lean.

• cc-nexs-run

  /cc-nexs:run Codex mirror skill. Use when $cc-nexs-run is explicitly invoked. Lean/Hotfix orchestrator. Runs the active mode through local verification, Review, one exact-candidate test release, and the release gate unless explicitly opted out or prerequisites are unavailable.

• cc-nexs-status

  /cc-nexs:status Codex mirror skill. Use when $cc-nexs-status is explicitly invoked. Read-only status snapshot of the active feature pipeline.

• cc-nexs-switch-test-target

  /cc-nexs:switch-test-target Codex mirror skill. Use when $cc-nexs-switch-test-target is explicitly invoked. Switch one task to an explicitly authorized non-production test environment.

• cc-nexs-sync-base

  /cc-nexs:sync-base Codex mirror skill. Use when $cc-nexs-sync-base is explicitly invoked. Synchronize changed base into assigned development worktrees and resume verification.

• cc-nexs-verify-local

  /cc-nexs:verify-local Codex mirror skill. Use when $cc-nexs-verify-local is explicitly invoked. Run the fast Lean/Hotfix pre-deployment checks and bind evidence to exact candidate commits.

• cc-nexs-verify-skill

  /cc-nexs:verify-skill Codex mirror skill. Use when $cc-nexs-verify-skill is explicitly invoked. Create or refresh a code repository's verification guide and feature map, in the repository, in the docs repository (--docs), or in the workspace (--workspace), so every Verifier drives the real app the s

• brainstorming

  Clarify ambiguous requirements and update requirements.md during an explicit cc-nexs brainstorm. Skip when the requirements are complete; not a general prerequisite step for writing code or planning.

• branch-gate

  Compatibility guard that verifies the current worktree assignment without creating or changing branches.

• commit-discipline

  cc-nexs candidate commit constraints. The Git Custodian commits the specified paths, preserving the commit history bound to review and verification.

• md-aggregation

  cc-nexs document aggregation rules quick reference. Avoid file proliferation (the anti-pattern of one md file per round). Trigger words: plan.md evidence, BUG document, append, file naming, appending, document proliferation.

• merge-discipline

  Compatibility guard for merge requests. Roles never merge; release automation or a human merges candidates, then Git Custodian verifies and cleans up.

• role-isolation

  Verify the read/write boundaries and independent-session requirements of the current cc-nexs role; applies to dispatched SOP roles.

• using-cc-nexs

  Guides new features, cross-module requirements, full development-test acceptance, or 'run by the SOP' requests into cc-nexs. New requirements default to lean, with support for a single consolidated Review, test release, automated browser acceptance, manual fallback, and hotfix triage.

• using-worktrees

  Compatibility entry for worktree requests. Delegates all repository topology changes to the Orchestrator-owned Git Custodian.

Slash commands (26)

• /cc-nexs:approve-plan

  Approve the Lean requirements and plan scope, binding the gate to their hashes.

• /cc-nexs:approve-release

  Record Gateway B approval for an exact candidate and its test evidence or authorized environment exception.

• /cc-nexs:brainstorm

  Optional requirements clarification entry point: completes requirements.md; when requirements are complete, proceeds directly to the planning step of the current mode.

• /cc-nexs:build

  Run only changed modules with exact-candidate success caching and dependency-aware bounded parallelism.

• /cc-nexs:compound

  Compound role entry point. Read all-docs/doc/<id>/* for the completed requirement and distill \"non-obvious lessons\" into docs/solutions/<topic>.md, so the Lean Planner picks it up for the next similar requirement. Bypass command; does not enter the state machine.

• /cc-nexs:doctor

  Validate workspace repositories, private overlay, and progress.json v2 files without changing project state.

• /cc-nexs:execute

  Lean implementation entry point. Implements in parallel by plan task and path ownership; not responsible for Git mutation.

• /cc-nexs:git-custodian

  Sole Git mutation boundary for multi-repository worktrees, candidate commits, merge verification, and safe cleanup.

• /cc-nexs:hotfix

  Hotfix — independent fix branch and BUG document, local verification, independent Review, test acceptance, and Gateway B.

• /cc-nexs:init

  Initialize a new requirement directory from a template. Automatically continues numbering from existing numbers under all-docs/doc/, and automatically generates a slug from the requirement description. By default, creates an independent git worktree in .worktrees/<id>-<slug>/, so multiple requiremen

• /cc-nexs:lean-review

  Lean: one consolidated Review by the review panel and a Judge, and at most one delta closure check.

• /cc-nexs:lean-verify

  Lean test environment black-box acceptance, aggregating AC evidence directly into plan.md.

• /cc-nexs:migrate-feature-config

  Safely migrate an existing Lean/Hotfix config.json to automatic risk-based model routing without removing explicit overrides.

• /cc-nexs:plan

  Lean default-mode planning entry point. Drafts or normalizes requirements.md and plan.md, runs the independent plan review for high/critical plans, and stops at Gateway A unless --auto-plan authorized it.

• /cc-nexs:release-base

  Integrate exact approved candidates into configured base branches and clean worktrees after proof.

• /cc-nexs:release-test

  Integrate final feature candidates into test, run the project release driver, then hand deployed evidence to the black-box Verifier.

• /cc-nexs:render-plan

  Render the Lean plan Markdown as a human-friendly temporary HTML page.

• /cc-nexs:request-release-changes

  Record Gateway B feedback and route evidence-only, implementation, or scope changes safely.

• /cc-nexs:resolve-test-conflict

  Continue test delivery after a real test branch merge conflict.

• /cc-nexs:revise-hotfix

  Record authorized Hotfix scope revisions in place, or promote the same repair to Lean.

• /cc-nexs:run

  Lean/Hotfix orchestrator. Runs the active mode through local verification, Review, one exact-candidate test release, and the release gate unless explicitly opted out or prerequisites are unavailable.

• /cc-nexs:status

  Read-only status snapshot of the active feature pipeline.

• /cc-nexs:switch-test-target

  Switch one task to an explicitly authorized non-production test environment.

• /cc-nexs:sync-base

  Synchronize changed base into assigned development worktrees and resume verification.

• /cc-nexs:verify-local

  Run the fast Lean/Hotfix pre-deployment checks and bind evidence to exact candidate commits.

• /cc-nexs:verify-skill

  Create or refresh a code repository's verification guide and feature map, in the repository, in the docs repository (--docs), or in the workspace (--workspace), so every Verifier drives the real app the same way. Bypass command; does not enter the state machine.

Subagents (9)

• compound-claude

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Compound identity. Reads the completed all-docs/doc/<id>/* and distills \"non-obvious lessons\" into docs/solutions/<topic>.md, so that the Lean Planner picks them u

• hotfix-developer

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Implement a Hotfix with a bound scope inside an isolated latest-base hotfix worktree, and return precise change and verification information.

• hotfix-reviewer

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Hotfix Reviewer. As a panel reviewer, tries to break the exact Hotfix candidate and returns run-proven findings; as the Judge, reruns them, keeps every verified find

• hotfix-verifier

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Independently perform black-box reproduction, regression, and smoke acceptance of the exact Hotfix candidate in the test environment.

• lean-developer

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Implementation role for Lean mode. Executes only assigned plan tasks, and can implement frontend and backend in parallel along non-overlapping paths.

• lean-plan-reviewer

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Lean mode independent plan reviewer. Challenges requirements.md and plan.md against the repository before Gateway A; blocks only P0/P1.

• lean-planner

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Lean-mode planning role. Collects the necessary current state in parallel, maintains the approved scope of requirements.md and plan.md, and does not write business c

• lean-reviewer

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Lean mode Reviewer. As a panel reviewer, tries to break the exact candidate and returns run-proven findings; as the Judge, reruns them, keeps every verified finding,

• lean-verifier

  Only dispatch after the user explicitly invokes a cc-nexs command or skill; never auto-trigger for ordinary natural-language requests. Black-box acceptance role for the Lean mode test environment. Verifies the deployed candidate against the plan's test matrix.

Hooks (3)

• PreToolUse

  node -e "const p=require('node:path'),u=require('node:url'),r=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT||process.env.CC_NEXS_PLUGIN_ROOT;if(!r){console.error('[cc-nexs hook] plugin root

• PreToolUse

  node -e "const p=require('node:path'),u=require('node:url'),r=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT||process.env.CC_NEXS_PLUGIN_ROOT;if(!r){console.error('[cc-nexs hook] plugin root

• PreToolUse

  node -e "const p=require('node:path'),u=require('node:url'),r=process.env.PLUGIN_ROOT||process.env.CLAUDE_PLUGIN_ROOT||process.env.CC_NEXS_PLUGIN_ROOT;if(!r){console.error('[cc-nexs hook] plugin root

Similar plugins