From nexa-claude-core
Creates structured change request documents for intentional modifications to already-implemented use cases. Use when the user asks to "create a change request", "log a CR", "document a change", or describes a stakeholder-requested modification to existing behavior (e.g., renaming a field, changing validation rules, restructuring data). A change request always references exactly one use case and describes only the delta — the original use case remains immutable.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nexa-claude-core:change-requestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a change request document for $ARGUMENTS in `docs/change_requests/`. $ARGUMENTS is a
Create a change request document for $ARGUMENTS in docs/change_requests/. $ARGUMENTS is a
description of the requested change, a reference to a use case (UC-XXX) where the behavior
is currently defined, or a full GitHub issue URL.
A change request describes an intentional, stakeholder-approved modification to behavior that is already implemented. It is not a bug (unintended deviation) and not a new use case (net-new behavior). It is a delta: what changes, why, and what is affected.
One change request references exactly one use case. If a change spans multiple use cases, create one CR per use case.
report-bug instead)use-case-spec instead)Read and follow ${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md.
Use templates/change-request.md as the document structure.
| CR ID | CR-001 |
| Title | Replace 'Role' field with 'Department' on User Profile form |
| Status | Open |
| References | UC-007: Edit User Profile |
| Requested By | Product — customer feedback Q1 2026 |
| Origin | human-in-the-loop |
| GitHub Issue | https://github.com/acme/app/issues/88 |
UC-007 currently allows users to edit their profile, which includes a free-text role field
stored in the users table. The field is displayed on the profile page and used in team listings.
Replace the role free-text field with a department dropdown backed by a departments
lookup table. The dropdown must be populated from the database and validated server-side.
The role column in users is renamed to department_id (foreign key).
department_id against lookup tableusers.role to users.department_id; add departments table; migrate datarole fieldDepartment dropdown populated from the databasedepartment_idrole free-text field no longer appears anywhere in the UIdepartment_id valuesrole value migrated to the closest matching department| Test File | Test Name | Action Required |
|---|---|---|
e2e/profile/edit-profile.spec.ts | user can update role | Update — rename to user can update department, replace text input interaction with dropdown selection |
e2e/team/team-listing.spec.ts | team members display role | Update — assert department label instead of role |
Annotation: All updated and new E2E tests must carry both @UC-007 and @CR-001.
docs/use_cases/UC-007-edit-user-profile.mdsrc/app/profile/, src/actions/profile.ts, prisma/schema.prismaDetermine the origin of the change request from $ARGUMENTS:
github-issue — $ARGUMENTS contains a GitHub issue URL. The issue already exists and is
the source of truth.human-in-the-loop — $ARGUMENTS is a description or artifact reference with no issue URL.
The CR document becomes the source of truth and a new GitHub issue will be created.docs/change_requests/ for existing CRs to determine the next CR-XXX IDdocs/use_cases/ to understand the current behaviorgithub-issue:
a. Read the issue: gh issue view <issue-number> --json title,body,labels
b. Extract the change description and context from the issue
c. Set Origin to the full GitHub issue URL
d. Set GitHub Issue to the same URL — do NOT create a new issuehuman-in-the-loop:
a. Gather the change description from the user's request
b. Set Origin to human-in-the-loopdocs/requirements.md to reflect the new desired behavior## Amendments section of the referenced UC file in this format:
- **CR-XXX** ([date]) — [One-line summary of what changed]. Full spec: `docs/change_requests/CR-XXX-<slug>.md`
If the UC file has no ## Amendments section yet, add it above the --- divider.human-in-the-loop:
a. Create a GitHub tracking issue by following the Before Implementation steps in
${CLAUDE_PLUGIN_ROOT}/shared/tracking/TRACKING.md
b. Update the CR's GitHub Issue field with the issue URLgithub-issue:
a. Follow the Before Implementation steps in ${CLAUDE_PLUGIN_ROOT}/shared/tracking/TRACKING.md
— the issue already exists, so only the hash sync and drift reconciliation steps applynpx claudepluginhub nexadevapp/nexa-claude-skills-marketplace --plugin nexa-claude-coreCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.