Skip to content
SDD TemplateSDD TemplateSDD Template

Legal framework and commercial use

Reference Facts to consult while you work. Not meant to be read end to end.

🌍 Language pair / Par de idioma

Section titled “🌍 Language pair / Par de idioma”

🗣️ Friendly prompt (copy/paste)

Section titled “🗣️ Friendly prompt (copy/paste)”

Use this when you are not technical and want the AI to do setup + guidance end-to-end:

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].


If my project is new, initialize it with this template and GitHub Spec Kit.
If my project already exists, adapt it to idea/specs/bitacora without breaking current behavior.
Guide me step by step for my level (beginner/intermediate/advanced), using simple language.
Do not skip specification, plan, tasks, refinement trace, logbook, and validation.

This document summarizes the licensing terms. For complete legal language, refer to the root-level legal documents.

Project licensing status

Section titled “Project licensing status”

This repository is licensed under the MIT License. It is OSI-approved open source.

Aspect Detail
License MIT
OSI open-source ✅ Yes
Commercial use ✅ Allowed, free, no permission needed
Copyright holder Juan Carlos Alvarez Lagos

What you may do

Section titled “What you may do”

Everything below is permitted, costs nothing, and requires no notice to anyone.

Use case Allowed? Notes
Personal learning and experimentation ✅ Yes
Academic and educational use ✅ Yes Classroom, workshops, research
Use inside a company, at any scale ✅ Yes Including in your team’s CI
Building a paid product or SaaS on it ✅ Yes Sell what you build
Selling it, hosting it, white-labeling it ✅ Yes Rename it if you want
Including it in a paid course or training ✅ Yes
Using it in an open-source project ✅ Yes MIT is compatible with every common license
Forking it and shipping under your own brand ✅ Yes See the naming page below
Contributing back to this repository ✅ Yes Under the CLA terms (see below)

The one condition

Section titled “The one condition”

Keep the copyright notice. The MIT License requires the notice in LICENSE to travel with copies and substantial portions of the software. That is the whole obligation.

Two things are about identity rather than code, and they are not license conditions: do not present a fork as officially endorsed by the author, and do not publish under his name, handle, npm scope or MCP namespace. Forking and renaming are expressly permitted.

Section titled “Legal documents in this repository”
Document Purpose
LICENSE Full MIT License text
NOTICE Courtesy attribution notice
TEMPLATE-OUTPUT.md The documents you write with the templates are yours
COMMERCIAL_SUPPORT.md Optional paid support. Nothing to buy for normal use
DISCLAIMER.md Warranty and liability disclaimer
TRADEMARK_POLICY.md Names and accounts. What is claimed and what is permitted
ENFORCEMENT.md How to report stripped attribution or misused identity
CLA.md Contributor License Agreement
LEGAL_OVERVIEW.md Summary of all legal documents

Contributor License Agreement (CLA)

Section titled “Contributor License Agreement (CLA)”

By contributing to this repository, you agree to the CLA terms in legal/CLA.md. Key points:

  • You retain copyright of your contributions
  • You grant the project a broad, perpetual license to use your contributions
  • You certify that your contributions are your original work

⚠️ Important note

Section titled “⚠️ Important note”

[!WARNING] This document is informational only and does not constitute legal advice. For binding terms, refer to the actual license text in LICENSE. When in doubt, consult a lawyer.