New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Openspec Propose Change

by sillsdev in sillsdev/FieldWorks

Create a change and generate all artifacts needed for implementation in one go.

MITAuto-check passed

Install Openspec Propose Change

skills CLI
$ npx skills add sillsdev/FieldWorks --skill openspec-propose-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sillsdev/FieldWorks openspec-propose-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/openspec-propose-change .claude/skills/openspec-propose-change && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openspec-propose-change
GitHub stars
110
Token cost
~1.2k tokens
SKILL.md length
552 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Create a change and generate all artifacts needed for implementation in one go.

  • Works in 5 steps: If no clear input provided, ask what… → Create the change directory → Get the artifact build order → …
  • The user wants the preferred OpenSpec fast path for a new proposal
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Openspec Propose Change is an agent skill from sillsdev/FieldWorks. Create a change and generate all artifacts needed for implementation in one go. Use when the user wants the preferred OpenSpec fast path for a new proposal.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires openspec CLI.

The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts. The licence is MIT.

When your agent uses it

  • The user wants the preferred OpenSpec fast path for a new proposal

Example prompts

  • “/openspec-propose-change”

Requirements

  • Compatibility (from SKILL.md): Requires openspec CLI.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. If no clear input provided, ask what they want to build
  2. Create the change directory
  3. Get the artifact build order
  4. Create artifacts in sequence until apply-ready
  5. Show final status

What it can do on your machine

Read from SKILL.md and the folder at commit 489ed1b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires openspec CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Openspec Propose Change loads about 1.2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sillsdev/FieldWorks at commit 489ed1b, republished under its MIT licence (© sillsdev). 552 words, ~1,169 tokens.

Download SKILL.mdSave it as .claude/skills/openspec-propose-change/SKILL.md (or your agent's skills folder).
name
openspec-propose-change
description
Create a change and generate all artifacts needed for implementation in one go. Use when the user wants the preferred OpenSpec fast path for a new proposal.
compatibility
Requires openspec CLI.
license
MIT
metadata.author
openspec
metadata.version
1.0
metadata.generatedBy
1.3.1

Create a change and generate all artifacts needed for implementation in one go.

This is the preferred user-facing alias of the fast-forward workflow.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

  1. If no clear 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.

    If the request uses overloaded repo terms or unclear planning language, apply grill-with-docs before creating artifacts so proposal/spec/design wording matches CONTEXT.md and real codebase terminology.

  2. Create the change directory

    bash
    openspec new change "<name>"

    This creates a scaffolded change at openspec/changes/<name>/.

  3. Get the artifact build order

    bash
    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

  4. 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:
      bash
      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 <artifact-id>"

    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

  5. Show final status

    bash
    openspec status --change "<name>"
Show full SKILL.md (181 more words)Show less

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 or ask me to implement to start working on the tasks."

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, suggest continuing that change instead
  • Verify each artifact file exists after writing before proceeding to next

© sillsdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/openspec-propose-change of sillsdev/FieldWorks.

Open the folder on GitHubat commit 489ed1b

Compare with similar skills

Openspec Propose Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openspec Propose Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openspec Propose Change this skillsillsdev/FieldWorks110—~1.2kAutomated safety check: PassMIT
Geo Proposalsickn33/agentic-awesome-skills47k1 repos~3.2kAutomated safety check: NotesMIT
Better Proposals AutomationComposioHQ/awesome-claude-skills77k3 repos~764Automated safety check: PassNone
Contract And Proposal Writeralirezarezvani/claude-skills28k2 repos~3.4kAutomated safety check: PassMIT
ProposalChorus-AIDLC/Chorus1.2k—~5.5kAutomated safety check: PassAGPL-3.0
Proposal Writerholaboss-ai/holaOS11k—~574Automated safety check: PassCustom licence

Similar skills

  • Geo Proposal

    sickn33/agentic-awesome-skills

    Auto-generate a professional, client-ready GEO service proposal from audit data.

    47k GitHub starsUsed in 1 repo~3.2k tokens
    Sales & SupportAuto-check: notes

  • Better Proposals Automation

    ComposioHQ/awesome-claude-skills

    Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~764 tokens
    Productivity & AutomationAuto-check passed

  • Contract And Proposal Writer

    alirezarezvani/claude-skills

    Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs.

    28k GitHub starsUsed in 2 repos~3.4k tokens
    Legal & ComplianceAuto-check passed

  • Proposal

    Chorus-AIDLC/Chorus

    Chorus Proposal workflow on Hermes — create proposals with document and task drafts, manage dependency DAG, validate, submit, and run the read-only proposal reviewer via delegatetask.

    1.2k GitHub stars~5.5k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Proposal Writer

    holaboss-ai/holaOS

    Draft client proposals and statements of work that scope, price, and win the project.

    11k GitHub stars~574 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • Openspec Verify Change

    Fission-AI/OpenSpec

    Verify implementation matches OpenSpec change artifacts. An agent skill from Fission-AI/OpenSpec.

    71k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

More from sillsdev/FieldWorks

All 29 skills in this repo

  • Atlassian Readonly Skills

    sillsdev/FieldWorks

    Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.

    110 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Atlassian Skills

    sillsdev/FieldWorks

    Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.

    110 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Fieldworks Winapp

    sillsdev/FieldWorks

    Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.

    110 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Convert Slice

    sillsdev/FieldWorks

    Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.

    110 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Dependabot Consolidation

    sillsdev/FieldWorks

    Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…

    110 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Fieldworks Semantic Render Parity

    sillsdev/FieldWorks

    Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.

    110 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Openspec Propose Change

What does Openspec Propose Change do?

Create a change and generate all artifacts needed for implementation in one go. Openspec Propose Change is an agent skill from sillsdev/FieldWorks. Create a change and generate all artifacts needed for implementation in one go.

When should I use Openspec Propose Change?

Openspec Propose Change fits situations like: the user wants the preferred OpenSpec fast path for a new proposal.

How do I install Openspec Propose Change in Claude Code?

Run `npx skills add sillsdev/FieldWorks --skill openspec-propose-change -a claude-code`. Or copy the skill folder (.claude/skills/openspec-propose-change in sillsdev/FieldWorks) into .claude/skills/openspec-propose-change in your project. Claude Code loads it when a task matches its description.

How do I install Openspec Propose Change in Codex?

Run `npx skills add sillsdev/FieldWorks --skill openspec-propose-change -a codex`. Or copy the skill folder (.claude/skills/openspec-propose-change in sillsdev/FieldWorks) into .agents/skills/openspec-propose-change in your project. Codex loads it when a task matches its description.

Can I use Openspec Propose Change in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sillsdev/FieldWorks --skill openspec-propose-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openspec-propose-change, .gemini/skills/openspec-propose-change, .github/skills/openspec-propose-change and .opencode/skills/openspec-propose-change in your project.

What does Openspec Propose Change need to run?

SKILL.md names no scripts, command-line tools or credentials: Openspec Propose Change is instructions for the agent only. Compatibility (from SKILL.md): Requires openspec CLI..

Does Openspec Propose Change access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Openspec Propose Change safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openspec Propose Change use?

Openspec Propose Change is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openspec Propose Change use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Openspec Propose Change?

Skills that share tags, products or a category with Openspec Propose Change: Geo Proposal (sickn33/agentic-awesome-skills, 47k stars), Better Proposals Automation (ComposioHQ/awesome-claude-skills, 77k stars), Contract And Proposal Writer (alirezarezvani/claude-skills, 28k stars) and Proposal (Chorus-AIDLC/Chorus, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openspec Propose Change?

sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

Source: sillsdev/FieldWorks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.