Generate proposal, design, and task artifacts from a change description.
npx skills add https://github.com/Valynt/ValueOS --skill openspec-propose-valynt
Please help me install this Agent Skill. Skill: openspec-propose Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/openspec-propose Command: npx skills add https://github.com/Valynt/ValueOS --skill openspec-propose-valynt
Propose a new change and generate all required artifacts in a single, streamlined workflow, eliminating manual drafting of proposals, designs, and task lists.
Describe the desired change and run openspec new change <name> to generate the complete proposal, design, and task artifacts.
High-intent search queries and answers about installing and using this skill.
To generate a change proposal in one step, describe the desired change and run the command to automatically scaffold proposal.md, design.md, and tasks.md files from your input.
Standardizing change proposals is done by automatically scaffolding proposal.md, design.md, and tasks.md from a user description, enforcing a standardized structure to accelerate review and implementation.
Yes, you can outline scope, design, and tasks by providing a text description of the desired change, which the tool uses to automatically scaffold the complete proposal, design, and task artifacts.
Yes, OpenSpec tooling is required to create change management artifacts, as the workflow relies on it to generate the required proposal, design, and task files from user input.
Manually drafting a design document is unnecessary because the workflow automatically scaffolds proposal.md, design.md, and tasks.md from a user description, eliminating manual drafting of proposals, designs, and task lists.
You need to scaffold proposal, design, and tasks files when you want to rapidly align stakeholders on scope and plan for a new change across product, engineering, and project-management contexts.
mrclrchtrGenerate OpenSpec change artifacts in dependency order using the openspec CLI.
QuafadasGenerate proposal.md, design.md, and tasks.md for openspec changes.
LippyyDevScaffold OpenSpec changes with naming conventions and artifact sequencing.
t-udaGenerate a compact execution spec with Task, Goal, Scope, and Done criteria.
