sdd-propose

Generate structured change proposals as proposal.md files with intent, scope, and risks.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-propose-eduardojvn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/EduardoJVN/my-ia-config/tree/main/.claude/skills/sdd-propose
Command: npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-propose-eduardojvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of structured change proposals, ensuring all necessary components like intent, scope, and approach are clearly defined.

Core Features & Use Cases

  • Structured Proposal Generation: Creates proposal.md files within a specified change directory.
  • Intent, Scope, Approach Definition: Guides the user to articulate the problem, deliverables, and technical solution.
  • Use Case: When a new feature is conceived, this Skill helps formalize the plan by generating a proposal document that can be reviewed by stakeholders.

Quick Start

Use the sdd-propose skill to create a proposal for the change named 'add-user-authentication'.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema
How do I create a structured change proposal for a new software feature?

Generate a structured change proposal by defining the intent, scope, approach, affected areas, risks, and rollback plans. This process formalizes software development changes by creating a proposal.md document within a specified change directory for stakeholder review.

What should be included in software development change documentation?

Change documentation should include the problem intent, deliverables scope, technical approach, affected areas, potential risks, and rollback plans. Integrating existing project specifications ensures comprehensive change tracking and formalization.

How do I formalize a technical plan for stakeholder review?

Formalize a technical plan by generating a proposal.md file that articulates the problem, deliverables, and technical solution. This structured document facilitates stakeholder review by explicitly outlining the approach, risks, and rollback strategies.

Can I integrate existing project specifications into a new change proposal?

Yes, existing project specifications can be integrated into a new change proposal. The proposal generation process supports project configuration and specification integration to produce comprehensive, context-aware change documentation.

What is the best way to document rollback plans and risks for software changes?

Document rollback plans and risks within a structured change proposal. By generating a proposal.md file, you systematically outline potential risks and rollback strategies alongside the intent, scope, and technical approach for comprehensive change management.

Do I need a specific framework to generate a change proposal document?

No external framework dependencies are required to generate a change proposal document. The process creates a proposal.md file within a specified change directory, relying on your project configuration and existing specifications rather than external dependencies.