st4ck

Debug and fix bugs with role-separated agents — research, test gaps, fix, verify green. You are the dev manager.

Activates the `impact` skill. Use when:

Full feature lifecycle — requirements → plan → code → QA → deliver. Role-separated agents with human gates.

Migrate legacy tests to v2 component format. Activates the qa-testing-migration skill, which classifies each test by shape (agentic / components_v1 / components_v2 / mixed) via classify_test_migration_shape and runs the appropriate internal branch (agentic re-author OR component-upgrade) inline. Per plan §13.2 (consolidated 2026-04-26 — was three skills before).

PO feature research — explore codebase, challenge requirements, surface logic gaps, present solution options with effort/risk.

Use this agent to implement features from the plan's task list. Writes code, unit tests for pure functions, and runs quality gates. Never writes or reviews QA tests.

Use this agent to review code changes for bugs, logic errors, security vulnerabilities, and adherence to project conventions. Returns findings with confidence scores.

Use this agent to explore and understand a codebase — traces architecture, patterns, dependencies, similar features, data models, and git history. Returns structured findings for planning.

Primary authoring teammate. Drives a single Session per test journey, captures primitives, decomposes the trace into save_component(s) + create_test_case at the end of the drive. Same prompt for feature, version, regression, and migration authoring. Cannot modify code files.

Use this agent to review and sign QA test cases it did not author. Verifies UI strings, routes, and assertions against the actual codebase. Cannot modify code files.

Forwarding stub. This skill was consolidated into qa-testing-migration on 2026-04-26 (plan §13.2, mid-12). Activate qa-testing-migration instead — it covers Path A (heavy re-author) AND Path B (light component-upgrade) inline, with classify_test_migration_shape selecting the branch per test.

Phase 5 §5.2 — agent-driven test impact analysis. Reads the local git diff, calls get_tests_affected_by_diff, creates test_design_change dev_tasks per affected component. Optionally invokes the propose subworkflow to attach proposed component diffs. Triggered explicitly via `/st4ck:impact` or auto on PostToolUse(Edit/Write) hits inside a cited file.

Forwarding stub. This skill was consolidated into qa-testing-migration on 2026-04-26 (plan §13.2, mid-12). Activate qa-testing-migration instead — it covers Path A (heavy re-author) AND Path B (light component-upgrade) inline, with classify_test_migration_shape selecting the branch per test.

Create comprehensive implementation plans for features including phased tasks, security analysis, test strategy, and migration files. Use when transitioning from approved requirements to implementation.

Forwarding stub. This skill was consolidated into qa-testing-migration on 2026-04-26 (plan §13.2, mid-12). Activate qa-testing-migration instead — it covers Path A (heavy re-author) AND Path B (light component-upgrade) inline, with classify_test_migration_shape selecting the branch per test.

1 hook across 1 event