fa.story-time

Add/extend Playwright E2E/integration specs for web use-case changes. Prefer existing repo naming conventions; include UC ID when introducing new use-case-specific specs.

Ensure GitHub Actions CI exists and is green. CI must run lint/format, build, and tests as applicable. Failing CI is blocking.

Derive comprehensive `/docs` from an existing codebase when docs are missing/stale. This is blocking work before new features.

Add docker-compose for HTTP APIs (required before implementing/changing use cases). Provide .env.example + Make targets: up/down/test/lint/build.

End-to-end Gaia SDLC workflow (Repo Explorer → drift/CI fixes → task graph → gated delivery → QA veto → MCP proof). Use for any work in a repo.

Run curl-style integration checks against the docker-compose stack for HTTP APIs. Required for use-case changes.

Add or extend lint/format tooling and ensure it runs locally (Makefile) and in CI. Lint/build are always required in Gaia.

Manual backend regression via curl-like HTTP checks against the docker-compose stack. Required for API use-case changes (label: curl).

Perform manual web regression using Playwright MCP tools (interactive). Required for web use-case changes. Keep evidence low-context (labels + paths only).

Survey repo reality (stack, docs/code/skills drift, CI/lint/tests/docker/Makefile) and produce a compact Repo Survey + suggested tasks for the orchestrator.

Prevent and repair drift between `/docs` (source of truth), code, tests, CI, and runtime artifacts. Use before marking work done.

Opinionated baseline for .NET HTTP APIs: analyzers/formatting, unit+integration strategy, docker-compose, Makefile targets, and CI wiring.

Opinionated baseline for .NET MAUI apps: analyzers/format, tests where feasible, Makefile targets, and CI wiring (build validation).

Opinionated baseline for Flutter apps: format/analyze, tests, Makefile targets, and CI wiring (no docker unless backend exists separately).

Opinionated baseline for Python projects: ruff-based lint/format, pytest, optional dockerization for services, Makefile targets, and CI wiring.

Opinionated baseline for JS/TS web repos: lint/format, tests, Playwright, docker (if HTTP API), Makefile targets, and CI wiring.

How the orchestrator must create/manage MCP tasks (todo/doing/done), set required_gates, handle blockers/questions, and record low-context proof for completion.