sdd-propose

Generate structured technical change proposals in standardized markdown format.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill sdd-propose-luisalbertomk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/LuisAlbertoMK/gentleman-agent-gh/tree/main/internal/assets/skills/sdd-propose
Command: npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill sdd-propose-luisalbertomk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity and lack of alignment in software development by enforcing a structured, outcome-first proposal process that bridges the gap between intent and implementation.

Core Features & Use Cases

  • Structured Proposal Generation: Automatically creates a standardized proposal.md document covering intent, scope, capabilities, and risks.
  • Interactive Shaping: Guides the user through a question round to uncover business rules, edge cases, and product tradeoffs before finalizing the plan.
  • Multi-Mode Persistence: Supports flexible storage strategies including Engram, OpenSpec filesystem structures, or hybrid approaches to fit existing project workflows.

Quick Start

Invoke the sdd-propose skill to initiate a new change proposal for the requested feature and guide me through the interactive shaping questions.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema
How do I structure a technical change proposal for software engineering?▼

To structure a technical change proposal, generate a standardized markdown document defining intent, scope, capabilities, and risks while ensuring alignment through interactive questioning.

What is spec-driven development and how does it handle architectural documentation?▼

Spec-driven development enforces an outcome-first proposal process that bridges intent and implementation by synthesizing requirements into structured architectural documentation with risk and rollback planning.

How do I define the technical scope and approach before starting implementation?▼

Define the technical scope and approach by synthesizing exploration analysis and user requirements into a proposal.md, guiding users through questions to uncover business rules and product tradeoffs.

Can I use this proposal generation workflow with existing filesystem structures?▼

Yes, the proposal workflow supports flexible storage strategies including Engram, OpenSpec filesystem structures, or hybrid approaches to fit existing project workflows and persistence requirements.

Do I need to prepare exploration analysis before generating a technical proposal?▼

Yes, you need to provide exploration analysis and user requirements beforehand, as the proposal generation synthesizes these inputs into a standardized markdown format for architectural alignment.

What's the best way to manage rollback planning within a specification workflow?▼

Manage rollback planning within a specification workflow by enforcing a structured proposal process that mandates risk assessment and rollback strategies alongside technical approach documentation.