openspec-propose

Generates complete OpenSpec change proposals with specs, design, and tasks artifacts.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-propose-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-propose
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-propose-javakishore-veleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a structured, reviewable implementation plan requires writing proposals, specs, design docs, and task lists by hand. This Skill automates that entire planning phase through the OpenSpec CLI, producing all required artifacts in one guided workflow. ## Core Features & Use Cases - One-Step Proposal Generation: Creates a change directory and generates every required artifact (proposal.md, specs, design.md, tasks.md) in dependency order. - Schema-Aware Planning: Uses the configured OpenSpec workflow schema or an explicitly requested one, following each artifact's authoritative instructions and templates. - Store Support: Works with registered OpenSpec stores via --store flags, or falls back to the nearest local openspec/ root. - Use Case: Describe "add user authentication" and receive a complete, validated planning package with proposal, capability spec deltas, design decisions, and implementation tasks ready for review. ## Quick Start Ask the assistant to propose a new change, for example: "Propose a change to add user authentication to the app."

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I create an OpenSpec change proposal?

Describe what you want to build and the Skill derives a kebab-case change name, runs `openspec new change`, then generates every required artifact in dependency order. It uses `openspec status` and `openspec instructions` to follow the configured schema.

What artifacts does an OpenSpec proposal include?

With the default spec-driven schema it creates proposal.md (what and why), spec deltas under specs/<capability-path>/spec.md, design.md (how), and tasks.md (implementation steps). The exact set is determined by the schema's dependency graph.

Does this Skill implement the change after planning?

No. The workflow is strictly limited to planning artifacts and explicitly stops after presenting them. Implementation requires a separate, explicit user request that starts the apply workflow.

Can I use OpenSpec with a registered store instead of a local repo?

Yes. Run `openspec store list --json` to discover store ids, then the Skill appends `--store <id>` to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

What happens if a change with the same name already exists?

The Skill asks whether you want to continue the existing change or create a new one before proceeding, avoiding accidental overwrites of in-progress planning work.