SkillGild
Development

OpenSpec Propose

Turn a feature request into an OpenSpec change before any code is written: proposal, delta specs, design and implementation tasks, grounded in the project's existing specs.

  • 25 free runs a month
  • Runs in your agent, private tools on SkillGild
  • v1.1.0
skillgild install openspec-propose
Works with
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
and any MCP client

License: MIT · Created by Fission AI

Install and connect

Pick your agent. The wrapper only tells your agent how to start a session. The skill's instructions arrive with each session, after your access is checked.

  1. Sign in once from your terminal.

    Terminal
    skillgild login
  2. Install this skill for Claude Code.

    Terminal
    skillgild install openspec-propose --agent claude-code
  3. Register the SkillGild MCP server with Claude Code.

    Terminal
    claude mcp add --scope user skillgild -- $(command -v skillgild) mcp

How it runs

  1. Your agent starts a session. SkillGild checks your access and allowance, counts one run, and sends the skill's instructions for this task.
  2. Your agent does the work with its own model and tools, in your project. SkillGild makes no AI model call.
  3. Private steps run on SkillGild. Your agent calls the server tools below and gets their results. The tool code never leaves SkillGild, and tool input is not stored.

Use it from code

Start a session, call its tools, then end it. Create an API key under Account and pass it as a bearer token.

Terminal
# Prints the session ID, its tools and the instructions for your agent
skillgild session openspec-propose
skillgild call <session-id> validate_change --input '{"data": {}}'
skillgild end <session-id>

Server tools

Each call uses one of the session's tool calls.

validate_changeValidate an OpenSpec change

Checks a proposed OpenSpec change the way `openspec validate` does: change name, the proposal's Why and What Changes sections, delta spec sections (ADDED/MODIFIED/REMOVED/RENAMED Requirements), SHALL/MUST requirement text, scenarios and task checkboxes. Checks structure only; it does not read the project or judge whether the plan is right.

FieldTypeNotes
change_nameRequiredstringUp to 120 characters
specsRequiredarrayNo extra rules.
proposalstringUp to 60000 characters
skip_specsbooleanNo extra rules.
tasksstringUp to 60000 characters