sdd-proposal

Create and refine change proposals within the SDD workflow.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Akiyama-sama/SDD-WorkSpace --skill sdd-proposal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-proposal
Source: https://github.com/Akiyama-sama/SDD-WorkSpace/tree/main/.agents/skills/sdd-proposal
Command: npx skills add https://github.com/Akiyama-sama/SDD-WorkSpace --skill sdd-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables users to effectively capture and refine change proposals within the repository's SDD workflow, facilitating structured communication and collaboration.

Core Features & Use Cases

  • Capture Proposals: Record change proposals clearly and concisely.
  • Refine Proposals: Edit and improve proposals before they are implemented.
  • Use Case: When planning a new feature, use this Skill to document the proposal, including its objectives, constraints, and expected outcomes.

Quick Start

To create a new change proposal for a feature, type /sdd proposal new FeatureName and follow the on-screen prompts.

Frequently Asked Questions about sdd-proposal

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

FAQPage Schema
What is the best way to document feature requests for project planning?

The best way to document feature requests is using structured change proposals to capture objectives, constraints, and expected outcomes. This ensures clarity and consistency in project documentation while facilitating effective communication during requirements gathering.

How do I create a new change proposal within the SDD workflow?

To create a change proposal within the SDD workflow, type the proposal command with your feature name and follow the on-screen prompts. This structured creation process helps record proposals clearly and concisely for project planning.

Can I refine and edit requirements before they are implemented?

Yes, you can refine and edit requirements before implementation. The proposal workflow allows you to improve change proposals, ensuring constraints and expected outcomes are clearly documented and communicated prior to final project execution.

When do I need structured change proposals for software engineering?

You need structured change proposals when planning new features or gathering requirements in software engineering. They maintain clarity and consistency in project documentation by capturing objectives, constraints, and expected outcomes before any code implementation begins.

Does the SDD proposal workflow require any external dependencies?

The SDD proposal workflow does not require external dependencies. It operates independently to facilitate structured communication and collaboration, relying entirely on its internal scripts to capture and refine your project documentation.

Why should I use a structured workflow for requirements gathering instead of plain text?

A structured workflow for requirements gathering maintains consistency and clarity in project documentation. Unlike plain text, it enforces the capture of objectives, constraints, and expected outcomes, facilitating better communication and collaboration across the team.