Welcome to the PaellaDoc community — Bienvenida

./announcements
1

Hi, I’m @jlcases. I built PaellaDoc not because other tools lie, but because as a developer the work I actually need today doesn’t fit inside an IDE plus four tmux panes.

What happens with current AI-assisted setups, in plain terms:

  • The agent declares “done” too easily. You read the diff and trust it. Three weeks later, production catches a bug nobody asked the agent about.
  • The agent writes the tests it wants to write — usually trivial unit tests that pass on the first try — and skips the tests you actually need (the end-to-end ones that prove your acceptance criteria are met).
  • You end up doing the validation work yourself, manually, late at night. It ends up eating most of the time you thought you were saving.

PaellaDoc is built around that asymmetry. The orchestrator’s job isn’t to write more code, faster. It’s to make the validation layer native to the workflow: every acceptance criterion closes with real Playwright e2e against your dev server, evidence captured to disk, status only flips to done when the evidence exists and passes.

The agent doesn’t decide closure. The gate does.

What this forum is for

  • Onboarding by persona: you have a repo (./dev-con-repo), you start from scratch (./desde-cero), you define product, not code (./product-manager), you don’t write code (./no-coder). Each has its own home.
  • Validation engine: how the Golden Gate works, edge cases, how to debug it (./golden-gate).
  • Method packs: extending the canonical vocabulary — PRD, epic, user story, AC, decision record (./method-packs).
  • Engines: setup, switching between Claude Code, Codex, Gemini, troubleshooting (./engines).
  • Show & Tell: what you built. Include evidence — screenshots, video, or the .paella file (./show-and-tell).
  • Help: when something doesn’t work (./help).

House rules

  1. Languages: the forum auto-translates EN ↔ ES. Write in whichever feels natural.
  2. Evidence beats opinion. Bug reports without logs get closed. Show & Tell without a screenshot or .paella gets closed.
  3. No marketing. This is a builders’ forum, not a launch board.
  4. Be specific. “It doesn’t work” gets no replies. “Reverse-intake fails on macOS 14.3 with a Python monorepo that has 4 packages” gets answers.

Posts will be sparse at first. That’s normal. I read everything.