elucas.dev

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

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) rather than eyeballing the rules.

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.

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.

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.

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.

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.

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.