Psters_AI_Workflow

Per-repo commit worker. Analyzes ALL changed files independently, groups them by ticket, and makes MULTIPLE focused commits — one per logical group. Spawned in parallel by /pwf-commit-changes (one instance per repo). Never create branches or push.

Commit uncommitted changes across all workspace repos and tag commits with ticket numbers. Each repo gets its own subagent that analyzes files individually, groups them by ticket, and makes multiple focused commits. Use when the user pastes issue text (with TICKET-XXX) and wants to commit, or says "commit with these tickets" / "commit my changes".

Deploy AWS Lambdas using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo.

Load and enforce mandatory project documentation baseline before implementation work.

Run standardized post-implementation documentation maintenance and quality checks.

Use when implementation is complete to close branch/worktree with a disciplined decision flow (merge, PR, keep, discard) plus cleanup.

Manages Git worktrees for isolated parallel development. Use when creating separate working directories for branches without switching the main repo.

Use for explicit multi-subagent orchestration when tasks are independent and parallelization improves quality or speed while preserving deterministic merge.

Use when processing review feedback to prioritize critical findings and resolve comments safely before commit.

Use when requesting a focused review with standardized findings format (critical, important, informational) before commit or PR.

Use for bugs, failing tests, and unexpected behavior; enforce a 4-phase root-cause-first debugging process before implementing fixes.

Optional TDD workflow; use only when user explicitly requests TDD/tests (red-green-refactor with minimal scope).

Meta-skill for selecting and invoking the right workflow skill before acting; use when starting or switching task type to avoid bypassing required discipline.

Use before any completion/success claim to enforce fresh verification evidence (build/lint/tests/repro command) and explicit limitations when verification is partial.

Use during brainstorm only when the problem is strongly visual (complex UI, flow mapping, alternatives) and create optional browser/canvas artifacts.

Frontend conventions for Angular projects: standalone components, features, error capture, styles. Use when implementing or reviewing code in Angular frontends.

Backend conventions for NestJS projects: modules, controllers, services, DTOs, migrations, structure. Use when implementing or reviewing code in NestJS backends.