sdd-help

Answers questions about the Specification-Driven Development process, artifacts, roles, and skill commands.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-help-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-help
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/sdd-team/skills/sdd-help
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-help-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams adopting Specification-Driven Development often lose track of which artifact to create next, what each document should contain, or which agent and command fits their current situation. This Skill acts as a read-only knowledge guide that explains the SDD workflow and recommends the next step based on the actual state of your project. ## Core Features & Use Cases - Process & Artifact Reference: Loads detailed reference files explaining the full 7-stage SDD lifecycle, every artifact type (PRD, UX, architecture, proposal, design, tasks, specs), team roles, and all skill commands. - State-Aware Guidance: Inspects your artifact folder to detect which documents exist and recommends the exact next command, such as running the proposal or implementation step. - Use Case: You return to a project after a week and forget where you left off. Ask what to do next, and the Skill checks which SDD documents exist, then tells you whether to propose a change, continue implementation, verify, or archive. ## Quick Start Ask the sdd-help skill what the next SDD step is for my project based on the current artifacts folder.

Frequently Asked Questions about sdd-help

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

FAQPage Schema
How do I learn the Specification-Driven Development process?▼

Use the sdd-help skill with a topic like process, artifacts, roles, or skills to load detailed reference explanations. Running it with no argument shows an overview and a navigation menu for exploring each topic.

How do I know which SDD command to run next?▼

Ask sdd-help what's next and it inspects your artifacts folder for prd.md, ux.md, architecture.md, and active changes. Based on what exists, it recommends the exact next command such as propose, implement, verify, or archive.

What artifacts does a spec-driven development workflow use?▼

SDD uses shared documents (prd.md, ux.md, architecture.md), per-change artifacts (proposal.md, design.md, tasks.md), and capability specs under specs/<name>/spec.md. The artifacts reference file explains each document's purpose and sections.

Can sdd-help create or edit SDD documents?▼

No, sdd-help is strictly read-only and never creates, modifies, or deletes files. To create or update documents it directs you to the appropriate skill command such as sdd-prd, sdd-propose, or sdd-implement.

Which agent should I use for each SDD task?▼

The roles reference maps agents to tasks: sdd-pm for PRD and proposals, sdd-architect for architecture, sdd-dev for implementation and verification, and sdd-ux for design and prototyping.