Bootstrap an already-cloned starter-kit into a configured project. Use when the user says "start project", "iniciar projeto", "bootstrap project" or "inicializar projeto". Asks the 9 stack questions, fills AGENTS.md, narrows conventions.md, records ADR-003 (technology stack), and creates the bootstrap requirements + spec. Do NOT use to clone a fresh copy from GitHub — that is create-project.
Guide the user through the judgment steps after a methodology upgrade copied in new files: merge new doc sections into AGENTS.md, reconcile overwritten tooling, and adapt existing project artifacts to new/changed conventions (e.g. give a troubleshooting.md TRB ids, add traceability links). Use when the user says "reconcile upgrade", "ajustar upgrade", "ajustar arquivos da metodologia", "finalizar upgrade", "adaptar metodologia" or right after running `spec-kit upgrade` / the upgrade-methodology skill. Drives interactive edits, never git/outward-facing steps, and ends on a green check.
Drive the Red → Green → Refactor TDD cycle for an active spec, ensuring tests are written before implementation. Use when the user says "run TDD cycle", "executar TDD", "TDD", "write tests" or "escrever testes", or when implementing a spec from .specs/changes/. Reads the spec's Tests section, writes failing tests, implements, refactors against clean-code standards, and updates the spec checklist + component catalog.
Bring a project that ALREADY uses this methodology up to the starter-kit's latest version, applying only the delta non-destructively. Use when the user says "upgrade methodology", "atualizar metodologia", "sync methodology", "sincronizar metodologia", "migrar metodologia" or "update methodology" inside a repo that already has .specs/ and .claude/skills/. Version-aware: compares the project's methodology version to the kit's and adds only what is missing or outdated. Do NOT use to adopt the methodology for the first time (that is adopt-project) or to bootstrap a new project (create-project / init-project).
Validate that all skills and project conventions are structurally consistent by running the deterministic checker script. Use when the user says "check consistency", "verificar consistência", "validate skills" or "validar skills", and before committing any skill or config change. Runs scripts/check-consistency.mjs (frontmatter, sections, naming, hardcoded URLs, orphan refs, changelog coverage, troubleshooting schema, requirements↔spec traceability, alignment gate) rather than eyeballing the rules.
Append a distilled error-and-fix entry to .specs/memory/troubleshooting.md after resolving a non-trivial problem, so the fix is not re-derived later. Use when the user says "record troubleshooting", "registrar troubleshooting", "log this fix", "registrar solução" or "salvar troubleshooting", or right after debugging something that cost real investigation (a tricky bug, a build/CI failure, an environment gotcha). Compiles the durable lesson out of the incident; does not replace the per-incident bugfix-spec.
Prepare a versioned release of this project: validate version consistency, roll CHANGELOG [Unreleased] into a dated version section, and print the remaining manual tag/publish steps. Use when the user says "cut release", "cortar release", "preparar release", "fazer release" or "lançar versão". Runs scripts/cut-release.mjs (deterministic); it does NOT tag, push, merge, or publish — those outward-facing steps require explicit confirmation.
Overlay the spec-driven + TDD methodology onto an EXISTING project that already has code. Use when the user says "adopt methodology", "adotar metodologia", "add methodology" or "adicionar metodologia" inside a repo that already has a stack and source. Detects the stack (no blind questions), brings the methodology files in without overwriting anything, auto-drafts the memory docs from the real codebase, and sets a forward-only TDD coverage baseline. Do NOT use on an empty project (that is init-project) or to clone a fresh one (create-project).