altivum-feature-dev-pipeline

Deploy the implemented change safely — feasibility check, reviewable/reversible mechanisms, migrations, and live verification.

UX-friction lens — traces real user flows and proposes up to 3 code-grounded fixes for the friction users actually hit, ranked by impact.

Empirical health & architecture audit — structure, correctness, security, maintainability — with prioritized, evidence-backed fixes.

Execute a previously generated implementation plan with precision, TDD, and verification.

Interface-craft lens — audits visual design quality and modern CSS, proposes exactly 3 UI upgrades with before/after code.

Read-only deep analysis of ONE focus area of a codebase (a layer like frontend/backend/data, or a cross-cutting concern such as UX-flow friction). Returns structured findings — strengths, gaps, file:line evidence, candidate improvements with rough impact/effort. Does not rank or edit. Invoke one per focus area, in parallel.

Use after a deployment to verify it actually worked end-to-end — checks infra/app status, live endpoints, deployed artifacts, and migrated data. Read-only; reports evidence, never mutates infrastructure.

Read-only live web research on ONE angle (category leaders, signature UX/interaction patterns, emerging platform capabilities, or a field-specific question) for a given project positioning. Returns concrete cited findings (name + URL + technique + why-now) grounded to the repo. Invoke one per angle, in parallel.

Functional gate for a code change. Launches the app and OPERATES the changed functionality end-to-end — web changes via Claude-in-Chrome, non-web changes via their real interface (API/CLI/function) — then reports whether a real user could actually use it. The critical must-pass of the refine quality gate. Runs processes and drives a browser, but never edits source code.

Use during/after the execute phase to review code changes for security vulnerabilities — auth/authz, injection, input validation, secrets, IAM least-privilege, data exposure, and unsafe external calls. Read-only; reports findings, does not modify code.

1 hook across 1 event