openspec-propose

Generate OpenSpec change artifacts from feature requests or bug descriptions.

15|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-propose-mahoushoujyo-eee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/mahoushoujyo-eee/eshell/tree/main/.codex/skills/openspec-propose
Command: npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-propose-mahoushoujyo-eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the overhead of manually structuring a software change proposal by turning a feature request or bug description into a complete, implementation-ready set of artifacts.

Core Features & Use Cases

  • Change Scaffolding: Creates a new OpenSpec change directory with the required project metadata.
  • Artifact Generation: Produces proposal, design, and task artifacts in dependency order using the OpenSpec schema and project context.
  • Workflow Validation: Checks artifact status, reads dependencies, verifies generated files, and confirms that the change is ready for implementation.
  • Use Case: When a team wants to add a new feature, describe the desired outcome and receive a coordinated proposal, technical design, and implementation task list ready for execution.

Quick Start

Use the openspec-propose skill to turn my request for a new feature or fix into a complete proposal with design and implementation tasks.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
What is OpenSpec change scaffolding and how does it structure technical designs?

Generating implementation task lists requires user clarification when the requested change lacks sufficient detail, ensuring the final proposal, technical design, and task list are fully structured for execution readiness.

Do I need the OpenSpec CLI to create dependency-aware artifacts?

Yes, you need the OpenSpec CLI to create dependency-aware artifacts and perform workflow validation, which checks artifact status, reads dependencies, verifies generated files, and confirms implementation readiness.

How do I check if a change proposal is ready for implementation?

To check if a change proposal is ready for implementation, the workflow validation process verifies generated files, reads dependencies, checks artifact status, and confirms the change is fully prepared for execution.

What is the best way to structure implementation tasks for a new software feature?

The best way to structure implementation tasks is to generate them in dependency order using the OpenSpec schema, ensuring the technical design and proposal artifacts are coordinated and ready for team execution.