openspec-new-change — community openspec-new-change, vscode-open-in-marked2, community, ide skills, Claude Code, Cursor, Windsurf

v1.0
GitHub

About this Skill

Ideal for Developer Agents requiring seamless Markdown and AsciiDoc file handling in VS Code with Marked 2 integration. VS Code extension to open Markdown and AsciiDoc files in Marked 2

gAmUssA gAmUssA
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The openspec-new-change skill by gAmUssA is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Developer Agents requiring seamless Markdown and AsciiDoc file handling in VS Code with Marked 2 integration.

Core Value

Empowers agents to initiate new changes using the experimental artifact-driven approach, leveraging Markdown and AsciiDoc files, and streamlining development workflows with VS Code extensions and Marked 2.

↓ Capabilities Granted for openspec-new-change

Automating Markdown file openings in Marked 2
Generating kebab-case change names from user descriptions
Initiating new changes with artifact-driven approaches in VS Code

! Prerequisites & Limits

  • Requires VS Code and Marked 2 installation
  • Limited to Markdown and AsciiDoc file formats
  • Dependent on user input for change name or description
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

openspec-new-change

Install openspec-new-change, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

Start a new change using the experimental artifact-driven approach.

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.

  2. Determine the workflow schema

    Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

    Use a different schema only if the user mentions:

    • A specific schema name → use --schema <name>
    • "show workflows" or "what workflows" → run openspec schemas --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory

    bash
    1openspec new change "<name>"

    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.

  4. Show the artifact status

    bash
    1openspec status --change "<name>"

    This shows which artifacts need to be created and which are ready (dependencies satisfied).

  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".

    bash
    1openspec instructions <first-artifact-id> --change "<name>"

    This outputs the template and context for creating the first artifact.

  6. STOP and wait for user direction

Output

After completing the steps, summarize:

  • Change name and location
  • Schema/workflow being used and its artifact sequence
  • Current status (0/N artifacts complete)
  • The template for the first artifact
  • Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

  • Do NOT create any artifacts yet - just show the instructions
  • Do NOT advance beyond showing the first artifact template
  • If the name is invalid (not kebab-case), ask for a valid name
  • If a change with that name already exists, suggest continuing that change instead
  • Pass --schema if using a non-default workflow

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is openspec-new-change?

Ideal for Developer Agents requiring seamless Markdown and AsciiDoc file handling in VS Code with Marked 2 integration. VS Code extension to open Markdown and AsciiDoc files in Marked 2

How do I install openspec-new-change?

Run the command: npx killer-skills add gAmUssA/vscode-open-in-marked2. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for openspec-new-change?

Key use cases include: Automating Markdown file openings in Marked 2, Generating kebab-case change names from user descriptions, Initiating new changes with artifact-driven approaches in VS Code.

Which IDEs are compatible with openspec-new-change?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for openspec-new-change?

Requires VS Code and Marked 2 installation. Limited to Markdown and AsciiDoc file formats. Dependent on user input for change name or description.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add gAmUssA/vscode-open-in-marked2. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use openspec-new-change immediately in the current project.

Related Skills

Looking for an alternative to openspec-new-change or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI