openspec-propose

Generate openspec-compliant proposal, design, and task artifacts in one step.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill openspec-propose-susomejias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-propose
Source: https://github.com/susomejias/rembric/tree/main/.opencode/skills/openspec-propose
Command: npx skills add https://github.com/susomejias/rembric --skill openspec-propose-susomejias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating structured change proposal artifacts (proposals, designs, task lists) for software development is time-consuming and prone to inconsistency, slowing down implementation planning.

Core Features & Use Cases

  • Automated Artifact Scaffolding: Generates all required openspec change artifacts in one step, including proposal.md, design.md, and tasks.md.
  • Dependency-Aware Generation: Builds artifacts in the correct order based on their dependencies to ensure completeness.
  • Use Case: A developer planning a new authentication feature can describe the change and get a full, implementation-ready proposal package without manually writing each document.

Quick Start

Describe the new feature or change you want to implement to generate a complete proposal with design and task artifacts ready for development.

Frequently Asked Questions about openspec-propose

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

FAQPage Schema
How do I generate change proposal artifacts for software development without writing them manually?

Change proposal artifacts like proposal.md, design.md, and tasks.md can be generated automatically by describing a feature, which scaffolds implementation-ready packages without manual document authoring.

What are openspec change proposal artifacts and when do I need them?

Openspec change proposal artifacts are structured documents including proposals, technical designs, and task lists needed during implementation planning to ensure teams have complete, structured change documentation before development begins.

Can I scaffold technical design and task list documents in a single step?

Yes, complete technical design and task list documents can be scaffolded in a single step using dependency-aware generation that builds all required change artifacts in the correct order based on their dependencies.

What is the best way to automate implementation planning for a new software feature?

Automating implementation planning is best done by generating complete, openspec-compliant change proposal packages at once, eliminating the time-consuming and inconsistent process of manually creating structured change documentation.

Do I need any dependencies to generate openspec-compliant change proposals?

No dependencies are required to generate openspec-compliant change proposals, allowing developers to quickly scaffold implementation-ready packages directly from a feature description without additional environment setup.

Why does manual change proposal creation slow down implementation planning?

Manual change proposal creation slows down implementation planning because writing each structured document individually is time-consuming and prone to inconsistency, delaying the availability of technical designs and task lists for development.