ShaftHQ/SHAFT_ENGINE

chaos-engine

Load the canonical ChaosEngine policy and this repository's selected project profile before every task.

local-coding-delegate

Optional local coding loop as a mechanical or default delegate. Use when the decider model wants a cheap local coder and a hardware probe says the host can run one.

work-item

Use when opening or rewriting a work item on any git-based SCM. Source-control agnostic; GitHub, GitLab, and Azure Boards are adapters only.

caveman

Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman…

chaos-engine

Load the canonical installed ChaosEngine before every task.

chaos-engine

Load the canonical installed ChaosEngine before every task.

chaos-engine

Canonical provider-neutral skill router and working contract. Use at the start of every task, on every host, in every main thread and delegate, before discovery, planning, edits, or answering.

shaft-developer

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

agent-guidance-boundary-guard

Use when auditing SHAFT agent guidance, host adapters, hooks, guidance budgets, or retrieval setup.

agentic-pdca-loop

Use for SHAFT PDCA, Kevin/Bob/Bruce roles, or refinement loops.

allure-extent-report-operator

Use when operating SHAFT report generation, Allure/Extent artifacts, CI summaries, upload actions, or failure extraction.

ci-failure-investigator

Route CI run, job, and Allure failure investigations to the canonical playbook.

flaky-test-stabilizer

Route intermittent SHAFT test diagnosis and stabilization to the canonical playbook.

mcp-transport-contract-auditor

Route shaft-mcp transport-contract audits to the canonical playbook.

modular-boundary-auditor

Use when auditing Maven module boundaries, BOM wiring, legacy coordinates, bundled examples, or clean consumer fixtures.

public-behavior-docs-synchronizer

Route public-behavior documentation synchronization to the canonical playbook.

release-dependency-guard

Use when preparing or reviewing a SHAFT release, dependency updates, static versions, or Maven Central safeguards.

shaft-marketing-ad-producer

Route SHAFT marketing-ad planning and production to the canonical playbook.

shaft-ui-design

Route SHAFT UI and visual QA work to the canonical design playbook.

shaft-accessibility-testing

Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.

shaft-api-testing

Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.

shaft-assertions

Use when selecting or repairing SHAFT hard assertions, soft verifications, browser or element oracles, API checks, object checks, or failure messages.

shaft-automated-test-authoring

Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.

shaft-change-verification

Use when edited SHAFT Java needs a reuse plan, preview diff, guardrail check, approved application, focused test, and evidence-backed verdict.

shaft-cli

Use when a SHAFT task needs a deterministic one-shot command, machine-readable output, offline discovery, or code generation from a persisted recording.

shaft-database-testing

Use when implementing or repairing SHAFT.DB checks for persisted state, queries, rows, transactions, cleanup, or database-backed integration behavior.

shaft-defect-reporting

Use when reporting a confirmed SHAFT product defect with severity, impact, environment, reproduction steps, expected and actual behavior, and evidence links.

shaft-execution-reporting

Use when reporting SHAFT execution to engineers with reconciled counts, coverage, environments, failures, defects, flakes, evidence, risks, and next actions.

shaft-failure-analysis

Use when investigating consistently failed SHAFT results through evidence, controlled reproduction, hypotheses, and root-cause ownership.

shaft-flaky-test-analysis

Use when SHAFT tests inconsistently pass or fail under equivalent conditions and need history, retry, timing, state, data, or environment analysis.

shaft-fluent-api

Use when composing or repairing SHAFT fluent browser, element, touch, assertion, verification, or report-message chains.

shaft-guide-search

Use when current official SHAFT syntax, configuration, migration, troubleshooting, or feature guidance must be found and cited before coding.

shaft-locator-design

Use when identifying, ranking, repairing, or generating resilient SHAFT web or mobile locators from current DOM, ARIA, or accessibility-tree evidence.

shaft-mcp

Use when a SHAFT task needs structured tool calls, interactive exploration, or browser, mobile, driver, and capture state that persists across calls.

shaft-mobile-actions

Use when implementing SHAFT native or mobile-web sessions, context switches, taps, gestures, rotation, keyboard, or app lifecycle behavior.

shaft-nonfunctional-test-design

Use when designing measurable risk-based tests for performance, security, reliability, recovery, compatibility, scalability, usability, or operations.

shaft-page-objects

Use when creating or refactoring reusable SHAFT page objects, component objects, locators, and user-intent methods without duplicating owners.

shaft-recording-codegen

Use when a persisted SHAFT web, Playwright, mobile, or API recording must become compilable, repository-aware Java code or insertion blocks.

shaft-requirements-analysis

Use when analyzing requirements for testability, acceptance criteria, traceability, contradictions, omissions, risks, assumptions, or coverage gaps.

shaft-stakeholder-reporting

Use when translating verified SHAFT coverage, outcomes, defects, trends, and residual risk into business quality or release decisions.