Skip to content

Quick guide for non-programmers

Tutorial A guided lesson. Follow it start to finish and you will have built something.

[!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 need spec/ 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.

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:

  1. idea defined
  2. first spec created
  3. first log entry written
  4. validations executed
  1. Fill idea/IDEA_GENERAL.md in simple language.
  2. Create first spec:
Terminal window
./scripts/new-spec.sh "my-first-feature" "Owner"
  1. Complete in specs/001-.../:
  • spec.md
  • plan.md
  • tasks.md
  • history.md
  1. Validate:
Terminal window
./scripts/validate-sdd.sh . --strict
./scripts/check-sdd-gate.sh .
  1. Write session log in bitacora/global/PROJECT_LOG.md.
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.
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.
Review spec.md, plan.md and tasks.md for consistency.
List gaps and exact fixes before implementation.
  • No code before approved spec.md + consistent plan.md.
  • If idea changes, update docs first.