ign

Use when implementation work in this repository changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the project-local divedra workflow `divedra-workflows/design-and-implement-review-loop`, including design/plan alignment, implementation, review, user-facing documentation refresh, and final handoff.

Use when creating or organizing design documents. Provides directory structure, file naming, and content guidelines for design specs and references.

Use when a divedra workflow, CLI command, GraphQL control plane, event listener, or submodule integration appears to fail because of an upstream divedra bug. Requires reproducing with the local submodule, filing an issue in tacogips/divedra when the bug is real, fixing the submodule, validating it, and committing the divedra change.

Use when helping an end user run, inspect, monitor, resume, continue, rerun, or troubleshoot existing divedra workflows. Applies to workflow list/status/validate/inspect/run, session progress/status/resume/continue/rerun, GraphQL inspection, mock scenarios, workflow roots, runtime artifacts, local serve, GraphQL endpoint execution, and event-triggered workflow usage.

Use when creating, modifying, reviewing, or validating divedra workflow bundles. Applies to step-addressed workflow.json authoring, node payload files, prompt files, built-in node add-ons, cross-workflow transitions, manager/worker routing, and portable workflows under a workflow root.

Use when testing or verifying divedra workflow bundles. Applies to deterministic mock-scenario runs, workflow validate/inspect/run checks, EXPECTED_RESULTS.md updates, regression assertions, session output verification, and CI-style workflow fixture validation.

Use when executing tasks from implementation plans. Provides task selection, parallel execution, progress tracking, and review cycle guidelines.

Use when creating implementation plans from design documents. Provides plan structure, status tracking, and progress logging guidelines.

Use when creating test plans from implementation and design documents. Provides test plan structure, test case tracking, and coverage guidelines.

Use when refactoring tests for better maintainability. Provides guidelines for removing duplicates, DRYing fixtures/assertions, restructuring test organization, renaming, and splitting oversized files.

Use when writing, reviewing, or refactoring TypeScript code. Provides type safety patterns, error handling, project layout, and async programming guidelines.

Use when reviewing TypeScript changes for alignment with ts-coding-standards, Biome lint rules, and repository conventions before merge or handoff.