Quick guide for non-programmers
Tutorial A guided lesson. Follow it start to finish and you will have built something.
🌍 Language pair / Par de idioma
Section titled “🌍 Language pair / Par de idioma”- English: 13-quick-guide-non-programmers.md
- Español: ../es/13-guia-rapida-no-programadores.md
[!IMPORTANT] Where are these scripts? It depends on how you installed SDD:
- If you added the
spec/folder to a project you already had (the usual case), they needspec/in front:./spec/scripts/new-spec.sh …- If you created the project from scratch with the template, they are as shown:
./scripts/new-spec.sh …Run them from your project’s top folder, in a terminal.
🗣️ Friendly prompt (copy/paste)
Section titled “🗣️ Friendly prompt (copy/paste)”Using https://github.com/juanklagos/spec-driven-development-template, create everything needed to carry out my project end-to-end.My project is: [describe your project in plain language].Guide me step by step for my level and do not skip specification, plan, tasks, logbook, and validation.Who is this for:
- You are starting with SDD and want clear steps without technical overload.
Finish one clean cycle:
- idea defined
- first spec created
- first log entry written
- validations executed
- Fill
idea/IDEA_GENERAL.mdin simple language. - Create first spec:
./scripts/new-spec.sh "my-first-feature" "Owner"- Complete in
specs/001-.../:
spec.mdplan.mdtasks.mdhistory.md
- Validate:
./scripts/validate-sdd.sh . --strict./scripts/check-sdd-gate.sh .- Write session log in
bitacora/global/PROJECT_LOG.md.
Prompt pack (Beginner)
Section titled “Prompt pack (Beginner)”Prompt A: Complete idea
Section titled “Prompt A: Complete idea”Act as a beginner-friendly SDD coach.Help me complete idea/IDEA_GENERAL.md with simple language.Ask one short question at a time.Do not assume missing information.Prompt B: Create first spec
Section titled “Prompt B: Create first spec”Based on idea/IDEA_GENERAL.md, create specs/001-... with:spec.md, plan.md, tasks.md, history.md.Use clear wording and avoid unexplained abbreviations.Do not implement code.Prompt C: Pre-implementation check
Section titled “Prompt C: Pre-implementation check”Review spec.md, plan.md and tasks.md for consistency.List gaps and exact fixes before implementation.Rules you must keep
Section titled “Rules you must keep”- No code before approved
spec.md+ consistentplan.md. - If idea changes, update docs first.