source-command-opsx-propose

Creates OpenSpec change proposals with proposal, design, and tasks artifacts in one workflow.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-propose-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-opsx-propose
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.agents/skills/source-command-opsx-propose
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill source-command-opsx-propose-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new spec-driven change requires manually scaffolding directories, writing proposal, design, and task documents, and keeping them consistent with project standards. This Skill automates the entire OpenSpec change proposal flow in a single step. ## Core Features & Use Cases - One-Step Change Creation: Runs openspec new change and generates all required artifacts (proposal.md, design.md, tasks.md) in dependency order until the change is apply-ready. - Automated Requirement Enrichment: Spawns an Opus subagent that applies the enrich-us workflow to expand a rough user description into a full functional analysis before writing artifacts. - Optional Jira Integration: Detects KAN-style ticket keys, links them to the change via a .jira file, and transitions the ticket to "En curso" using the Jira REST API or an MCP comment fallback. - Use Case: A developer types /opsx:propose add-supplier-orders and receives a fully scaffolded OpenSpec change with standards-compliant proposal, design, and tasks files, ready for implementation via /opsx:apply. ## Quick Start Ask the assistant to run /opsx:propose followed by a kebab-case change name or a description of what you want to build.

Frequently Asked Questions about source-command-opsx-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenSpec change proposal in one step?▼

Run /opsx:propose with a kebab-case change name or a plain description of what you want to build. The skill scaffolds the change with the openspec CLI and generates proposal.md, design.md, and tasks.md in dependency order until the change is apply-ready.

What artifacts does the opsx propose workflow generate?▼

It generates the artifacts required by the OpenSpec schema before implementation, typically proposal.md (what and why), design.md (how), and tasks.md (implementation steps). The exact set is determined by the applyRequires field returned by openspec status.

Does the propose workflow integrate with Jira tickets?▼

Yes, optionally. If a ticket key matching KAN-<number> appears in context, the skill saves it to a .jira file in the change directory and transitions the ticket to "En curso" via the Jira REST API, falling back to an MCP comment if credentials are missing.

What happens if I run opsx propose without a change name?▼

The skill asks what you want to build using an open-ended question, then derives a kebab-case name from your description. It does not proceed until it understands the intended change.

Why does the propose step spawn a subagent before writing artifacts?▼

The subagent runs the enrich-us workflow on Opus to expand a rough request into a functional analysis and enhanced specification. This enriched output becomes the definitive input for the proposal, design, and tasks artifacts.