skills.rest
zabuuq
zabuuqCOMMUNITY
Explore all skills by this author →
GitHub

sdd-guide

Enforce interview-driven behavior and validation across SDD plugin workflows.

Updated Apr 9, 2026
Search Tags:#state management#spec-driven development#planning automation#interview workflow#resume and handoff#command guardrails#process notes
One-click install
npx skills add https://github.com/zabuuq/sdd-plugin --skill sdd-guide-zabuuq
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: sdd-guide
Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/sdd-guide
Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill sdd-guide-zabuuq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

sdd-guide standardizes how the SDD plugin conducts interviews and produces planning outputs, preventing drift, messy prompting, and accidental rule-breaking by enforcing tone, question cadence, validation checks, and handoff behavior.

Core Features & Use Cases

  • Tone control via user profile: adopts the user's communicationStyle from ~/.claude/sdd-user-profile.json (set during /sdd:onboard) or falls back to a direct, collegial-product-manager default.
  • Interview discipline and safety rules: asks one open-ended question at a time, keeps deepening adaptive, prevents clarifying questions from advancing the interview, and always pauses for an explicit user invitation at the end of each beat/topic.
  • Operational guard rails for every command: performs prerequisite and structure validation before real work; blocks execution and directs the user to the correct command if required artifacts are missing or invalid.
  • Deterministic state and lifecycle management: updates docs/project-state.json lastCommand, manages handoff messaging and /clear /compact recommendations, and ensures resume behavior via docs/<command>-resume.md.
  • Process-note rigor: specifies append-only process note files per phase and sprint, plus how /sdd:retro reviews and synthesizes outcomes.

Quick Start

Open a new SDD project flow by running /sdd:onboard, then follow the next-command prompts that sdd-guide enforces.

Frequently Asked Questions about sdd-guide

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

FAQPage Schema
What is spec-driven development and how does interview workflow automation keep it on track?â–¼

Spec-driven development structures planning through sequential interviews. Interview workflow automation enforces one open-ended question at a time, checks prerequisites, and pauses for explicit user input to prevent prompt drift and accidental rule-breaking during planning.

How do I start a spec-driven development project using planning automation?â–¼

Start spec-driven development by running /sdd:onboard to configure your user profile. Planning automation then directs you through subsequent commands, validating required artifacts before proceeding and managing deterministic resume behavior via state tracking.

Can I use state management to safely pause and resume an interview workflow across sessions?â–¼

Yes, state management enables deterministic resume behavior by tracking the last command in project-state.json and generating resume files. This ensures interview workflows pause cleanly and resume accurately after /clear or /compact handoffs.

How does command guardrail validation prevent errors during spec-driven development?â–¼

Command guardrails validate required artifacts and structure before executing real work. If prerequisites are missing or invalid, the system blocks execution and directs the user to the correct command, preventing messy prompting and accidental rule-breaking.

Why must process notes be append-only during spec-driven development sprints?â–¼

Append-only process notes maintain a rigorous, unalterable history per phase and sprint. This prevents state drift and allows retrospective reviews to accurately synthesize outcomes without losing prior context or overwriting critical decisions.

Does spec-driven development require specific files for tone control and user profiling?â–¼

Tone control requires ~/.claude/sdd-user-profile.json, set during onboarding. If absent, the system falls back to a direct, collegial-product-manager default, ensuring consistent communication style across all interview-driven planning commands.

Related Skills

Explore More Product & Management Skills→
zabuuqzabuuq

onboard

Create or update an SDD user profile with communication and git preferences.

Community
Intermediate
zabuuqzabuuq

retro

Synthesize sprint notes and artifacts into a project retrospective document.

Community
Advanced
zabuuqzabuuq

feedback

Record sprint feedback notes to docs/sdd-feedback.md for the SDD plugin.

Community
Intermediate
LYKOS68LYKOS68

prompt-engineering-system

Orchestrate LLM prompt generation, validation, and calibration via PROMPT_PACK and META-KERN-PROMPT.

Community
Advanced