A command that creates an OpenSpec change and generates the planning documents needed before implementation. OpenSpec is the project's system for organizing proposed changes.

Use it to start a new change from a description, create its change directory, check required artifacts, and generate them until the work is ready to implement.

It automates the early planning steps so a requested feature or fix is named, scaffolded, and documented in the required order.

How ly1836/spring-ai-rag-demo configures Claude Code and Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to ly1836/spring-ai-rag-demo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ly1836/spring-ai-rag-demo/main/.cursor/commands/opsx-ff.md

Clone the repo

git clone --depth 1 https://github.com/ly1836/spring-ai-rag-demo

Made for: Claude Code, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-ff/github.svg)](https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-ff)

Your own site

<a href="https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-ff"><img src="https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-ff/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-ff"><img src="https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-ff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 936 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 75% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00936
Opus 5	$0.00010	$0.00468
Sonnet 5	$0.00004	$0.00187
Haiku 4.5	$0.00002	$0.00094

Measured 9d ago against content hash a103b9821dd7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

/opsx-ff scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

75% identical to OPSX: Propose — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/commands/opsx-ff.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fast-forward through artifact creation - generate everything needed to start implementation.

Input: The argument after /opsx:ff is the change name (kebab-case), OR a description of what the user wants to build.

Steps

If no input provided, ask what they want to build

Use the AskUserQuestion tool (open-ended, no preset options) to ask:

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Create the change directory
```
openspec new change "<name>"
```
This creates a scaffolded change at openspec/changes/<name>/.
Get the artifact build order
```
openspec status --change "<name>" --json
```
Parse the JSON to get:
- applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
- artifacts: list of all artifacts with their status and dependencies
Create artifacts in sequence until apply-ready

Use the TodoWrite tool to track progress through the artifacts.

Loop through artifacts in dependency order (artifacts with no pending dependencies first):

a. For each artifact that is ready (dependencies satisfied):
- Get instructions:
```
openspec instructions <artifact-id> --change "<name>" --json
```
- The instructions JSON includes:
  - context: Project background (constraints for you - do NOT include in output)
  - rules: Artifact-specific rules (constraints for you - do NOT include in output)
  - template: The structure to use for your output file
  - instruction: Schema-specific guidance for this artifact type
  - outputPath: Where to write the artifact
  - dependencies: Completed artifacts to read for context
- Read any completed dependency files for context
- Create the artifact file using template as the structure
- Apply context and rules as constraints - but do NOT copy them into the file
- Show brief progress: "✓ Created "
b. Continue until all applyRequires artifacts are complete
- After creating each artifact, re-run openspec status --change "<name>" --json
- Check if every artifact ID in applyRequires has status: "done" in the artifacts array
- Stop when all applyRequires artifacts are done
c. If an artifact requires user input (unclear context):
- Use AskUserQuestion tool to clarify
- Then continue with creation
Show final status
```
openspec status --change "<name>"
```

Output

After completing all artifacts, summarize:

Change name and location
List of artifacts created with brief descriptions
What's ready: "All artifacts created! Ready for implementation."
Prompt: "Run /opsx:apply to start implementing."

Artifact Creation Guidelines

Follow the instruction field from openspec instructions for each artifact type
The schema defines what each artifact should contain - follow it
Read dependency artifacts for context before creating new ones
Use template as the structure for your output file - fill in its sections
IMPORTANT: context and rules are constraints for YOU, not content for the file
- Do NOT copy <context>, <rules>, <project_context> blocks into the artifact
- These guide what you write, but should never appear in the output

Guardrails

Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
Always read dependency artifacts before creating a new one
If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
If a change with that name already exists, ask if user wants to continue it or create a new one
Verify each artifact file exists after writing before proceeding to next

Read the full file on GitHub · 98 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 98 lines · 19 tokens per session scan A a103b9821dd7

Subscribe to this mod's changes

/opsx-ff is a command published in the GitHub repository ly1836/spring-ai-rag-demo (85 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 936 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to OPSX: Propose, differing in 28 lines, and is treated as a copy.

Planning ai-agents deepseek docker echarts erp gemini workflow

context

A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.

fengshao1227/ccg-workflow · 23 tokens

init

A project-initialization command that scans a codebase and creates or updates CLAUDE.md files. These files give AI coding tools project and module instructions, and the command also creates navigation diagrams.

fengshao1227/ccg-workflow · 20 tokens

clean-branches

A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.

fengshao1227/ccg-workflow · 23 tokens

rollback

An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.

fengshao1227/ccg-workflow · 22 tokens

spec-research

A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.

fengshao1227/ccg-workflow · 16 tokens

spec-impl

An implementation command that follows an approved specification and task checklist, uses multiple analysis models, and archives the completed work. It keeps changes within the defined scope and requires external suggestions to be reviewed before use.

fengshao1227/ccg-workflow · 12 tokens

spring-ai-rag-demo: Command for Claude Code