browzer-marketplace

AI agent skills to empower it with Browzer — hybrid vector + Graph RAG for codebases and document workspaces. Skills around the `browzer` CLI: RAG (embed-workspace-graphs, embed-documents, explore-workspace-graphs, semantic-search, dependency-graph, ingestion-jobs), a tier-aware workflow (brainstorming → probe-tier → generate-prd → scope-feature → generate-task → execute-task → code-review → receiving-code-review → regression-guard → feature-acceptance → finalize-feature → commit), orchestration (orchestrate-task-delivery picks `tier ∈ {express, standard, full}` via haiku probe at Step 0.5; express skips PRD/scope/task-plan and inline-writes a single TASK_01.md), ops (auth-status, workspace-management), and tools (use-rag-cli, browzer-bootstraper, find-skills). State lives as plain markdown under `docs/browzer/<feat>/staging/` (six per-phase subfolders: planning/, tasks/, review/, review-lanes/, fixes/, acceptance/); only README.md at the feat root is committed. Code-review spawns 4 mandatory Opus lanes — senior-engineer, software-architect, qa, regression-tester — plus a cheap haiku pr-coherence lane and N dynamic specialists; the regression-tester scopes to baseline-failure detection against `main` via git-stash. Mutation testing is removed entirely. Tests are authored inline by `execute-task`'s coder alongside the implementation; a hard-fail host quality gate (lint+typecheck+test, +build at tier=full when public API drifted) runs BEFORE TASK_NN atomic-renames to .completed.md. Receiving-code-review closes EVERY finding with a 7-step ladder (sonnet → research → opus → research → log to tech-debt); haiku is forbidden for fix dispatch. The new `regression-guard` skill re-runs the host quality gate over the aggregate post-fix diff, routing failures back through the fix ladder for up to 3 rounds total. Feature-acceptance mode is tier-aware (smoke / hybrid / autonomous-with-stack-boot). Finalize-feature absorbs host-doc patching (Phase A) + the committed README render (Phase B). Universal subagent preamble requires `browzer deps --reverse` blast-radius probing before any edit.