Name: change
Author: zlatkomq

Prompt file imported from zlatkomq/spec-first-framework (.cursor/commands/change.md). Copyright stays with the author.

change

Handle a scope change or change request for an existing spec. Produces a Change Proposal document with impact analysis and, on approval, updates affected artifacts.

Usage

/change {spec_reference} — where {spec_reference} is a spec ID (e.g. 001), slug (e.g. 001-user-registration), or folder path.

Optionally include a Jira ticket reference after a colon:

/change 001: PROJ-456 — loads the spec and uses the Jira ticket for classification check.

1. Parse user input

Split on colon (:): before = spec reference, after = Jira ticket ID or change description.
Parse spec reference to extract spec_id and spec_slug (same logic as /flow).

2. Resolve spec folder

Search specs/ for a folder matching {spec_id}.
If not found: "No spec folder found for {spec_id}. Cannot create a change request without an existing spec." STOP.
Verify SPEC.md exists in the folder. If not: STOP.

3. Load context

Read {spec_folder}/SPEC.md (acceptance criteria, scope, Bug History, Amendment History).
Read {spec_folder}/DESIGN.md (if exists).
Read {spec_folder}/TASKS.md (if exists).
Read CONSTITUTION.md for project standards.

4. Apply rules

Apply @skills/change-request/SKILL.md — this handles:

Classification check (if Jira ticket provided)
Change analysis and impact assessment
Change Proposal generation
Approval and artifact updates
Amendment History population
SPEC-CURRENT.md regeneration

Reference

Skill: skills/change-request/SKILL.md
Template: .framework/templates/CHANGE-PROPOSAL.template.md
Output: {spec_folder}/CHANGE-PROPOSAL-{date}.md

Install change and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# change\n\nHandle a scope change or change request for an existing spec. Produces a Change Proposal document with impact analysis and, on approval, updates affected artifacts.\n\n## Usage\n\n`/change {spec_reference}` — where `{spec_reference}` is a spec ID (e.g. `001`), slug (e.g. `001-user-registration`), or folder path.\n\nOptionally include a Jira ticket reference after a colon:\n\n`/change 001: PROJ-456` — loads the spec and uses the Jira ticket for classification check.\n\n## 1. Parse user input\n\n- Split on colon (`:`): before = spec reference, after = Jira ticket ID or change description.\n- Parse spec reference to extract `spec_id` and `spec_slug` (same logic as `/flow`).\n\n## 2. Resolve spec folder\n\n- Search `specs/` for a folder matching `{spec_id}`.\n- If not found: \"No spec folder found for {spec_id}. Cannot create a change request without an existing spec.\" STOP.\n- Verify SPEC.md exists in the folder. If not: STOP.\n\n## 3. Load context\n\n- Read `{spec_folder}/SPEC.md` (acceptance criteria, scope, Bug History, Amendment History).\n- Read `{spec_folder}/DESIGN.md` (if exists).\n- Read `{spec_folder}/TASKS.md` (if exists).\n- Read `CONSTITUTION.md` for project standards.\n\n## 4. Apply rules\n\nApply @skills/change-request/SKILL.md — this handles:\n- Classification check (if Jira ticket provided)\n- Change analysis and impact assessment\n- Change Proposal generation\n- Approval and artifact updates\n- Amendment History population\n- SPEC-CURRENT.md regeneration\n\n## Reference\n\n- Skill: `skills/change-request/SKILL.md`\n- Template: `.framework/templates/CHANGE-PROPOSAL.template.md`\n- Output: `{spec_folder}/CHANGE-PROPOSAL-{date}.md`", "variables": [], "notes": "Handle a scope change or change request for an existing spec. Produces a Change Proposal document with impact analysis and, on approval, updates affected artifacts.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zlatkomq/spec-first-framework", "path": ".cursor/commands/change.md", "ref": "b68394c29200be946c7b556153c5cb1b925fe1d0", "url": "https://github.com/zlatkomq/spec-first-framework/blob/b68394c29200be946c7b556153c5cb1b925fe1d0/.cursor/commands/change.md", "key": "zlatkomq/spec-first-framework/.cursor/commands/change.md" } } }

change

About

change

Usage

1. Parse user input

2. Resolve spec folder

3. Load context

4. Apply rules

Reference

Install change and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews