Data2Evidence-coding-agent-tools

Use for D2E backend function development and debugging under repos/Data2Evidence/plugins/functions, including Trex-hosted Deno/Express services, function route tracing through plugins/functions/package.json, temporary diagnostic logging, WATCH-mode function reloads, trex restart fallback, and filtered Docker logs.

Use for D2E backend function development and debugging under repos/Data2Evidence/plugins/functions, including Trex-hosted Deno/Express services, function route tracing through plugins/functions/package.json, temporary diagnostic logging, WATCH-mode function reloads, trex restart fallback, and filtered Docker logs.

Use for D2E backend function development and debugging under repos/Data2Evidence/plugins/functions, including Trex-hosted Deno/Express services, function route tracing through plugins/functions/package.json, temporary diagnostic logging, WATCH-mode function reloads, trex restart fallback, and filtered Docker logs.

Use for D2E backend function development and debugging under repos/Data2Evidence/plugins/functions, including Trex-hosted Deno/Express services, function route tracing through plugins/functions/package.json, temporary diagnostic logging, WATCH-mode function reloads, trex restart fallback, and filtered Docker logs.

Use when updating, regenerating, reviewing, or troubleshooting Data2Evidence OpenAPI specs under docs/openapi/specs and tools/d2e-openapi-spec, including source-diff review from the previous baseline, clean generation from latest origin/develop, request/response/example updates, and OpenAPI style checks.

Use when updating, regenerating, reviewing, or troubleshooting Data2Evidence OpenAPI specs under docs/openapi/specs and tools/d2e-openapi-spec, including source-diff review from the previous baseline, clean generation from latest origin/develop, request/response/example updates, and OpenAPI style checks.

Use when updating, regenerating, reviewing, or troubleshooting Data2Evidence OpenAPI specs under docs/openapi/specs and tools/d2e-openapi-spec, including source-diff review from the previous baseline, clean generation from latest origin/develop, request/response/example updates, and OpenAPI style checks.

Use when updating, regenerating, reviewing, or troubleshooting Data2Evidence OpenAPI specs under docs/openapi/specs and tools/d2e-openapi-spec, including source-diff review from the previous baseline, clean generation from latest origin/develop, request/response/example updates, and OpenAPI style checks.

Use to break an approved PRD into implementation phases, subphases, dependencies, risks, and acceptance criteria.

Use to create a product requirements document for larger D2E work needing product, technical, and architecture alignment.

Use to enable and verify D2E single-spa Import Map Overrides, point portal plugin modules to local dev server lifecycle bundles, or handle the Cohort Builder/vue-mri exception that requires build-and-copy hot deploy to trex. Trigger when a task mentions D2E devtools, single-spa import map overrides, the bottom-right ellipsis menu, serving updated UI from another app setup, localhost:41100 UI override checks, module override URLs, or verifying that "Import Map Overrides" appears after setting localStorage devtools.

Use for D2E Cohorts, Patient Analytics, vue-mri, or MRI UI5 changes, including build, hot deploy, and verification workflow.

Use for D2E Concept Sets UI changes, including build, hot deploy, and verification workflow.

Use to verify D2E UI behavior with browser tooling, screenshots, network checks, and known local runtime paths.

Use to implement a specific subphase from a D2E implementation plan with scope discipline, testing, and review.

Use for D2E Cohorts, Patient Analytics, vue-mri, or MRI UI5 changes, including build, hot deploy, and verification workflow.

Use for D2E Concept Sets UI changes, including build, hot deploy, and verification workflow.

Use to enable and verify D2E single-spa Import Map Overrides, point portal plugin modules to local dev server lifecycle bundles, or handle the Cohort Builder/vue-mri exception that requires build-and-copy hot deploy to trex. Trigger when a task mentions D2E devtools, single-spa import map overrides, the bottom-right ellipsis menu, serving updated UI from another app setup, localhost:41100 UI override checks, module override URLs, or verifying that "Import Map Overrides" appears after setting localStorage devtools.

Use to verify D2E UI behavior with browser tooling, screenshots, network checks, and known local runtime paths.

Use to curate, verify, deduplicate, and route durable D2E knowledge before it is added to or changed under knowledge/.

Use to break an approved PRD into implementation phases, subphases, dependencies, risks, and acceptance criteria.

Use to implement a specific subphase from a D2E implementation plan with scope discipline, testing, and review.

Use to create a product requirements document for larger D2E work needing product, technical, and architecture alignment.

Use for targeted D2E fixes with small scope, reproduce-first behavior for bugs, minimal edits, and focused verification.

Use for small D2E features spanning roughly 1-3 files where scope is clear but a quick implementation plan and review are useful.

Use for D2E Cohorts, Patient Analytics, vue-mri, or MRI UI5 changes, including build, hot deploy, and verification workflow.

Use for D2E Concept Sets UI changes, including build, hot deploy, and verification workflow.

Use to enable and verify D2E single-spa Import Map Overrides, point portal plugin modules to local dev server lifecycle bundles, or handle the Cohort Builder/vue-mri exception that requires build-and-copy hot deploy to trex. Trigger when a task mentions D2E devtools, single-spa import map overrides, the bottom-right ellipsis menu, serving updated UI from another app setup, localhost:41100 UI override checks, module override URLs, or verifying that "Import Map Overrides" appears after setting localStorage devtools.

Use to verify D2E UI behavior with browser tooling, screenshots, network checks, and known local runtime paths.

Use to curate, verify, deduplicate, and route durable D2E knowledge before it is added to or changed under knowledge/.

Use to break an approved PRD into implementation phases, subphases, dependencies, risks, and acceptance criteria.

Use to implement a specific subphase from a D2E implementation plan with scope discipline, testing, and review.

Use to create a product requirements document for larger D2E work needing product, technical, and architecture alignment.

Use for targeted D2E fixes with small scope, reproduce-first behavior for bugs, minimal edits, and focused verification.

Use for small D2E features spanning roughly 1-3 files where scope is clear but a quick implementation plan and review are useful.

Use for D2E Cohorts, Patient Analytics, vue-mri, or MRI UI5 changes, including build, hot deploy, and verification workflow.

Use for D2E Concept Sets UI changes, including build, hot deploy, and verification workflow.

Use to enable and verify D2E single-spa Import Map Overrides, point portal plugin modules to local dev server lifecycle bundles, or handle the Cohort Builder/vue-mri exception that requires build-and-copy hot deploy to trex. Trigger when a task mentions D2E devtools, single-spa import map overrides, the bottom-right ellipsis menu, serving updated UI from another app setup, localhost:41100 UI override checks, module override URLs, or verifying that "Import Map Overrides" appears after setting localStorage devtools.

Use to verify D2E UI behavior with browser tooling, screenshots, network checks, and known local runtime paths.

Use to curate, verify, deduplicate, and route durable D2E knowledge before it is added to or changed under knowledge/.