shaft-developer

name	shaft-developer
description	Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.

SHAFT Developer

Routing

• Lifecycle: shaft-requirements-analysis, shaft-test-planning, shaft-test-case-design, shaft-test-data-design, shaft-test-environment, shaft-test-execution, shaft-test-monitoring, shaft-failure-analysis, shaft-flaky-test-analysis, shaft-defect-reporting, shaft-execution-reporting, shaft-stakeholder-reporting, shaft-accessibility-testing, shaft-nonfunctional-test-design
• Implementation: shaft-automated-test-authoring, shaft-page-objects, shaft-fluent-api, shaft-locator-design, shaft-web-actions, shaft-mobile-actions, shaft-api-testing, shaft-database-testing, shaft-assertions, shaft-guide-search, shaft-test-recording, shaft-recording-codegen, shaft-change-verification
• Tools: shaft-mcp, shaft-cli

Read the deterministic routing map, select the single closest specialist for the current deliverable, and load only that skill. A natural-language web, mobile, or API scenario whose output is generated test code starts at shaft-test-recording, then returns here for shaft-recording-codegen after the recording is persisted and replay-proven. Return here only when the user asks for a distinct next deliverable. Never guess SHAFT syntax, tool names, execution evidence, or product behavior.