jandrescodes/sdd
Complete Spec-Driven Development flow as portable skills for GitHub Copilot.
Use this skill when the user wants a project document built from the SDD artifacts — in any language they ask in ("generate the PRD", "write the technical doc", "acceptance record for this feature", "change log for the client", "update the schema doc", "genera el PRD", "acta de aceptación", "documento de cambios", "paquete de entrega", "documento de entrega", "flujo de la app", "diagrama de flujo", "brief de UX"). Derives PRD, TRD, acceptance record, scope change log, delivery package, schema, app flow, and UX brief from the existing specs, plans, and validations, after the user approves a proposal. Whatever the artifacts do not state is left as a marked gap, never invented.
Use this skill when the user wants to start or drive a project with Spec-Driven Development (SDD) — in any language they ask in ("start a project with SDD", "spec-driven flow", "do it phase by phase with a spec", "empezar con SDD", "flujo spec-driven"). Explains the 8 phases, which artifact each one leaves, and which slash command runs it, plus the cross-cutting /sdd:docs command, and brings the base templates to copy into the project.
Use this skill when the user asks to create, write, or review a feature specification (spec), in any language they address you in. Guides a one-question-at-a-time requirements interview and produces a spec.md with EARS-notation requirements following the included template.