sddl-proposal

Generates a lightweight proposal.md framing problem, scope, and feasibility for spec-driven changes.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sddl-proposal-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sddl-proposal
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-lite/skills/sddl-proposal
Command: npx skills add https://github.com/nico0695/ai-tools --skill sddl-proposal-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns vague or broad change requests into a structured, lightweight proposal artifact before any formal specification work begins, preventing wasted effort on poorly framed ideas. ## Core Features & Use Cases - Problem Framing: Consolidates the user's idea into a proposal.md with problem statement, desired outcome, initial scope sketch, and feasibility signal. - Readiness Gates: Runs contradiction, insufficient-context, and ambiguous-framing gates with severity levels, asking the user at most five targeted questions when framing is unsafe. - Lightweight Exploration: Optionally scans up to 10 high-signal repo files when the request lacks context, and recommends deep exploration only for blocking unknowns. - Use Case: A user says "improve authentication" in a repo. The skill scans key files, frames the problem, sketches likely in/out of scope, records open questions, and writes proposal.md plus state.yaml so the spec stage can proceed without guessing. ## Quick Start Ask the sddl orchestrator to start a new change, and it will route your idea through this proposal stage to produce proposal.md and state.yaml.

Frequently Asked Questions about sddl-proposal

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

FAQPage Schema
How do I turn a vague feature request into a structured proposal?▼

Run the proposal stage with the raw request; it frames the problem, desired outcome, and scope sketch, then writes proposal.md. If the request is too vague, it performs a lightweight scan of up to 10 high-signal repo files before framing.

What is a readiness gate in spec-driven development?▼

A readiness gate is a check run before writing the proposal artifact. This stage evaluates contradiction, insufficient context, and ambiguous framing gates, recording each verdict with a severity so downstream stages know whether the change is safe to formalize.

When does the proposal stage ask the user questions?▼

It asks only when an answer would change the problem framing, scope sketch, or route safety. Questions are delivered once as a single block of at most five, each explaining why it matters, and skipped questions become open questions for the spec stage.

Does the proposal stage write spec or design documents?▼

No. It writes only proposal.md and state.yaml inside the change directory. Formal scope boundaries and acceptance criteria belong to the spec stage, and technical design belongs to the design stage.

What happens if a change is blocked during proposal framing?▼

The stage still writes proposal.md and state.yaml recording what was asked, what remains unresolved, and the gate verdicts. This write invariant makes an interrupted change resumable from disk rather than from chat memory.