← all publishers

jebauza

@jebauza source repo

6 published skills

  1. Spec · jebauza bundle
    Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.
    0 installs
  2. Spec Impl · jebauza
    Implements an approved spec. Validates that the state means "Approved" (in any language), creates a git branch named after the spec, switches to it, and starts the implementation step by step with pauses to review diffs.
    0 installs
  3. Worktree Merge · jebauza
    Closes a spec implemented with /worktree-spec-impl. Run from the primary checkout, on the spec's base branch (develop, a task branch, main…). Verifies the branch already contains its base and is clean, fast-forwards the base to it, runs the checks, and cleans up the worktree, its database and its port. Integrates one branch at a time. Never pushes.
    0 installs
  4. Worktree Doctor · jebauza
    Read-only diagnostic to run once on a new machine or project, before /worktree-spec-impl. Reports what will work and what will not (node/git versions, package manager, .trees/ ignored, database reachability and CREATEDB permission, detected port and database variables, hardlink support, Windows long paths) without creating anything permanent.
    0 installs
  5. Worktree Spec Impl · jebauza bundle
    Implements an approved spec in an isolated git worktree so several agents can work in parallel. Validates that the state means "Approved" (in any language), creates .trees/spec-NN-slug from the current branch (develop, a task branch, main… or --base), bootstraps it (ignored files, node_modules, own port and database), implements step by step with pauses to review diffs, and finally merges the base branch into the spec's branch resolving conflicts so it is ready for /worktree-merge.
    0 installs
  6. Node Clean Architecture · jebauza bundle
    Arquitectura por capas escalable para backends Node.js/TypeScript/JavaScript (domain/infrastructure/presentation, entidades, repositorios abstractos, datasources intercambiables por tecnología), con catálogo de patrones de diseño, seguridad de API y tests unitarios. Úsala al diseñar o implementar un backend Node nuevo (o un feature nuevo en uno existente), y también cuando el usuario pida mejorar, refactorizar o migrar la arquitectura de un proyecto backend existente hacia algo más escalable ("mejora la arquitectura", "migra esto a algo más limpio/escalable", "este proyecto tiene una arquitectura poco escalable").
    0 installs