specdo-propose

Create and revise SpecDo change artifacts in the specdo/changes workspace.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-propose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specdo-propose
Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-propose
Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-propose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

SpecDo Propose streamlines creating or revising formal SpecDo change artifacts under the specdo/changes workspace, enabling disciplined lifecycle transitions from proposal to design to tasks.

Core Features & Use Cases

  • Scaffold new changes with change.yaml, proposal.md, design.md, tasks.md, and delta specs.
  • Validate and classify changes to determine artifact readiness and appropriate workflow routing.
  • Route work through the lifecycle (brainstorming → explore → propose → apply) based on stability and artifact completeness.

Quick Start

Scaffold a new change with the scaffold script and then complete artifacts using the propose workflow.

Frequently Asked Questions about specdo-propose

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

FAQPage Schema
How do I scaffold a new change request with formal artifacts?

Scaffolding a new change request generates standard artifacts like change.yaml, proposal.md, design.md, tasks.md, and delta specs within the specdo/changes workspace. You initiate this with a scaffold script and then complete the artifacts using the propose workflow.

How does change classification and validation determine workflow routing?

Change validation checks artifact readiness and classifies changes to determine appropriate workflow routing. It routes work through the lifecycle from brainstorming to apply based on the stability of the proposal and the completeness of the generated artifacts.

Can I revise active changes or is this only for new proposals?

You can revise active changes. The propose workflow supports both creating new change requests and revising existing active changes, enforcing scaffold validation and delta-spec generation to maintain artifact integrity throughout the lifecycle.

What is the structured handoff process to apply changes?

The structured handoff to apply occurs after a change is validated and artifacts are complete. The propose workflow routes the finished change artifacts to specdo-apply, transitioning the work from the proposal stage into the apply stage.

Do I need any external dependencies to generate delta specs?

No external dependencies are required to generate delta specs. The propose workflow handles scaffold creation, validation, and delta-spec generation internally using its built-in scripts and references.

When should I not use the propose workflow for artifact creation?

You should not use the propose workflow if your changes do not require formal artifact tracking or lifecycle routing. It is specifically designed for disciplined transitions from proposal to design to tasks within the specdo/changes workspace.