marathon-ralph

Cancel the active marathon

Run the marathon development system. This command automatically:

Check marathon progress and Linear project status

Implement the current feature following the implementation plan.

Completes an issue cycle - updates Linear, state file, and reports progress. Called at the end of verify-plan-code-test-qa loop.

Create Linear project and issues from specification. Used when starting a new marathon.

Create implementation plan for the current Linear issue. Reviews codebase and documents approach.

Create E2E tests for web features. Skips non-web projects.

Verify Linear MCP is connected and authenticated. Run automatically before marathon operations.

Write unit and integration tests for the implemented feature.

Run comprehensive verification (tests, lint, types) before starting new work. MUST pass before coding.

SQLite database implementation using LibSQL client and Drizzle ORM. This skill covers local development, Turso cloud, and Cloudflare D1 deployments.

Autonomous long-running development from specifications. Use when user wants to build an application from a spec file, run continuous development, or automate feature implementation. Triggers on phrases like "marathon this", "build from spec", "autonomous development", "keep coding until done".

Detects project type, package manager, and monorepo structure. Returns correct commands for test/build/lint/dev. Run at project initialization and cache results in state. Use before running any build/test commands.

Configure Playwright for E2E testing. Use when setting up end-to-end tests, when no E2E framework is detected, or when the user asks to configure browser testing.

Configure Vitest for unit and integration testing. Use when setting up a test framework, when no test runner is detected, or when the user asks to configure testing.

Programmatically update marathon-ralph state file using deterministic jq commands. Use this instead of manually editing the JSON file.

Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.

Write Playwright E2E tests using fixtures and best practices. Use when creating E2E tests, writing browser automation tests, or testing user flows.

1 hook across 1 event