starter-kit

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

Print a "where you left off" summary of the project's spec-driven state — the latest working-log entry, specs in flight (with their alignment-gate status), and requirements without a spec yet. Use when the user says "where did I leave off", "onde paramos", "resume session", "retomar sessão", "where were we" or at the start of a work session to regain context. Runs scripts/session-context.mjs; the same script is auto-injected by the Claude Code SessionStart hook.

Create a new, standardized skill discoverable by both opencode and Claude Code. Use when the user says "create skill", "criar skill", "add skill" or "adicionar skill". Produces a .claude/skills/<name>/SKILL.md with valid YAML frontmatter (name + description) and the 6 canonical body sections, then validates it with check-consistency.

Semantically check that a spec faithfully covers its requirements document — catching omissions, contradictions, and scope drift that the deterministic check-consistency script cannot see. Use when the user says "review alignment", "revisar alinhamento", "check spec alignment", "verificar spec", "validar spec contra requisitos", or at the requirements→spec transition before run-tdd and before archiving. Produces an alignment-review.md verdict that the consistency gate enforces.

One-shot bootstrap of a brand-new project from the starter-kit: clone from GitHub, clean git history, then run the full init-project flow. Use when the user says "create new project", "criar novo projeto", "start from scratch" or "começar do zero". Delegates stack configuration to the init-project skill — it does NOT duplicate those steps.

Guide requirements elicitation from a raw idea to a structured requirements document. Use when the user says "gather requirements", "levantar requisitos", "elicit requirements" or "elicitar requisitos", or before writing a spec for a non-trivial feature. Supports User Stories, Use Cases, Job Stories and BDD, and writes to .specs/requirements/<nnn>-<slug>/. For trivial changes (typo, refactor, dependency bump, simple bugfix) skip this and use the run-change fast-path instead.

Decide the right ceremony for a change and run the lightweight path for trivial work. Use when the user says "run change", "fazer mudança", "quick change" or "mudança rápida", or asks for a small edit (typo, refactor, dependency bump, simple bugfix) where full requirements elicitation would be overkill. Routes non-trivial work to gather-requirements + the full spec flow instead.

Generate CHANGELOG.md entries from archived specs by running the changelog script. Use when the user says "update changelog", "atualizar changelog", "generate changelog" or "gerar changelog", typically right after a spec is moved to .specs/archive/. Runs scripts/update-changelog.mjs, which is idempotent (skips specs already in the changelog) — no manual writing.