[
  {
    "id": "api-contract-drift-audit",
    "slug": "api-contract-drift-audit",
    "category": "backend-api",
    "title": "API Contract Drift Audit",
    "intent": "Compare OpenAPI, implementation, and tests to find field or status-code drift.",
    "verify": "npx openapi-diff old.yaml new.yaml && pytest tests/api",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Contract Drift Audit for a backend API service: Compare OpenAPI, implementation, and tests to find field or status-code drift.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `npx openapi-diff old.yaml new.yaml && pytest tests/api`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare OpenAPI, implementation, and tests to find field or status-code drift.\n- The verification command or evidence path succeeds: `npx openapi-diff old.yaml new.yaml && pytest tests/api`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx openapi-diff old.yaml new.yaml && pytest tests/api` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "idempotent-create-endpoint",
    "slug": "idempotent-create-endpoint",
    "category": "backend-api",
    "title": "Idempotent Create Endpoint",
    "intent": "Add idempotency keys and replay-safe semantics to a create endpoint.",
    "verify": "pytest -k idempotency",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Idempotent Create Endpoint for a backend API service: Add idempotency keys and replay-safe semantics to a create endpoint.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k idempotency`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add idempotency keys and replay-safe semantics to a create endpoint.\n- The verification command or evidence path succeeds: `pytest -k idempotency`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k idempotency` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "api-error-taxonomy",
    "slug": "api-error-taxonomy",
    "category": "backend-api",
    "title": "API Error Taxonomy",
    "intent": "Unify HTTP status codes, machine error codes, user messages, and logs.",
    "verify": "pytest -k error_response",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Error Taxonomy for a backend API service: Unify HTTP status codes, machine error codes, user messages, and logs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k error_response`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Unify HTTP status codes, machine error codes, user messages, and logs.\n- The verification command or evidence path succeeds: `pytest -k error_response`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k error_response` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "pagination-consistency",
    "slug": "pagination-consistency",
    "category": "backend-api",
    "title": "Pagination Consistency",
    "intent": "Fix cursor or offset pagination so rows are not skipped, duplicated, or reordered.",
    "verify": "pytest -k pagination",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Pagination Consistency for a backend API service: Fix cursor or offset pagination so rows are not skipped, duplicated, or reordered.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k pagination`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix cursor or offset pagination so rows are not skipped, duplicated, or reordered.\n- The verification command or evidence path succeeds: `pytest -k pagination`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k pagination` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "request-validation-boundary",
    "slug": "request-validation-boundary",
    "category": "backend-api",
    "title": "Request Validation Boundary",
    "intent": "Move input validation to the API boundary and reject unknown fields.",
    "verify": "pytest -k validation",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Request Validation Boundary for a backend API service: Move input validation to the API boundary and reject unknown fields.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k validation`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Move input validation to the API boundary and reject unknown fields.\n- The verification command or evidence path succeeds: `pytest -k validation`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k validation` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "api-rate-limit-policy",
    "slug": "api-rate-limit-policy",
    "category": "backend-api",
    "title": "API Rate Limit Policy",
    "intent": "Implement rate limit behavior, headers, and over-limit responses for critical routes.",
    "verify": "k6 run rate_limit.js",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Rate Limit Policy for a backend API service: Implement rate limit behavior, headers, and over-limit responses for critical routes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `k6 run rate_limit.js`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement rate limit behavior, headers, and over-limit responses for critical routes.\n- The verification command or evidence path succeeds: `k6 run rate_limit.js`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `k6 run rate_limit.js` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "webhook-retry-contract",
    "slug": "webhook-retry-contract",
    "category": "backend-api",
    "title": "Webhook Retry Contract",
    "intent": "Define webhook signature verification, retry, dedupe, and failure observability.",
    "verify": "pytest -k webhook",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Webhook Retry Contract for a backend API service: Define webhook signature verification, retry, dedupe, and failure observability.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k webhook`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define webhook signature verification, retry, dedupe, and failure observability.\n- The verification command or evidence path succeeds: `pytest -k webhook`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k webhook` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "backward-compatible-response",
    "slug": "backward-compatible-response",
    "category": "backend-api",
    "title": "Backward-Compatible Response",
    "intent": "Add response fields without breaking old clients and document removal paths.",
    "verify": "pytest -k contract",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Backward-Compatible Response for a backend API service: Add response fields without breaking old clients and document removal paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k contract`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add response fields without breaking old clients and document removal paths.\n- The verification command or evidence path succeeds: `pytest -k contract`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k contract` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "grpc-timeout-propagation",
    "slug": "grpc-timeout-propagation",
    "category": "backend-api",
    "title": "gRPC Timeout Propagation",
    "intent": "Propagate deadlines across service calls and cancel work correctly.",
    "verify": "go test ./...",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete gRPC Timeout Propagation for a backend API service: Propagate deadlines across service calls and cancel work correctly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `go test ./...`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Propagate deadlines across service calls and cancel work correctly.\n- The verification command or evidence path succeeds: `go test ./...`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `go test ./...` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "async-job-state-machine",
    "slug": "async-job-state-machine",
    "category": "backend-api",
    "title": "Async Job State Machine",
    "intent": "Make async job transitions explicit and tested across pending/running/succeeded/failed/canceled.",
    "verify": "pytest -k job_state",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Async Job State Machine for a backend API service: Make async job transitions explicit and tested across pending/running/succeeded/failed/canceled.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k job_state`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Make async job transitions explicit and tested across pending/running/succeeded/failed/canceled.\n- The verification command or evidence path succeeds: `pytest -k job_state`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k job_state` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "authz-resource-scope",
    "slug": "authz-resource-scope",
    "category": "backend-api",
    "title": "Resource-Level Authorization",
    "intent": "Prevent logged-in users from accessing resources they do not own.",
    "verify": "pytest -k authz",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Resource-Level Authorization for a backend API service: Prevent logged-in users from accessing resources they do not own.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k authz`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prevent logged-in users from accessing resources they do not own.\n- The verification command or evidence path succeeds: `pytest -k authz`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k authz` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "api-versioning-plan",
    "slug": "api-versioning-plan",
    "category": "backend-api",
    "title": "API Versioning Plan",
    "intent": "Create a v1/v2 coexistence plan with deprecation headers and migration tests.",
    "verify": "pytest -k api_version",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Versioning Plan for a backend API service: Create a v1/v2 coexistence plan with deprecation headers and migration tests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `pytest -k api_version`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create a v1/v2 coexistence plan with deprecation headers and migration tests.\n- The verification command or evidence path succeeds: `pytest -k api_version`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k api_version` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "db-migration-safety",
    "slug": "db-migration-safety",
    "category": "backend-data",
    "title": "Database Migration Safety",
    "intent": "Review a migration for rollback, online execution, and lock risk.",
    "verify": "npm run migrate:dry-run",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Database Migration Safety for a data-backed backend service: Review a migration for rollback, online execution, and lock risk.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `npm run migrate:dry-run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Review a migration for rollback, online execution, and lock risk.\n- The verification command or evidence path succeeds: `npm run migrate:dry-run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run migrate:dry-run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "transaction-boundary-audit",
    "slug": "transaction-boundary-audit",
    "category": "backend-data",
    "title": "Transaction Boundary Audit",
    "intent": "Find missing or oversized transactions in multi-table write paths.",
    "verify": "pytest -k transaction",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Transaction Boundary Audit for a data-backed backend service: Find missing or oversized transactions in multi-table write paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k transaction`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find missing or oversized transactions in multi-table write paths.\n- The verification command or evidence path succeeds: `pytest -k transaction`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k transaction` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "cache-invalidation-map",
    "slug": "cache-invalidation-map",
    "category": "backend-data",
    "title": "Cache Invalidation Map",
    "intent": "Map write paths to cache keys and fix stale reads.",
    "verify": "pytest -k cache",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Cache Invalidation Map for a data-backed backend service: Map write paths to cache keys and fix stale reads.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k cache`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Map write paths to cache keys and fix stale reads.\n- The verification command or evidence path succeeds: `pytest -k cache`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k cache` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "n-plus-one-query-fix",
    "slug": "n-plus-one-query-fix",
    "category": "backend-data",
    "title": "N+1 Query Fix",
    "intent": "Reduce list endpoint query count with batching or preloading.",
    "verify": "pytest -k query_count",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete N+1 Query Fix for a data-backed backend service: Reduce list endpoint query count with batching or preloading.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k query_count`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce list endpoint query count with batching or preloading.\n- The verification command or evidence path succeeds: `pytest -k query_count`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k query_count` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "optimistic-locking-rollout",
    "slug": "optimistic-locking-rollout",
    "category": "backend-data",
    "title": "Optimistic Locking Rollout",
    "intent": "Add version checks and conflict responses for concurrent edits.",
    "verify": "pytest -k optimistic_lock",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Optimistic Locking Rollout for a data-backed backend service: Add version checks and conflict responses for concurrent edits.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k optimistic_lock`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add version checks and conflict responses for concurrent edits.\n- The verification command or evidence path succeeds: `pytest -k optimistic_lock`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k optimistic_lock` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "soft-delete-integrity",
    "slug": "soft-delete-integrity",
    "category": "backend-data",
    "title": "Soft Delete Integrity",
    "intent": "Make queries, unique indexes, and restore flows respect soft deletion.",
    "verify": "pytest -k soft_delete",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Soft Delete Integrity for a data-backed backend service: Make queries, unique indexes, and restore flows respect soft deletion.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k soft_delete`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Make queries, unique indexes, and restore flows respect soft deletion.\n- The verification command or evidence path succeeds: `pytest -k soft_delete`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k soft_delete` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "db-index-regression",
    "slug": "db-index-regression",
    "category": "backend-data",
    "title": "Index Regression Check",
    "intent": "Add or adjust indexes and prove read gains do not create unacceptable write cost.",
    "verify": "pytest -k slow_query",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Index Regression Check for a data-backed backend service: Add or adjust indexes and prove read gains do not create unacceptable write cost.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k slow_query`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add or adjust indexes and prove read gains do not create unacceptable write cost.\n- The verification command or evidence path succeeds: `pytest -k slow_query`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k slow_query` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "outbox-pattern-adoption",
    "slug": "outbox-pattern-adoption",
    "category": "backend-data",
    "title": "Outbox Reliable Events",
    "intent": "Use an outbox table to prevent lost events after successful database commits.",
    "verify": "pytest -k outbox",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Outbox Reliable Events for a data-backed backend service: Use an outbox table to prevent lost events after successful database commits.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k outbox`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use an outbox table to prevent lost events after successful database commits.\n- The verification command or evidence path succeeds: `pytest -k outbox`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k outbox` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "read-replica-lag-guard",
    "slug": "read-replica-lag-guard",
    "category": "backend-data",
    "title": "Read Replica Lag Guard",
    "intent": "Prevent write-after-read paths from hitting stale replicas.",
    "verify": "pytest -k replica_lag",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Read Replica Lag Guard for a data-backed backend service: Prevent write-after-read paths from hitting stale replicas.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `pytest -k replica_lag`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prevent write-after-read paths from hitting stale replicas.\n- The verification command or evidence path succeeds: `pytest -k replica_lag`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k replica_lag` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "schema-drift-detector",
    "slug": "schema-drift-detector",
    "category": "backend-data",
    "title": "Schema Drift Detector",
    "intent": "Compare ORM models, migrations, and the live database schema.",
    "verify": "prisma migrate diff",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Schema Drift Detector for a data-backed backend service: Compare ORM models, migrations, and the live database schema.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `prisma migrate diff`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare ORM models, migrations, and the live database schema.\n- The verification command or evidence path succeeds: `prisma migrate diff`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `prisma migrate diff` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ci-flaky-test-triage",
    "slug": "ci-flaky-test-triage",
    "category": "devops-ci",
    "title": "CI Flaky Test Triage",
    "intent": "Identify flaky tests, separate real failures, and fix unstable waits or fixtures.",
    "verify": "gh run view --log",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete CI Flaky Test Triage for a repository with CI/CD automation: Identify flaky tests, separate real failures, and fix unstable waits or fixtures.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `gh run view --log`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Identify flaky tests, separate real failures, and fix unstable waits or fixtures.\n- The verification command or evidence path succeeds: `gh run view --log`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `gh run view --log` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "build-cache-correctness",
    "slug": "build-cache-correctness",
    "category": "devops-ci",
    "title": "Build Cache Correctness",
    "intent": "Check whether CI cache keys cause stale dependencies or cross-branch pollution.",
    "verify": "npm ci && npm test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Build Cache Correctness for a repository with CI/CD automation: Check whether CI cache keys cause stale dependencies or cross-branch pollution.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `npm ci && npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check whether CI cache keys cause stale dependencies or cross-branch pollution.\n- The verification command or evidence path succeeds: `npm ci && npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm ci && npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "dependency-update-gate",
    "slug": "dependency-update-gate",
    "category": "devops-ci",
    "title": "Dependency Update Gate",
    "intent": "Add dependency upgrade checks for tests, licenses, and vulnerabilities.",
    "verify": "npm audit && npm test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Dependency Update Gate for a repository with CI/CD automation: Add dependency upgrade checks for tests, licenses, and vulnerabilities.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `npm audit && npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add dependency upgrade checks for tests, licenses, and vulnerabilities.\n- The verification command or evidence path succeeds: `npm audit && npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm audit && npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "monorepo-affected-tests",
    "slug": "monorepo-affected-tests",
    "category": "devops-ci",
    "title": "Monorepo Affected Tests",
    "intent": "Run only affected tests without missing cross-package contracts.",
    "verify": "nx affected:test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Monorepo Affected Tests for a repository with CI/CD automation: Run only affected tests without missing cross-package contracts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `nx affected:test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run only affected tests without missing cross-package contracts.\n- The verification command or evidence path succeeds: `nx affected:test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `nx affected:test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "release-note-from-diff",
    "slug": "release-note-from-diff",
    "category": "devops-ci",
    "title": "Release Notes From Diff",
    "intent": "Generate user-facing release notes from commits, PR labels, and breaking changes.",
    "verify": "git log --oneline last..HEAD",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Release Notes From Diff for a repository with CI/CD automation: Generate user-facing release notes from commits, PR labels, and breaking changes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `git log --oneline last..HEAD`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Generate user-facing release notes from commits, PR labels, and breaking changes.\n- The verification command or evidence path succeeds: `git log --oneline last..HEAD`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `git log --oneline last..HEAD` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "artifact-provenance",
    "slug": "artifact-provenance",
    "category": "devops-ci",
    "title": "Artifact Provenance",
    "intent": "Trace a package or image back to the commit and workflow that produced it.",
    "verify": "gh run view",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Artifact Provenance for a repository with CI/CD automation: Trace a package or image back to the commit and workflow that produced it.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `gh run view`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Trace a package or image back to the commit and workflow that produced it.\n- The verification command or evidence path succeeds: `gh run view`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `gh run view` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ci-permission-minimize",
    "slug": "ci-permission-minimize",
    "category": "devops-ci",
    "title": "CI Permission Minimization",
    "intent": "Tighten GitHub Actions token permissions without breaking workflows.",
    "verify": "gh workflow run ci.yml",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete CI Permission Minimization for a repository with CI/CD automation: Tighten GitHub Actions token permissions without breaking workflows.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `gh workflow run ci.yml`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Tighten GitHub Actions token permissions without breaking workflows.\n- The verification command or evidence path succeeds: `gh workflow run ci.yml`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `gh workflow run ci.yml` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "branch-protection-audit",
    "slug": "branch-protection-audit",
    "category": "devops-ci",
    "title": "Branch Protection Audit",
    "intent": "Audit required checks, reviews, linear history, and admin bypasses.",
    "verify": "gh api repos/OWNER/REPO/branches/main/protection",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Branch Protection Audit for a repository with CI/CD automation: Audit required checks, reviews, linear history, and admin bypasses.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `gh api repos/OWNER/REPO/branches/main/protection`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Audit required checks, reviews, linear history, and admin bypasses.\n- The verification command or evidence path succeeds: `gh api repos/OWNER/REPO/branches/main/protection`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `gh api repos/OWNER/REPO/branches/main/protection` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "release-rollback-drill",
    "slug": "release-rollback-drill",
    "category": "devops-ci",
    "title": "Release Rollback Drill",
    "intent": "Create and test a rollback path for the latest release.",
    "verify": "npm run smoke",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Release Rollback Drill for a repository with CI/CD automation: Create and test a rollback path for the latest release.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `npm run smoke`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create and test a rollback path for the latest release.\n- The verification command or evidence path succeeds: `npm run smoke`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run smoke` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "semantic-version-check",
    "slug": "semantic-version-check",
    "category": "devops-ci",
    "title": "Semantic Version Check",
    "intent": "Infer the correct semver bump from API, behavior, and changelog diffs.",
    "verify": "npm test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Semantic Version Check for a repository with CI/CD automation: Infer the correct semver bump from API, behavior, and changelog diffs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Infer the correct semver bump from API, behavior, and changelog diffs.\n- The verification command or evidence path succeeds: `npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docker-image-slimming",
    "slug": "docker-image-slimming",
    "category": "devops-runtime",
    "title": "Docker Image Slimming",
    "intent": "Reduce image size while keeping runtime dependencies and security scans green.",
    "verify": "docker build . && trivy image IMAGE",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Docker Image Slimming for a deployed service: Reduce image size while keeping runtime dependencies and security scans green.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `docker build . && trivy image IMAGE`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce image size while keeping runtime dependencies and security scans green.\n- The verification command or evidence path succeeds: `docker build . && trivy image IMAGE`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `docker build . && trivy image IMAGE` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "k8s-readiness-liveness",
    "slug": "k8s-readiness-liveness",
    "category": "devops-runtime",
    "title": "Kubernetes Probe Repair",
    "intent": "Separate startup, readiness, and liveness probes to avoid bad restarts.",
    "verify": "kubectl describe pod",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Kubernetes Probe Repair for a deployed service: Separate startup, readiness, and liveness probes to avoid bad restarts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `kubectl describe pod`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Separate startup, readiness, and liveness probes to avoid bad restarts.\n- The verification command or evidence path succeeds: `kubectl describe pod`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `kubectl describe pod` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "terraform-plan-review",
    "slug": "terraform-plan-review",
    "category": "devops-runtime",
    "title": "Terraform Plan Review",
    "intent": "Review infrastructure changes for deletes, replacements, and permission expansion.",
    "verify": "terraform plan -out=tfplan",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Terraform Plan Review for a deployed service: Review infrastructure changes for deletes, replacements, and permission expansion.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `terraform plan -out=tfplan`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Review infrastructure changes for deletes, replacements, and permission expansion.\n- The verification command or evidence path succeeds: `terraform plan -out=tfplan`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `terraform plan -out=tfplan` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "helm-values-drift",
    "slug": "helm-values-drift",
    "category": "devops-runtime",
    "title": "Helm Values Drift",
    "intent": "Compare environment values to find hidden staging/prod differences.",
    "verify": "helm diff upgrade",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Helm Values Drift for a deployed service: Compare environment values to find hidden staging/prod differences.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `helm diff upgrade`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare environment values to find hidden staging/prod differences.\n- The verification command or evidence path succeeds: `helm diff upgrade`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `helm diff upgrade` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "autoscaling-thresholds",
    "slug": "autoscaling-thresholds",
    "category": "devops-runtime",
    "title": "Autoscaling Thresholds",
    "intent": "Tune HPA or worker scaling thresholds against real load and queue depth.",
    "verify": "kubectl get hpa",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Autoscaling Thresholds for a deployed service: Tune HPA or worker scaling thresholds against real load and queue depth.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `kubectl get hpa`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Tune HPA or worker scaling thresholds against real load and queue depth.\n- The verification command or evidence path succeeds: `kubectl get hpa`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `kubectl get hpa` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "runtime-config-validation",
    "slug": "runtime-config-validation",
    "category": "devops-runtime",
    "title": "Runtime Config Validation",
    "intent": "Fail startup on missing or invalid environment and config values.",
    "verify": "docker run --env-file .env.example IMAGE",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Runtime Config Validation for a deployed service: Fail startup on missing or invalid environment and config values.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `docker run --env-file .env.example IMAGE`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fail startup on missing or invalid environment and config values.\n- The verification command or evidence path succeeds: `docker run --env-file .env.example IMAGE`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `docker run --env-file .env.example IMAGE` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "zero-downtime-migration",
    "slug": "zero-downtime-migration",
    "category": "devops-runtime",
    "title": "Zero-Downtime Migration",
    "intent": "Plan and verify expand-migrate-contract deployment steps.",
    "verify": "npm run smoke",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Zero-Downtime Migration for a deployed service: Plan and verify expand-migrate-contract deployment steps.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `npm run smoke`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Plan and verify expand-migrate-contract deployment steps.\n- The verification command or evidence path succeeds: `npm run smoke`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run smoke` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "observability-minimum",
    "slug": "observability-minimum",
    "category": "devops-runtime",
    "title": "Observability Minimum",
    "intent": "Add logs, metrics, traces, and alerts for a service's critical paths.",
    "verify": "npm test && curl localhost:PORT/metrics",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Observability Minimum for a deployed service: Add logs, metrics, traces, and alerts for a service's critical paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `npm test && curl localhost:PORT/metrics`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add logs, metrics, traces, and alerts for a service's critical paths.\n- The verification command or evidence path succeeds: `npm test && curl localhost:PORT/metrics`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test && curl localhost:PORT/metrics` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "incident-runbook-gap",
    "slug": "incident-runbook-gap",
    "category": "devops-runtime",
    "title": "Incident Runbook Gap",
    "intent": "Turn a recent incident timeline into missing runbook and alert updates.",
    "verify": "markdownlint docs/runbooks",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Incident Runbook Gap for a deployed service: Turn a recent incident timeline into missing runbook and alert updates.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/runbooks`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Turn a recent incident timeline into missing runbook and alert updates.\n- The verification command or evidence path succeeds: `markdownlint docs/runbooks`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/runbooks` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "queue-backpressure",
    "slug": "queue-backpressure",
    "category": "devops-runtime",
    "title": "Queue Backpressure",
    "intent": "Protect databases and external APIs when worker queues build up.",
    "verify": "pytest -k backpressure",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Queue Backpressure for a deployed service: Protect databases and external APIs when worker queues build up.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `pytest -k backpressure`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Protect databases and external APIs when worker queues build up.\n- The verification command or evidence path succeeds: `pytest -k backpressure`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k backpressure` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "sql-injection-audit",
    "slug": "sql-injection-audit",
    "category": "security-appsec",
    "title": "SQL Injection Audit",
    "intent": "Replace SQL string concatenation with parameterized queries and tests.",
    "verify": "pytest -k injection",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete SQL Injection Audit for an application with security-sensitive code paths: Replace SQL string concatenation with parameterized queries and tests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k injection`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace SQL string concatenation with parameterized queries and tests.\n- The verification command or evidence path succeeds: `pytest -k injection`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k injection` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "command-injection-audit",
    "slug": "command-injection-audit",
    "category": "security-appsec",
    "title": "Command Injection Audit",
    "intent": "Replace shell string execution with argument arrays and validation.",
    "verify": "pytest -k command_injection",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Command Injection Audit for an application with security-sensitive code paths: Replace shell string execution with argument arrays and validation.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k command_injection`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace shell string execution with argument arrays and validation.\n- The verification command or evidence path succeeds: `pytest -k command_injection`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k command_injection` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ssrf-defense-review",
    "slug": "ssrf-defense-review",
    "category": "security-appsec",
    "title": "SSRF Defense Review",
    "intent": "Add URL allowlists and DNS/IP checks for fetch or callback features.",
    "verify": "pytest -k ssrf",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete SSRF Defense Review for an application with security-sensitive code paths: Add URL allowlists and DNS/IP checks for fetch or callback features.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k ssrf`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add URL allowlists and DNS/IP checks for fetch or callback features.\n- The verification command or evidence path succeeds: `pytest -k ssrf`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k ssrf` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "xss-output-encoding",
    "slug": "xss-output-encoding",
    "category": "security-appsec",
    "title": "XSS Output Encoding",
    "intent": "Audit HTML and Markdown rendering for unsafe sinks and missing encoding.",
    "verify": "npm test -- xss",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete XSS Output Encoding for an application with security-sensitive code paths: Audit HTML and Markdown rendering for unsafe sinks and missing encoding.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `npm test -- xss`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Audit HTML and Markdown rendering for unsafe sinks and missing encoding.\n- The verification command or evidence path succeeds: `npm test -- xss`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- xss` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "csrf-sensitive-action",
    "slug": "csrf-sensitive-action",
    "category": "security-appsec",
    "title": "CSRF Sensitive Action",
    "intent": "Protect cookie-authenticated writes from cross-site requests.",
    "verify": "pytest -k csrf",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete CSRF Sensitive Action for an application with security-sensitive code paths: Protect cookie-authenticated writes from cross-site requests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k csrf`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Protect cookie-authenticated writes from cross-site requests.\n- The verification command or evidence path succeeds: `pytest -k csrf`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k csrf` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "auth-bypass-route-map",
    "slug": "auth-bypass-route-map",
    "category": "security-appsec",
    "title": "Auth Bypass Route Map",
    "intent": "Enumerate routes and verify unauthenticated and unauthorized behavior.",
    "verify": "pytest -k auth",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Auth Bypass Route Map for an application with security-sensitive code paths: Enumerate routes and verify unauthenticated and unauthorized behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k auth`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Enumerate routes and verify unauthenticated and unauthorized behavior.\n- The verification command or evidence path succeeds: `pytest -k auth`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k auth` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "file-upload-security",
    "slug": "file-upload-security",
    "category": "security-appsec",
    "title": "File Upload Security",
    "intent": "Validate MIME, extension, size, scanning, and storage isolation.",
    "verify": "pytest -k upload_security",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete File Upload Security for an application with security-sensitive code paths: Validate MIME, extension, size, scanning, and storage isolation.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k upload_security`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Validate MIME, extension, size, scanning, and storage isolation.\n- The verification command or evidence path succeeds: `pytest -k upload_security`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k upload_security` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "tenant-isolation-test",
    "slug": "tenant-isolation-test",
    "category": "security-appsec",
    "title": "Tenant Isolation Test",
    "intent": "Verify tenant IDs are enforced in queries, caches, and background jobs.",
    "verify": "pytest -k tenant",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Tenant Isolation Test for an application with security-sensitive code paths: Verify tenant IDs are enforced in queries, caches, and background jobs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k tenant`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify tenant IDs are enforced in queries, caches, and background jobs.\n- The verification command or evidence path succeeds: `pytest -k tenant`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k tenant` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "replay-attack-defense",
    "slug": "replay-attack-defense",
    "category": "security-appsec",
    "title": "Replay Attack Defense",
    "intent": "Add nonce, timestamp, and expiration checks to signed requests.",
    "verify": "pytest -k replay",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Replay Attack Defense for an application with security-sensitive code paths: Add nonce, timestamp, and expiration checks to signed requests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k replay`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add nonce, timestamp, and expiration checks to signed requests.\n- The verification command or evidence path succeeds: `pytest -k replay`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k replay` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "insecure-direct-object-ref",
    "slug": "insecure-direct-object-ref",
    "category": "security-appsec",
    "title": "IDOR Audit",
    "intent": "Verify direct object ID access always checks ownership or scope.",
    "verify": "pytest -k idor",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete IDOR Audit for an application with security-sensitive code paths: Verify direct object ID access always checks ownership or scope.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `pytest -k idor`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify direct object ID access always checks ownership or scope.\n- The verification command or evidence path succeeds: `pytest -k idor`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k idor` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "secret-scan-baseline",
    "slug": "secret-scan-baseline",
    "category": "security-ops",
    "title": "Secret Scan Baseline",
    "intent": "Add secret scanning and triage historical findings safely.",
    "verify": "gitleaks detect",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Secret Scan Baseline for a production operations environment: Add secret scanning and triage historical findings safely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `gitleaks detect`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add secret scanning and triage historical findings safely.\n- The verification command or evidence path succeeds: `gitleaks detect`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `gitleaks detect` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "iam-least-privilege",
    "slug": "iam-least-privilege",
    "category": "security-ops",
    "title": "IAM Least Privilege",
    "intent": "Reduce cloud permissions to observed API usage and documented needs.",
    "verify": "terraform plan",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete IAM Least Privilege for a production operations environment: Reduce cloud permissions to observed API usage and documented needs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `terraform plan`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce cloud permissions to observed API usage and documented needs.\n- The verification command or evidence path succeeds: `terraform plan`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `terraform plan` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "github-actions-supply-chain",
    "slug": "github-actions-supply-chain",
    "category": "security-ops",
    "title": "GitHub Actions Supply Chain",
    "intent": "Pin third-party actions and review workflow permissions.",
    "verify": "rg \"uses:\" .github/workflows",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete GitHub Actions Supply Chain for a production operations environment: Pin third-party actions and review workflow permissions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `rg \"uses:\" .github/workflows`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Pin third-party actions and review workflow permissions.\n- The verification command or evidence path succeeds: `rg \"uses:\" .github/workflows`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `rg \"uses:\" .github/workflows` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "container-vuln-triage",
    "slug": "container-vuln-triage",
    "category": "security-ops",
    "title": "Container Vulnerability Triage",
    "intent": "Prioritize image CVEs by exploitability and runtime exposure.",
    "verify": "trivy image IMAGE",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Container Vulnerability Triage for a production operations environment: Prioritize image CVEs by exploitability and runtime exposure.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `trivy image IMAGE`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prioritize image CVEs by exploitability and runtime exposure.\n- The verification command or evidence path succeeds: `trivy image IMAGE`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `trivy image IMAGE` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "audit-log-coverage",
    "slug": "audit-log-coverage",
    "category": "security-ops",
    "title": "Audit Log Coverage",
    "intent": "Add audit logs for login, permission changes, and sensitive data access.",
    "verify": "pytest -k audit_log",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Audit Log Coverage for a production operations environment: Add audit logs for login, permission changes, and sensitive data access.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `pytest -k audit_log`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add audit logs for login, permission changes, and sensitive data access.\n- The verification command or evidence path succeeds: `pytest -k audit_log`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k audit_log` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "secret-rotation-drill",
    "slug": "secret-rotation-drill",
    "category": "security-ops",
    "title": "Secret Rotation Drill",
    "intent": "Verify rotating a key does not interrupt the service.",
    "verify": "npm run smoke",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Secret Rotation Drill for a production operations environment: Verify rotating a key does not interrupt the service.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `npm run smoke`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify rotating a key does not interrupt the service.\n- The verification command or evidence path succeeds: `npm run smoke`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run smoke` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "dependency-confusion-guard",
    "slug": "dependency-confusion-guard",
    "category": "security-ops",
    "title": "Dependency Confusion Guard",
    "intent": "Lock private package scopes and registries to prevent wrong-source installs.",
    "verify": "npm ci",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Dependency Confusion Guard for a production operations environment: Lock private package scopes and registries to prevent wrong-source installs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `npm ci`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Lock private package scopes and registries to prevent wrong-source installs.\n- The verification command or evidence path succeeds: `npm ci`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm ci` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "sbom-generation",
    "slug": "sbom-generation",
    "category": "security-ops",
    "title": "SBOM Generation",
    "intent": "Generate an SBOM and attach it to release artifacts.",
    "verify": "syft packages dir:.",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete SBOM Generation for a production operations environment: Generate an SBOM and attach it to release artifacts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `syft packages dir:.`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Generate an SBOM and attach it to release artifacts.\n- The verification command or evidence path succeeds: `syft packages dir:.`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `syft packages dir:.` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "prod-access-review",
    "slug": "prod-access-review",
    "category": "security-ops",
    "title": "Production Access Review",
    "intent": "Inventory production access, approval paths, and audit evidence.",
    "verify": "terraform state list",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Production Access Review for a production operations environment: Inventory production access, approval paths, and audit evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `terraform state list`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Inventory production access, approval paths, and audit evidence.\n- The verification command or evidence path succeeds: `terraform state list`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `terraform state list` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "backup-restore-security",
    "slug": "backup-restore-security",
    "category": "security-ops",
    "title": "Backup Restore Security",
    "intent": "Verify encrypted backups and a restricted restore path.",
    "verify": "./scripts/restore-dry-run.sh",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Backup Restore Security for a production operations environment: Verify encrypted backups and a restricted restore path.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `./scripts/restore-dry-run.sh`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify encrypted backups and a restricted restore path.\n- The verification command or evidence path succeeds: `./scripts/restore-dry-run.sh`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `./scripts/restore-dry-run.sh` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "etl-contract-tests",
    "slug": "etl-contract-tests",
    "category": "data-eng",
    "title": "ETL Contract Tests",
    "intent": "Add schema and sample-data contracts between source and target tables.",
    "verify": "pytest tests/etl",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete ETL Contract Tests for a data pipeline project: Add schema and sample-data contracts between source and target tables.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest tests/etl`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add schema and sample-data contracts between source and target tables.\n- The verification command or evidence path succeeds: `pytest tests/etl`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/etl` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "data-quality-rules",
    "slug": "data-quality-rules",
    "category": "data-eng",
    "title": "Data Quality Rules",
    "intent": "Define null, uniqueness, range, and reference checks for key datasets.",
    "verify": "great_expectations checkpoint run main",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Quality Rules for a data pipeline project: Define null, uniqueness, range, and reference checks for key datasets.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `great_expectations checkpoint run main`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define null, uniqueness, range, and reference checks for key datasets.\n- The verification command or evidence path succeeds: `great_expectations checkpoint run main`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `great_expectations checkpoint run main` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "backfill-safety-plan",
    "slug": "backfill-safety-plan",
    "category": "data-eng",
    "title": "Backfill Safety Plan",
    "intent": "Design a sharded, resumable, verifiable historical backfill.",
    "verify": "pytest -k backfill",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Backfill Safety Plan for a data pipeline project: Design a sharded, resumable, verifiable historical backfill.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k backfill`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Design a sharded, resumable, verifiable historical backfill.\n- The verification command or evidence path succeeds: `pytest -k backfill`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k backfill` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "incremental-load-watermark",
    "slug": "incremental-load-watermark",
    "category": "data-eng",
    "title": "Incremental Load Watermark",
    "intent": "Fix missing or duplicate rows in incremental sync logic.",
    "verify": "pytest -k watermark",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Incremental Load Watermark for a data pipeline project: Fix missing or duplicate rows in incremental sync logic.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k watermark`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix missing or duplicate rows in incremental sync logic.\n- The verification command or evidence path succeeds: `pytest -k watermark`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k watermark` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "late-arriving-data",
    "slug": "late-arriving-data",
    "category": "data-eng",
    "title": "Late-Arriving Data",
    "intent": "Handle delayed events and metric corrections safely.",
    "verify": "pytest -k late_arrival",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Late-Arriving Data for a data pipeline project: Handle delayed events and metric corrections safely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k late_arrival`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Handle delayed events and metric corrections safely.\n- The verification command or evidence path succeeds: `pytest -k late_arrival`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k late_arrival` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "data-lineage-map",
    "slug": "data-lineage-map",
    "category": "data-eng",
    "title": "Data Lineage Map",
    "intent": "Map critical report fields from source to consumers.",
    "verify": "dbt docs generate",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Lineage Map for a data pipeline project: Map critical report fields from source to consumers.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `dbt docs generate`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Map critical report fields from source to consumers.\n- The verification command or evidence path succeeds: `dbt docs generate`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt docs generate` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "pii-classification",
    "slug": "pii-classification",
    "category": "data-eng",
    "title": "PII Classification",
    "intent": "Classify sensitive fields and document masking rules.",
    "verify": "pytest -k pii",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete PII Classification for a data pipeline project: Classify sensitive fields and document masking rules.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k pii`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Classify sensitive fields and document masking rules.\n- The verification command or evidence path succeeds: `pytest -k pii`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k pii` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "data-retention-enforcement",
    "slug": "data-retention-enforcement",
    "category": "data-eng",
    "title": "Data Retention Enforcement",
    "intent": "Verify expiration, archival, deletion, and audit behavior.",
    "verify": "pytest -k retention",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Retention Enforcement for a data pipeline project: Verify expiration, archival, deletion, and audit behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k retention`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify expiration, archival, deletion, and audit behavior.\n- The verification command or evidence path succeeds: `pytest -k retention`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k retention` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "warehouse-cost-audit",
    "slug": "warehouse-cost-audit",
    "category": "data-eng",
    "title": "Warehouse Cost Audit",
    "intent": "Find expensive queries, duplicate tables, and unused scheduled jobs.",
    "verify": "dbt test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Warehouse Cost Audit for a data pipeline project: Find expensive queries, duplicate tables, and unused scheduled jobs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `dbt test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find expensive queries, duplicate tables, and unused scheduled jobs.\n- The verification command or evidence path succeeds: `dbt test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "stream-processing-lag",
    "slug": "stream-processing-lag",
    "category": "data-eng",
    "title": "Stream Processing Lag",
    "intent": "Diagnose Kafka/Flink/Spark lag and checkpoint bottlenecks.",
    "verify": "pytest -k stream_lag",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Stream Processing Lag for a data pipeline project: Diagnose Kafka/Flink/Spark lag and checkpoint bottlenecks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `pytest -k stream_lag`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Diagnose Kafka/Flink/Spark lag and checkpoint bottlenecks.\n- The verification command or evidence path succeeds: `pytest -k stream_lag`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k stream_lag` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "metric-definition-lock",
    "slug": "metric-definition-lock",
    "category": "data-analytics",
    "title": "Metric Definition Lock",
    "intent": "Turn core metric definitions into tested SQL or semantic-layer checks.",
    "verify": "dbt test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Metric Definition Lock for an analytics or BI project: Turn core metric definitions into tested SQL or semantic-layer checks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `dbt test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Turn core metric definitions into tested SQL or semantic-layer checks.\n- The verification command or evidence path succeeds: `dbt test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "dashboard-trust-audit",
    "slug": "dashboard-trust-audit",
    "category": "data-analytics",
    "title": "Dashboard Trust Audit",
    "intent": "Check filters, timezone, refresh cadence, permissions, and source reconciliation.",
    "verify": "dbt test && pytest tests/dashboard",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Dashboard Trust Audit for an analytics or BI project: Check filters, timezone, refresh cadence, permissions, and source reconciliation.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `dbt test && pytest tests/dashboard`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check filters, timezone, refresh cadence, permissions, and source reconciliation.\n- The verification command or evidence path succeeds: `dbt test && pytest tests/dashboard`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test && pytest tests/dashboard` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ab-test-srm-check",
    "slug": "ab-test-srm-check",
    "category": "data-analytics",
    "title": "A/B Test SRM Check",
    "intent": "Detect sample ratio mismatch in experiment assignment.",
    "verify": "pytest -k srm",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete A/B Test SRM Check for an analytics or BI project: Detect sample ratio mismatch in experiment assignment.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `pytest -k srm`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Detect sample ratio mismatch in experiment assignment.\n- The verification command or evidence path succeeds: `pytest -k srm`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k srm` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "funnel-dropoff-diagnosis",
    "slug": "funnel-dropoff-diagnosis",
    "category": "data-analytics",
    "title": "Funnel Dropoff Diagnosis",
    "intent": "Validate funnel events, step counts, and latency before interpreting dropoff.",
    "verify": "pytest -k funnel",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Funnel Dropoff Diagnosis for an analytics or BI project: Validate funnel events, step counts, and latency before interpreting dropoff.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `pytest -k funnel`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Validate funnel events, step counts, and latency before interpreting dropoff.\n- The verification command or evidence path succeeds: `pytest -k funnel`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k funnel` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "cohort-retention-query",
    "slug": "cohort-retention-query",
    "category": "data-analytics",
    "title": "Cohort Retention Query",
    "intent": "Create reusable retention SQL with hand-checked small samples.",
    "verify": "dbt test -s retention",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Cohort Retention Query for an analytics or BI project: Create reusable retention SQL with hand-checked small samples.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `dbt test -s retention`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create reusable retention SQL with hand-checked small samples.\n- The verification command or evidence path succeeds: `dbt test -s retention`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test -s retention` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "revenue-reconciliation",
    "slug": "revenue-reconciliation",
    "category": "data-analytics",
    "title": "Revenue Reconciliation",
    "intent": "Reconcile payments, orders, refunds, and finance definitions.",
    "verify": "pytest -k revenue_reconciliation",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Revenue Reconciliation for an analytics or BI project: Reconcile payments, orders, refunds, and finance definitions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `pytest -k revenue_reconciliation`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reconcile payments, orders, refunds, and finance definitions.\n- The verification command or evidence path succeeds: `pytest -k revenue_reconciliation`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k revenue_reconciliation` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "event-taxonomy-cleanup",
    "slug": "event-taxonomy-cleanup",
    "category": "data-analytics",
    "title": "Event Taxonomy Cleanup",
    "intent": "Deduplicate event names, properties, and version changes.",
    "verify": "pytest -k event_schema",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Event Taxonomy Cleanup for an analytics or BI project: Deduplicate event names, properties, and version changes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `pytest -k event_schema`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Deduplicate event names, properties, and version changes.\n- The verification command or evidence path succeeds: `pytest -k event_schema`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k event_schema` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "anomaly-detection-baseline",
    "slug": "anomaly-detection-baseline",
    "category": "data-analytics",
    "title": "Anomaly Detection Baseline",
    "intent": "Backtest alert thresholds against historical metrics.",
    "verify": "pytest -k anomaly",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Anomaly Detection Baseline for an analytics or BI project: Backtest alert thresholds against historical metrics.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `pytest -k anomaly`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Backtest alert thresholds against historical metrics.\n- The verification command or evidence path succeeds: `pytest -k anomaly`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k anomaly` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "attribution-window-review",
    "slug": "attribution-window-review",
    "category": "data-analytics",
    "title": "Attribution Window Review",
    "intent": "Verify campaign attribution windows and dedupe rules.",
    "verify": "dbt test -s attribution",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Attribution Window Review for an analytics or BI project: Verify campaign attribution windows and dedupe rules.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `dbt test -s attribution`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify campaign attribution windows and dedupe rules.\n- The verification command or evidence path succeeds: `dbt test -s attribution`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test -s attribution` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "self-serve-data-contract",
    "slug": "self-serve-data-contract",
    "category": "data-analytics",
    "title": "Self-Serve Data Contract",
    "intent": "Define trusted datasets and usage limits for business users.",
    "verify": "dbt test -s semantic",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Self-Serve Data Contract for an analytics or BI project: Define trusted datasets and usage limits for business users.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `dbt test -s semantic`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define trusted datasets and usage limits for business users.\n- The verification command or evidence path succeeds: `dbt test -s semantic`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `dbt test -s semantic` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "llm-golden-set-build",
    "slug": "llm-golden-set-build",
    "category": "ai-evals",
    "title": "LLM Golden Set Build",
    "intent": "Build an eval set from real failures and frequent tasks.",
    "verify": "pytest evals",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete LLM Golden Set Build for an AI evaluation project: Build an eval set from real failures and frequent tasks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build an eval set from real failures and frequent tasks.\n- The verification command or evidence path succeeds: `pytest evals`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "llm-regression-gate",
    "slug": "llm-regression-gate",
    "category": "ai-evals",
    "title": "LLM Regression Gate",
    "intent": "Compare old and new model or prompt outputs in PRs.",
    "verify": "pytest evals",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete LLM Regression Gate for an AI evaluation project: Compare old and new model or prompt outputs in PRs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare old and new model or prompt outputs in PRs.\n- The verification command or evidence path succeeds: `pytest evals`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "judge-calibration",
    "slug": "judge-calibration",
    "category": "ai-evals",
    "title": "Judge Calibration",
    "intent": "Measure LLM judge agreement against human labels.",
    "verify": "pytest evals/judges",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Judge Calibration for an AI evaluation project: Measure LLM judge agreement against human labels.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/judges`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Measure LLM judge agreement against human labels.\n- The verification command or evidence path succeeds: `pytest evals/judges`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/judges` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "hallucination-probe-suite",
    "slug": "hallucination-probe-suite",
    "category": "ai-evals",
    "title": "Hallucination Probe Suite",
    "intent": "Add negative cases for nonexistent files, fields, APIs, and sources.",
    "verify": "pytest evals/hallucination",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Hallucination Probe Suite for an AI evaluation project: Add negative cases for nonexistent files, fields, APIs, and sources.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/hallucination`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add negative cases for nonexistent files, fields, APIs, and sources.\n- The verification command or evidence path succeeds: `pytest evals/hallucination`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/hallucination` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "rag-answer-faithfulness",
    "slug": "rag-answer-faithfulness",
    "category": "ai-evals",
    "title": "RAG Answer Faithfulness",
    "intent": "Check that answers are supported by retrieved evidence.",
    "verify": "pytest evals/rag",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete RAG Answer Faithfulness for an AI evaluation project: Check that answers are supported by retrieved evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/rag`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check that answers are supported by retrieved evidence.\n- The verification command or evidence path succeeds: `pytest evals/rag`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/rag` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "tool-use-eval",
    "slug": "tool-use-eval",
    "category": "ai-evals",
    "title": "Tool Use Eval",
    "intent": "Evaluate whether an agent selects, orders, and validates tools correctly.",
    "verify": "pytest evals/tool_use",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Tool Use Eval for an AI evaluation project: Evaluate whether an agent selects, orders, and validates tools correctly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/tool_use`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Evaluate whether an agent selects, orders, and validates tools correctly.\n- The verification command or evidence path succeeds: `pytest evals/tool_use`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/tool_use` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "adversarial-prompt-redteam",
    "slug": "adversarial-prompt-redteam",
    "category": "ai-evals",
    "title": "Prompt Injection Red Team",
    "intent": "Test prompt leakage, unauthorized tools, and instruction override attempts.",
    "verify": "pytest evals/redteam",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Prompt Injection Red Team for an AI evaluation project: Test prompt leakage, unauthorized tools, and instruction override attempts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/redteam`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Test prompt leakage, unauthorized tools, and instruction override attempts.\n- The verification command or evidence path succeeds: `pytest evals/redteam`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/redteam` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "eval-data-dedup",
    "slug": "eval-data-dedup",
    "category": "ai-evals",
    "title": "Eval Data Dedup",
    "intent": "Remove duplicates, leakage, and near-identical eval samples.",
    "verify": "python scripts/dedup_evals.py",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Eval Data Dedup for an AI evaluation project: Remove duplicates, leakage, and near-identical eval samples.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `python scripts/dedup_evals.py`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Remove duplicates, leakage, and near-identical eval samples.\n- The verification command or evidence path succeeds: `python scripts/dedup_evals.py`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `python scripts/dedup_evals.py` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "cost-quality-frontier",
    "slug": "cost-quality-frontier",
    "category": "ai-evals",
    "title": "Cost Quality Frontier",
    "intent": "Compare models by quality, latency, and cost to choose routing tiers.",
    "verify": "pytest evals --record-costs",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Cost Quality Frontier for an AI evaluation project: Compare models by quality, latency, and cost to choose routing tiers.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals --record-costs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare models by quality, latency, and cost to choose routing tiers.\n- The verification command or evidence path succeeds: `pytest evals --record-costs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals --record-costs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "rubric-driven-eval",
    "slug": "rubric-driven-eval",
    "category": "ai-evals",
    "title": "Rubric-Driven Eval",
    "intent": "Replace binary scores with multi-dimensional rubrics for complex tasks.",
    "verify": "pytest evals/rubrics",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Rubric-Driven Eval for an AI evaluation project: Replace binary scores with multi-dimensional rubrics for complex tasks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `pytest evals/rubrics`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace binary scores with multi-dimensional rubrics for complex tasks.\n- The verification command or evidence path succeeds: `pytest evals/rubrics`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/rubrics` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "prompt-version-registry",
    "slug": "prompt-version-registry",
    "category": "ai-ops",
    "title": "Prompt Version Registry",
    "intent": "Bind prompt versions to eval results and deployment history.",
    "verify": "pytest tests/prompt_registry",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Prompt Version Registry for an AI application runtime: Bind prompt versions to eval results and deployment history.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/prompt_registry`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Bind prompt versions to eval results and deployment history.\n- The verification command or evidence path succeeds: `pytest tests/prompt_registry`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/prompt_registry` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "rag-chunking-experiment",
    "slug": "rag-chunking-experiment",
    "category": "ai-ops",
    "title": "RAG Chunking Experiment",
    "intent": "Compare chunk size, overlap, and metadata on retrieval and answer quality.",
    "verify": "pytest evals/rag_chunking",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete RAG Chunking Experiment for an AI application runtime: Compare chunk size, overlap, and metadata on retrieval and answer quality.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest evals/rag_chunking`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Compare chunk size, overlap, and metadata on retrieval and answer quality.\n- The verification command or evidence path succeeds: `pytest evals/rag_chunking`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/rag_chunking` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "vector-index-refresh",
    "slug": "vector-index-refresh",
    "category": "ai-ops",
    "title": "Vector Index Refresh",
    "intent": "Verify document updates are indexed completely and can be rolled back.",
    "verify": "pytest tests/index_refresh",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Vector Index Refresh for an AI application runtime: Verify document updates are indexed completely and can be rolled back.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/index_refresh`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify document updates are indexed completely and can be rolled back.\n- The verification command or evidence path succeeds: `pytest tests/index_refresh`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/index_refresh` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "model-routing-policy",
    "slug": "model-routing-policy",
    "category": "ai-ops",
    "title": "Model Routing Policy",
    "intent": "Route by risk, cost, latency, and quality evidence.",
    "verify": "pytest tests/model_routing",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Model Routing Policy for an AI application runtime: Route by risk, cost, latency, and quality evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/model_routing`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Route by risk, cost, latency, and quality evidence.\n- The verification command or evidence path succeeds: `pytest tests/model_routing`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/model_routing` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "llm-timeout-budget",
    "slug": "llm-timeout-budget",
    "category": "ai-ops",
    "title": "LLM Timeout Budget",
    "intent": "Define timeout, retry, fallback, and user-visible error behavior.",
    "verify": "pytest tests/llm_timeouts",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete LLM Timeout Budget for an AI application runtime: Define timeout, retry, fallback, and user-visible error behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/llm_timeouts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define timeout, retry, fallback, and user-visible error behavior.\n- The verification command or evidence path succeeds: `pytest tests/llm_timeouts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/llm_timeouts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "token-cost-attribution",
    "slug": "token-cost-attribution",
    "category": "ai-ops",
    "title": "Token Cost Attribution",
    "intent": "Attribute model costs by user, feature, model, and request ID.",
    "verify": "pytest tests/costs",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Token Cost Attribution for an AI application runtime: Attribute model costs by user, feature, model, and request ID.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/costs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Attribute model costs by user, feature, model, and request ID.\n- The verification command or evidence path succeeds: `pytest tests/costs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/costs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "prompt-injection-filter",
    "slug": "prompt-injection-filter",
    "category": "ai-ops",
    "title": "RAG Prompt Injection Filter",
    "intent": "Detect and isolate malicious instructions in retrieved documents.",
    "verify": "pytest evals/prompt_injection",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete RAG Prompt Injection Filter for an AI application runtime: Detect and isolate malicious instructions in retrieved documents.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest evals/prompt_injection`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Detect and isolate malicious instructions in retrieved documents.\n- The verification command or evidence path succeeds: `pytest evals/prompt_injection`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest evals/prompt_injection` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ai-output-schema-guard",
    "slug": "ai-output-schema-guard",
    "category": "ai-ops",
    "title": "AI Output Schema Guard",
    "intent": "Validate structured AI output and fail or retry safely.",
    "verify": "pytest tests/schema_guard",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete AI Output Schema Guard for an AI application runtime: Validate structured AI output and fail or retry safely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/schema_guard`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Validate structured AI output and fail or retry safely.\n- The verification command or evidence path succeeds: `pytest tests/schema_guard`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/schema_guard` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "human-review-threshold",
    "slug": "human-review-threshold",
    "category": "ai-ops",
    "title": "Human Review Threshold",
    "intent": "Escalate high-risk AI outputs based on confidence and policy rules.",
    "verify": "pytest tests/human_review",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Human Review Threshold for an AI application runtime: Escalate high-risk AI outputs based on confidence and policy rules.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/human_review`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Escalate high-risk AI outputs based on confidence and policy rules.\n- The verification command or evidence path succeeds: `pytest tests/human_review`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/human_review` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "ai-observability-traces",
    "slug": "ai-observability-traces",
    "category": "ai-ops",
    "title": "AI Observability Traces",
    "intent": "Trace prompts, retrieval, tools, models, scores, and request IDs.",
    "verify": "pytest tests/tracing",
    "difficulty": "advanced",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete AI Observability Traces for an AI application runtime: Trace prompts, retrieval, tools, models, scores, and request IDs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `pytest tests/tracing`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Trace prompts, retrieval, tools, models, scores, and request IDs.\n- The verification command or evidence path succeeds: `pytest tests/tracing`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/tracing` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-empty-states",
    "slug": "frontend-empty-states",
    "category": "frontend",
    "title": "Empty State System",
    "intent": "Design real empty states for lists, search, permissions, and first use.",
    "verify": "npm run test -- EmptyState",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Empty State System for a web frontend application: Design real empty states for lists, search, permissions, and first use.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run test -- EmptyState`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Design real empty states for lists, search, permissions, and first use.\n- The verification command or evidence path succeeds: `npm run test -- EmptyState`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run test -- EmptyState` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-error-boundary",
    "slug": "frontend-error-boundary",
    "category": "frontend",
    "title": "Error Boundary Experience",
    "intent": "Add recoverable page and component fallback UI for crashes.",
    "verify": "npm test -- ErrorBoundary",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Error Boundary Experience for a web frontend application: Add recoverable page and component fallback UI for crashes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm test -- ErrorBoundary`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add recoverable page and component fallback UI for crashes.\n- The verification command or evidence path succeeds: `npm test -- ErrorBoundary`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- ErrorBoundary` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-loading-skeletons",
    "slug": "frontend-loading-skeletons",
    "category": "frontend",
    "title": "Loading Skeletons",
    "intent": "Replace layout-shifting spinners with stable skeleton states.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Loading Skeletons for a web frontend application: Replace layout-shifting spinners with stable skeleton states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace layout-shifting spinners with stable skeleton states.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-form-validation",
    "slug": "frontend-form-validation",
    "category": "frontend",
    "title": "Form Validation",
    "intent": "Cover inline, submit, server error, and dirty-state validation.",
    "verify": "npm test -- form",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Form Validation for a web frontend application: Cover inline, submit, server error, and dirty-state validation.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm test -- form`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Cover inline, submit, server error, and dirty-state validation.\n- The verification command or evidence path succeeds: `npm test -- form`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- form` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-table-density",
    "slug": "frontend-table-density",
    "category": "frontend",
    "title": "Data Table Density",
    "intent": "Improve columns, filters, sorting, pagination, and bulk actions.",
    "verify": "npx playwright test table.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Table Density for a web frontend application: Improve columns, filters, sorting, pagination, and bulk actions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test table.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Improve columns, filters, sorting, pagination, and bulk actions.\n- The verification command or evidence path succeeds: `npx playwright test table.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test table.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-command-palette",
    "slug": "frontend-command-palette",
    "category": "frontend",
    "title": "Command Palette",
    "intent": "Add a keyboard-first entry point for high-frequency actions.",
    "verify": "npx playwright test command-palette.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Command Palette for a web frontend application: Add a keyboard-first entry point for high-frequency actions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test command-palette.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add a keyboard-first entry point for high-frequency actions.\n- The verification command or evidence path succeeds: `npx playwright test command-palette.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test command-palette.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-navigation-map",
    "slug": "frontend-navigation-map",
    "category": "frontend",
    "title": "Navigation Map",
    "intent": "Clarify primary navigation, breadcrumbs, and detail-page return paths.",
    "verify": "npx playwright test navigation.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Navigation Map for a web frontend application: Clarify primary navigation, breadcrumbs, and detail-page return paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test navigation.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Clarify primary navigation, breadcrumbs, and detail-page return paths.\n- The verification command or evidence path succeeds: `npx playwright test navigation.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test navigation.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-state-recovery",
    "slug": "frontend-state-recovery",
    "category": "frontend",
    "title": "State Recovery",
    "intent": "Restore filters and context after refresh, back, and deep links.",
    "verify": "npx playwright test state-recovery.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete State Recovery for a web frontend application: Restore filters and context after refresh, back, and deep links.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test state-recovery.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Restore filters and context after refresh, back, and deep links.\n- The verification command or evidence path succeeds: `npx playwright test state-recovery.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test state-recovery.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-permission-ui",
    "slug": "frontend-permission-ui",
    "category": "frontend",
    "title": "Permission State UI",
    "intent": "Separate unauthenticated, unauthorized, and missing-resource states.",
    "verify": "npx playwright test permissions.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Permission State UI for a web frontend application: Separate unauthenticated, unauthorized, and missing-resource states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test permissions.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Separate unauthenticated, unauthorized, and missing-resource states.\n- The verification command or evidence path succeeds: `npx playwright test permissions.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test permissions.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-bulk-actions",
    "slug": "frontend-bulk-actions",
    "category": "frontend",
    "title": "Bulk Actions",
    "intent": "Handle selection, confirm, undo, partial failure, and feedback.",
    "verify": "npx playwright test bulk-actions.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Bulk Actions for a web frontend application: Handle selection, confirm, undo, partial failure, and feedback.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test bulk-actions.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Handle selection, confirm, undo, partial failure, and feedback.\n- The verification command or evidence path succeeds: `npx playwright test bulk-actions.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test bulk-actions.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-search-filter",
    "slug": "frontend-search-filter",
    "category": "frontend",
    "title": "Search Filter Experience",
    "intent": "Unify search, filter chips, clear actions, and result counts.",
    "verify": "npx playwright test search-filter.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Search Filter Experience for a web frontend application: Unify search, filter chips, clear actions, and result counts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test search-filter.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Unify search, filter chips, clear actions, and result counts.\n- The verification command or evidence path succeeds: `npx playwright test search-filter.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test search-filter.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "frontend-realtime-updates",
    "slug": "frontend-realtime-updates",
    "category": "frontend",
    "title": "Realtime Update Prompts",
    "intent": "Handle background changes, conflicts, and refresh prompts.",
    "verify": "npx playwright test realtime.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Realtime Update Prompts for a web frontend application: Handle background changes, conflicts, and refresh prompts.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test realtime.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Handle background changes, conflicts, and refresh prompts.\n- The verification command or evidence path succeeds: `npx playwright test realtime.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test realtime.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-visual-hierarchy",
    "slug": "design-visual-hierarchy",
    "category": "design",
    "title": "Visual Hierarchy Pass",
    "intent": "Reorder headings, metadata, primary actions, and secondary actions.",
    "verify": "npx playwright test visual-hierarchy.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Visual Hierarchy Pass for a product UI codebase: Reorder headings, metadata, primary actions, and secondary actions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test visual-hierarchy.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reorder headings, metadata, primary actions, and secondary actions.\n- The verification command or evidence path succeeds: `npx playwright test visual-hierarchy.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test visual-hierarchy.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-token-audit",
    "slug": "design-token-audit",
    "category": "design",
    "title": "Design Token Audit",
    "intent": "Check colors, spacing, radii, and shadows against tokens.",
    "verify": "npm run lint:styles",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Design Token Audit for a product UI codebase: Check colors, spacing, radii, and shadows against tokens.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run lint:styles`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check colors, spacing, radii, and shadows against tokens.\n- The verification command or evidence path succeeds: `npm run lint:styles`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lint:styles` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-component-variants",
    "slug": "design-component-variants",
    "category": "design",
    "title": "Component Variant Matrix",
    "intent": "Complete button, input, card, and modal state coverage.",
    "verify": "npm run storybook:test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Component Variant Matrix for a product UI codebase: Complete button, input, card, and modal state coverage.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run storybook:test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Complete button, input, card, and modal state coverage.\n- The verification command or evidence path succeeds: `npm run storybook:test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run storybook:test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-dashboard-layout",
    "slug": "design-dashboard-layout",
    "category": "design",
    "title": "Dashboard Layout Pass",
    "intent": "Make an operational dashboard easier to scan and compare.",
    "verify": "npx playwright test dashboard.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Dashboard Layout Pass for a product UI codebase: Make an operational dashboard easier to scan and compare.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test dashboard.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Make an operational dashboard easier to scan and compare.\n- The verification command or evidence path succeeds: `npx playwright test dashboard.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test dashboard.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-modal-discipline",
    "slug": "design-modal-discipline",
    "category": "design",
    "title": "Modal Discipline",
    "intent": "Replace modal misuse with drawers, popovers, or pages where appropriate.",
    "verify": "npx playwright test modal.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Modal Discipline for a product UI codebase: Replace modal misuse with drawers, popovers, or pages where appropriate.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test modal.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace modal misuse with drawers, popovers, or pages where appropriate.\n- The verification command or evidence path succeeds: `npx playwright test modal.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test modal.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-iconography",
    "slug": "design-iconography",
    "category": "design",
    "title": "Iconography System",
    "intent": "Unify icon semantics for tools, statuses, and empty states.",
    "verify": "npm run lint:icons",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Iconography System for a product UI codebase: Unify icon semantics for tools, statuses, and empty states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run lint:icons`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Unify icon semantics for tools, statuses, and empty states.\n- The verification command or evidence path succeeds: `npm run lint:icons`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lint:icons` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-color-contrast",
    "slug": "design-color-contrast",
    "category": "design",
    "title": "Color Contrast Pass",
    "intent": "Fix low contrast text, icons, and state colors.",
    "verify": "npx axe http://localhost:3000",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Color Contrast Pass for a product UI codebase: Fix low contrast text, icons, and state colors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix low contrast text, icons, and state colors.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-motion-rules",
    "slug": "design-motion-rules",
    "category": "design",
    "title": "Motion Rules",
    "intent": "Define entry, exit, feedback, and reduced-motion behavior.",
    "verify": "npx playwright test motion.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Motion Rules for a product UI codebase: Define entry, exit, feedback, and reduced-motion behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test motion.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define entry, exit, feedback, and reduced-motion behavior.\n- The verification command or evidence path succeeds: `npx playwright test motion.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test motion.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-responsive-grid",
    "slug": "design-responsive-grid",
    "category": "design",
    "title": "Responsive Grid",
    "intent": "Define breakpoints, columns, and fixed-format constraints.",
    "verify": "npx playwright test responsive.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Responsive Grid for a product UI codebase: Define breakpoints, columns, and fixed-format constraints.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test responsive.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define breakpoints, columns, and fixed-format constraints.\n- The verification command or evidence path succeeds: `npx playwright test responsive.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test responsive.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-toolbar-usability",
    "slug": "design-toolbar-usability",
    "category": "design",
    "title": "Toolbar Usability",
    "intent": "Improve icon buttons, tooltips, grouping, and disabled states.",
    "verify": "npx playwright test toolbar.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Toolbar Usability for a product UI codebase: Improve icon buttons, tooltips, grouping, and disabled states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test toolbar.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Improve icon buttons, tooltips, grouping, and disabled states.\n- The verification command or evidence path succeeds: `npx playwright test toolbar.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test toolbar.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-data-card-system",
    "slug": "design-data-card-system",
    "category": "design",
    "title": "Data Card System",
    "intent": "Define metric cards with value, trend, anomaly, and source states.",
    "verify": "npm run storybook:test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Card System for a product UI codebase: Define metric cards with value, trend, anomaly, and source states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npm run storybook:test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define metric cards with value, trend, anomaly, and source states.\n- The verification command or evidence path succeeds: `npm run storybook:test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run storybook:test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "design-brand-fit",
    "slug": "design-brand-fit",
    "category": "design",
    "title": "Brand Fit Pass",
    "intent": "Align the interface language with the product's audience and use case.",
    "verify": "npx playwright test brand.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Brand Fit Pass for a product UI codebase: Align the interface language with the product's audience and use case.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `npx playwright test brand.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Align the interface language with the product's audience and use case.\n- The verification command or evidence path succeeds: `npx playwright test brand.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test brand.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-bottom-nav",
    "slug": "mobile-bottom-nav",
    "category": "mobile",
    "title": "Mobile Bottom Navigation",
    "intent": "Design thumb-friendly mobile navigation for core paths.",
    "verify": "npx playwright test --project=mobile navigation.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Bottom Navigation for a mobile or responsive application: Design thumb-friendly mobile navigation for core paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile navigation.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Design thumb-friendly mobile navigation for core paths.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile navigation.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile navigation.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-touch-targets",
    "slug": "mobile-touch-targets",
    "category": "mobile",
    "title": "Mobile Touch Targets",
    "intent": "Ensure buttons, checkboxes, and rows have usable tap areas.",
    "verify": "npx playwright test --project=mobile touch.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Touch Targets for a mobile or responsive application: Ensure buttons, checkboxes, and rows have usable tap areas.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile touch.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ensure buttons, checkboxes, and rows have usable tap areas.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile touch.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile touch.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-form-flow",
    "slug": "mobile-form-flow",
    "category": "mobile",
    "title": "Mobile Form Flow",
    "intent": "Handle long forms, keyboard occlusion, and error positioning.",
    "verify": "npx playwright test --project=mobile form.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Form Flow for a mobile or responsive application: Handle long forms, keyboard occlusion, and error positioning.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile form.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Handle long forms, keyboard occlusion, and error positioning.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile form.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile form.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-table-adaptation",
    "slug": "mobile-table-adaptation",
    "category": "mobile",
    "title": "Mobile Table Adaptation",
    "intent": "Convert wide tables into cards, horizontal scroll, or drill-downs.",
    "verify": "npx playwright test --project=mobile table.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Table Adaptation for a mobile or responsive application: Convert wide tables into cards, horizontal scroll, or drill-downs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile table.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Convert wide tables into cards, horizontal scroll, or drill-downs.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile table.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile table.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-filter-drawer",
    "slug": "mobile-filter-drawer",
    "category": "mobile",
    "title": "Mobile Filter Drawer",
    "intent": "Add mobile filters with apply, reset, count, and URL state.",
    "verify": "npx playwright test --project=mobile filter.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Filter Drawer for a mobile or responsive application: Add mobile filters with apply, reset, count, and URL state.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile filter.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add mobile filters with apply, reset, count, and URL state.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile filter.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile filter.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-offline-state",
    "slug": "mobile-offline-state",
    "category": "mobile",
    "title": "Mobile Offline State",
    "intent": "Show offline, cached data, and retry paths clearly.",
    "verify": "npx playwright test --project=mobile offline.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Offline State for a mobile or responsive application: Show offline, cached data, and retry paths clearly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile offline.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Show offline, cached data, and retry paths clearly.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile offline.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile offline.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-image-performance",
    "slug": "mobile-image-performance",
    "category": "mobile",
    "title": "Mobile Image Performance",
    "intent": "Optimize image sizes, lazy loading, placeholders, and formats.",
    "verify": "npm run lighthouse:mobile",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Image Performance for a mobile or responsive application: Optimize image sizes, lazy loading, placeholders, and formats.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse:mobile`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Optimize image sizes, lazy loading, placeholders, and formats.\n- The verification command or evidence path succeeds: `npm run lighthouse:mobile`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse:mobile` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-safe-area",
    "slug": "mobile-safe-area",
    "category": "mobile",
    "title": "Mobile Safe Area",
    "intent": "Handle iOS notch, bottom bars, and sticky actions.",
    "verify": "npx playwright test --project=mobile safe-area.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Safe Area for a mobile or responsive application: Handle iOS notch, bottom bars, and sticky actions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile safe-area.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Handle iOS notch, bottom bars, and sticky actions.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile safe-area.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile safe-area.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-gesture-conflicts",
    "slug": "mobile-gesture-conflicts",
    "category": "mobile",
    "title": "Mobile Gesture Conflicts",
    "intent": "Resolve conflicts between swipe, drag, and scroll interactions.",
    "verify": "npx playwright test --project=mobile gestures.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Gesture Conflicts for a mobile or responsive application: Resolve conflicts between swipe, drag, and scroll interactions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile gestures.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Resolve conflicts between swipe, drag, and scroll interactions.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile gestures.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile gestures.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-login-flow",
    "slug": "mobile-login-flow",
    "category": "mobile",
    "title": "Mobile Login Flow",
    "intent": "Improve magic link, OTP, password manager, and autofill behavior.",
    "verify": "npx playwright test --project=mobile login.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Login Flow for a mobile or responsive application: Improve magic link, OTP, password manager, and autofill behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile login.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Improve magic link, OTP, password manager, and autofill behavior.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile login.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile login.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-onboarding",
    "slug": "mobile-onboarding",
    "category": "mobile",
    "title": "Mobile Onboarding",
    "intent": "Create a short, skippable, restorable first-run path.",
    "verify": "npx playwright test --project=mobile onboarding.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Onboarding for a mobile or responsive application: Create a short, skippable, restorable first-run path.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile onboarding.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create a short, skippable, restorable first-run path.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile onboarding.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile onboarding.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "mobile-device-matrix",
    "slug": "mobile-device-matrix",
    "category": "mobile",
    "title": "Mobile Device Matrix",
    "intent": "Cover small screen, large screen, iOS, and Android key paths.",
    "verify": "npx playwright test --project=mobile",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Mobile Device Matrix for a mobile or responsive application: Cover small screen, large screen, iOS, and Android key paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Cover small screen, large screen, iOS, and Android key paths.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-quickstart",
    "slug": "docs-quickstart",
    "category": "docs",
    "title": "Quickstart",
    "intent": "Write the shortest fresh-clone path that runs successfully in five minutes.",
    "verify": "markdownlint README.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Quickstart for a developer-facing documentation site or repository: Write the shortest fresh-clone path that runs successfully in five minutes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint README.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write the shortest fresh-clone path that runs successfully in five minutes.\n- The verification command or evidence path succeeds: `markdownlint README.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint README.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-install-troubleshooting",
    "slug": "docs-install-troubleshooting",
    "category": "docs",
    "title": "Install Troubleshooting",
    "intent": "Document common install failures, causes, and fixes.",
    "verify": "markdownlint docs",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Install Troubleshooting for a developer-facing documentation site or repository: Document common install failures, causes, and fixes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Document common install failures, causes, and fixes.\n- The verification command or evidence path succeeds: `markdownlint docs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-api-examples",
    "slug": "docs-api-examples",
    "category": "docs",
    "title": "API Examples",
    "intent": "Add minimal request, response, and error examples for core APIs.",
    "verify": "pytest -k docs_api_examples",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Examples for a developer-facing documentation site or repository: Add minimal request, response, and error examples for core APIs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `pytest -k docs_api_examples`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add minimal request, response, and error examples for core APIs.\n- The verification command or evidence path succeeds: `pytest -k docs_api_examples`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k docs_api_examples` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-architecture-overview",
    "slug": "docs-architecture-overview",
    "category": "docs",
    "title": "Architecture Overview",
    "intent": "Explain module boundaries, data flow, and explicit non-goals.",
    "verify": "markdownlint docs/architecture.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Architecture Overview for a developer-facing documentation site or repository: Explain module boundaries, data flow, and explicit non-goals.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/architecture.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Explain module boundaries, data flow, and explicit non-goals.\n- The verification command or evidence path succeeds: `markdownlint docs/architecture.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/architecture.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-contribution-guide",
    "slug": "docs-contribution-guide",
    "category": "docs",
    "title": "Contribution Guide",
    "intent": "Document development, testing, commit, and PR review rules.",
    "verify": "markdownlint CONTRIBUTING.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Contribution Guide for a developer-facing documentation site or repository: Document development, testing, commit, and PR review rules.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint CONTRIBUTING.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Document development, testing, commit, and PR review rules.\n- The verification command or evidence path succeeds: `markdownlint CONTRIBUTING.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint CONTRIBUTING.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-release-notes",
    "slug": "docs-release-notes",
    "category": "docs",
    "title": "Release Notes",
    "intent": "Create user-facing change, migration, and breaking-change notes.",
    "verify": "markdownlint CHANGELOG.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Release Notes for a developer-facing documentation site or repository: Create user-facing change, migration, and breaking-change notes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint CHANGELOG.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create user-facing change, migration, and breaking-change notes.\n- The verification command or evidence path succeeds: `markdownlint CHANGELOG.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint CHANGELOG.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-env-vars",
    "slug": "docs-env-vars",
    "category": "docs",
    "title": "Environment Variables",
    "intent": "List env names, defaults, requiredness, and safety notes.",
    "verify": "pytest -k env_config",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Environment Variables for a developer-facing documentation site or repository: List env names, defaults, requiredness, and safety notes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `pytest -k env_config`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: List env names, defaults, requiredness, and safety notes.\n- The verification command or evidence path succeeds: `pytest -k env_config`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k env_config` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-runbook",
    "slug": "docs-runbook",
    "category": "docs",
    "title": "Operator Runbook",
    "intent": "Document alerts, recovery, rollback, and data repair steps.",
    "verify": "markdownlint docs/runbooks",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Operator Runbook for a developer-facing documentation site or repository: Document alerts, recovery, rollback, and data repair steps.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/runbooks`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Document alerts, recovery, rollback, and data repair steps.\n- The verification command or evidence path succeeds: `markdownlint docs/runbooks`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/runbooks` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-decision-records",
    "slug": "docs-decision-records",
    "category": "docs",
    "title": "Architecture Decision Records",
    "intent": "Add ADR templates and indexes for major technical decisions.",
    "verify": "markdownlint docs/adr",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Architecture Decision Records for a developer-facing documentation site or repository: Add ADR templates and indexes for major technical decisions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/adr`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add ADR templates and indexes for major technical decisions.\n- The verification command or evidence path succeeds: `markdownlint docs/adr`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/adr` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-glossary",
    "slug": "docs-glossary",
    "category": "docs",
    "title": "Glossary",
    "intent": "Unify product, engineering, and data-field terms.",
    "verify": "markdownlint docs/glossary.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Glossary for a developer-facing documentation site or repository: Unify product, engineering, and data-field terms.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/glossary.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Unify product, engineering, and data-field terms.\n- The verification command or evidence path succeeds: `markdownlint docs/glossary.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/glossary.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-screenshot-docs",
    "slug": "docs-screenshot-docs",
    "category": "docs",
    "title": "Screenshot Docs",
    "intent": "Add real screenshots and labels for UI workflows.",
    "verify": "markdownlint docs",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Screenshot Docs for a developer-facing documentation site or repository: Add real screenshots and labels for UI workflows.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint docs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add real screenshots and labels for UI workflows.\n- The verification command or evidence path succeeds: `markdownlint docs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "docs-docs-lint",
    "slug": "docs-docs-lint",
    "category": "docs",
    "title": "Docs Lint Gate",
    "intent": "Add link, spelling, and executable code block checks.",
    "verify": "markdownlint . && lychee .",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Docs Lint Gate for a developer-facing documentation site or repository: Add link, spelling, and executable code block checks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `markdownlint . && lychee .`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add link, spelling, and executable code block checks.\n- The verification command or evidence path succeeds: `markdownlint . && lychee .`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint . && lychee .` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-user-journeys",
    "slug": "product-user-journeys",
    "category": "product",
    "title": "User Journeys",
    "intent": "Map persona tasks into pages, events, and success states.",
    "verify": "markdownlint docs/product",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete User Journeys for a product planning and implementation repo: Map persona tasks into pages, events, and success states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/product`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Map persona tasks into pages, events, and success states.\n- The verification command or evidence path succeeds: `markdownlint docs/product`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/product` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-prd-skeleton",
    "slug": "product-prd-skeleton",
    "category": "product",
    "title": "PRD Skeleton",
    "intent": "Write goals, non-goals, constraints, and acceptance criteria.",
    "verify": "markdownlint docs/prd.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete PRD Skeleton for a product planning and implementation repo: Write goals, non-goals, constraints, and acceptance criteria.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/prd.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write goals, non-goals, constraints, and acceptance criteria.\n- The verification command or evidence path succeeds: `markdownlint docs/prd.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/prd.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-onboarding-metrics",
    "slug": "product-onboarding-metrics",
    "category": "product",
    "title": "Onboarding Metrics",
    "intent": "Define activation events, dropoff points, and dashboard queries.",
    "verify": "pytest -k analytics_events",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Onboarding Metrics for a product planning and implementation repo: Define activation events, dropoff points, and dashboard queries.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `pytest -k analytics_events`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define activation events, dropoff points, and dashboard queries.\n- The verification command or evidence path succeeds: `pytest -k analytics_events`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k analytics_events` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-feature-prioritization",
    "slug": "product-feature-prioritization",
    "category": "product",
    "title": "Feature Prioritization",
    "intent": "Split MVP and later work by impact, cost, and risk.",
    "verify": "markdownlint docs/roadmap.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Feature Prioritization for a product planning and implementation repo: Split MVP and later work by impact, cost, and risk.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/roadmap.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Split MVP and later work by impact, cost, and risk.\n- The verification command or evidence path succeeds: `markdownlint docs/roadmap.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/roadmap.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-permission-model",
    "slug": "product-permission-model",
    "category": "product",
    "title": "Permission Model",
    "intent": "Map roles, resources, actions, and UI visibility.",
    "verify": "pytest -k permissions",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Permission Model for a product planning and implementation repo: Map roles, resources, actions, and UI visibility.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `pytest -k permissions`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Map roles, resources, actions, and UI visibility.\n- The verification command or evidence path succeeds: `pytest -k permissions`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k permissions` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-notification-strategy",
    "slug": "product-notification-strategy",
    "category": "product",
    "title": "Notification Strategy",
    "intent": "Define triggers, channels, frequency, and unsubscribe behavior.",
    "verify": "pytest -k notifications",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Notification Strategy for a product planning and implementation repo: Define triggers, channels, frequency, and unsubscribe behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `pytest -k notifications`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define triggers, channels, frequency, and unsubscribe behavior.\n- The verification command or evidence path succeeds: `pytest -k notifications`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k notifications` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-empty-data-policy",
    "slug": "product-empty-data-policy",
    "category": "product",
    "title": "Empty Data Policy",
    "intent": "Choose blank, sample data, import, or CTA by user state.",
    "verify": "npx playwright test empty-data.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Empty Data Policy for a product planning and implementation repo: Choose blank, sample data, import, or CTA by user state.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `npx playwright test empty-data.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Choose blank, sample data, import, or CTA by user state.\n- The verification command or evidence path succeeds: `npx playwright test empty-data.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test empty-data.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-upgrade-path",
    "slug": "product-upgrade-path",
    "category": "product",
    "title": "Upgrade Path",
    "intent": "Design limits, paywalls, trials, and upgrade conversion paths.",
    "verify": "pytest -k entitlement",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Upgrade Path for a product planning and implementation repo: Design limits, paywalls, trials, and upgrade conversion paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `pytest -k entitlement`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Design limits, paywalls, trials, and upgrade conversion paths.\n- The verification command or evidence path succeeds: `pytest -k entitlement`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k entitlement` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-feedback-loop",
    "slug": "product-feedback-loop",
    "category": "product",
    "title": "Feedback Loop",
    "intent": "Collect, classify, track, and close user feedback.",
    "verify": "markdownlint docs/feedback.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Feedback Loop for a product planning and implementation repo: Collect, classify, track, and close user feedback.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/feedback.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Collect, classify, track, and close user feedback.\n- The verification command or evidence path succeeds: `markdownlint docs/feedback.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/feedback.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-search-relevance",
    "slug": "product-search-relevance",
    "category": "product",
    "title": "Search Relevance",
    "intent": "Define query handling, ranking, typo tolerance, and no-result behavior.",
    "verify": "pytest -k search_relevance",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Search Relevance for a product planning and implementation repo: Define query handling, ranking, typo tolerance, and no-result behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `pytest -k search_relevance`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define query handling, ranking, typo tolerance, and no-result behavior.\n- The verification command or evidence path succeeds: `pytest -k search_relevance`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k search_relevance` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-admin-workflows",
    "slug": "product-admin-workflows",
    "category": "product",
    "title": "Admin Workflows",
    "intent": "Design review, undo, audit log, and bulk moderation flows.",
    "verify": "npx playwright test admin.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Admin Workflows for a product planning and implementation repo: Design review, undo, audit log, and bulk moderation flows.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `npx playwright test admin.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Design review, undo, audit log, and bulk moderation flows.\n- The verification command or evidence path succeeds: `npx playwright test admin.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test admin.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "product-success-criteria",
    "slug": "product-success-criteria",
    "category": "product",
    "title": "Success Criteria",
    "intent": "Define quantitative and qualitative completion measures for a feature.",
    "verify": "markdownlint docs/success.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Success Criteria for a product planning and implementation repo: Define quantitative and qualitative completion measures for a feature.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `markdownlint docs/success.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define quantitative and qualitative completion measures for a feature.\n- The verification command or evidence path succeeds: `markdownlint docs/success.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint docs/success.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-critical-paths",
    "slug": "qa-critical-paths",
    "category": "qa",
    "title": "Critical Path Tests",
    "intent": "Cover signup, create, edit, delete, export, and recovery flows.",
    "verify": "npx playwright test critical-paths.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Critical Path Tests for a product with automated and manual QA coverage: Cover signup, create, edit, delete, export, and recovery flows.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npx playwright test critical-paths.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Cover signup, create, edit, delete, export, and recovery flows.\n- The verification command or evidence path succeeds: `npx playwright test critical-paths.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test critical-paths.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-regression-matrix",
    "slug": "qa-regression-matrix",
    "category": "qa",
    "title": "Regression Matrix",
    "intent": "Build feature/browser/role/data-state regression coverage.",
    "verify": "npx playwright test",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Regression Matrix for a product with automated and manual QA coverage: Build feature/browser/role/data-state regression coverage.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npx playwright test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build feature/browser/role/data-state regression coverage.\n- The verification command or evidence path succeeds: `npx playwright test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-fixture-strategy",
    "slug": "qa-fixture-strategy",
    "category": "qa",
    "title": "Fixture Strategy",
    "intent": "Create deterministic seed, mock, factory, and cleanup patterns.",
    "verify": "pytest -k fixtures",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Fixture Strategy for a product with automated and manual QA coverage: Create deterministic seed, mock, factory, and cleanup patterns.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `pytest -k fixtures`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create deterministic seed, mock, factory, and cleanup patterns.\n- The verification command or evidence path succeeds: `pytest -k fixtures`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k fixtures` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-visual-regression",
    "slug": "qa-visual-regression",
    "category": "qa",
    "title": "Visual Regression",
    "intent": "Add screenshot diffs for critical pages with controlled thresholds.",
    "verify": "npx playwright test visual.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Visual Regression for a product with automated and manual QA coverage: Add screenshot diffs for critical pages with controlled thresholds.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npx playwright test visual.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add screenshot diffs for critical pages with controlled thresholds.\n- The verification command or evidence path succeeds: `npx playwright test visual.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test visual.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-api-contracts",
    "slug": "qa-api-contracts",
    "category": "qa",
    "title": "API Contracts",
    "intent": "Validate frontend/backend schema, error codes, and boundary values.",
    "verify": "pytest -k contract",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Contracts for a product with automated and manual QA coverage: Validate frontend/backend schema, error codes, and boundary values.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `pytest -k contract`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Validate frontend/backend schema, error codes, and boundary values.\n- The verification command or evidence path succeeds: `pytest -k contract`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k contract` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-flaky-test-audit",
    "slug": "qa-flaky-test-audit",
    "category": "qa",
    "title": "Flaky Test Audit",
    "intent": "Find unstable tests and fix waits, isolation, or fixtures.",
    "verify": "pytest --count=20",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Flaky Test Audit for a product with automated and manual QA coverage: Find unstable tests and fix waits, isolation, or fixtures.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `pytest --count=20`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find unstable tests and fix waits, isolation, or fixtures.\n- The verification command or evidence path succeeds: `pytest --count=20`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest --count=20` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-error-injection",
    "slug": "qa-error-injection",
    "category": "qa",
    "title": "Error Injection",
    "intent": "Simulate 500s, timeouts, network failure, and partial success.",
    "verify": "npx playwright test error-injection.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Error Injection for a product with automated and manual QA coverage: Simulate 500s, timeouts, network failure, and partial success.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npx playwright test error-injection.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Simulate 500s, timeouts, network failure, and partial success.\n- The verification command or evidence path succeeds: `npx playwright test error-injection.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test error-injection.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-cross-browser",
    "slug": "qa-cross-browser",
    "category": "qa",
    "title": "Cross-Browser Coverage",
    "intent": "Run critical flows across Chromium, Firefox, and WebKit.",
    "verify": "npx playwright test --project=chromium --project=firefox --project=webkit",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Cross-Browser Coverage for a product with automated and manual QA coverage: Run critical flows across Chromium, Firefox, and WebKit.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=chromium --project=firefox --project=webkit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run critical flows across Chromium, Firefox, and WebKit.\n- The verification command or evidence path succeeds: `npx playwright test --project=chromium --project=firefox --project=webkit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=chromium --project=firefox --project=webkit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-release-smoke",
    "slug": "qa-release-smoke",
    "category": "qa",
    "title": "Release Smoke",
    "intent": "Define the smallest pre-release verification checklist.",
    "verify": "npm run smoke",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Release Smoke for a product with automated and manual QA coverage: Define the smallest pre-release verification checklist.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `npm run smoke`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define the smallest pre-release verification checklist.\n- The verification command or evidence path succeeds: `npm run smoke`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run smoke` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-data-migration",
    "slug": "qa-data-migration",
    "category": "qa",
    "title": "Data Migration Test",
    "intent": "Verify counts, constraints, and rollback around data migration.",
    "verify": "pytest -k migration",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Data Migration Test for a product with automated and manual QA coverage: Verify counts, constraints, and rollback around data migration.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `pytest -k migration`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify counts, constraints, and rollback around data migration.\n- The verification command or evidence path succeeds: `pytest -k migration`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k migration` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-security-smoke",
    "slug": "qa-security-smoke",
    "category": "qa",
    "title": "Security Smoke",
    "intent": "Check auth, permission bypass, and sensitive info leakage.",
    "verify": "pytest -k security_smoke",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Security Smoke for a product with automated and manual QA coverage: Check auth, permission bypass, and sensitive info leakage.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `pytest -k security_smoke`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check auth, permission bypass, and sensitive info leakage.\n- The verification command or evidence path succeeds: `pytest -k security_smoke`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -k security_smoke` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "qa-bug-repro-template",
    "slug": "qa-bug-repro-template",
    "category": "qa",
    "title": "Bug Reproduction Template",
    "intent": "Standardize environment, steps, expected, actual, and evidence.",
    "verify": "markdownlint .github/ISSUE_TEMPLATE",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Bug Reproduction Template for a product with automated and manual QA coverage: Standardize environment, steps, expected, actual, and evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `markdownlint .github/ISSUE_TEMPLATE`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Standardize environment, steps, expected, actual, and evidence.\n- The verification command or evidence path succeeds: `markdownlint .github/ISSUE_TEMPLATE`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint .github/ISSUE_TEMPLATE` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-keyboard-nav",
    "slug": "accessibility-keyboard-nav",
    "category": "accessibility",
    "title": "Keyboard Navigation",
    "intent": "Ensure the whole app works with Tab, Enter, and Escape.",
    "verify": "npx playwright test keyboard.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Keyboard Navigation for a web or mobile interface: Ensure the whole app works with Tab, Enter, and Escape.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test keyboard.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ensure the whole app works with Tab, Enter, and Escape.\n- The verification command or evidence path succeeds: `npx playwright test keyboard.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test keyboard.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-screen-reader",
    "slug": "accessibility-screen-reader",
    "category": "accessibility",
    "title": "Screen Reader Semantics",
    "intent": "Check landmarks, labels, aria-live, and button names.",
    "verify": "npx axe http://localhost:3000",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Screen Reader Semantics for a web or mobile interface: Check landmarks, labels, aria-live, and button names.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check landmarks, labels, aria-live, and button names.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-focus-visible",
    "slug": "accessibility-focus-visible",
    "category": "accessibility",
    "title": "Focus Visible",
    "intent": "Give every interactive element a clear focus state.",
    "verify": "npx playwright test focus.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Focus Visible for a web or mobile interface: Give every interactive element a clear focus state.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test focus.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Give every interactive element a clear focus state.\n- The verification command or evidence path succeeds: `npx playwright test focus.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test focus.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-color-contrast",
    "slug": "accessibility-color-contrast",
    "category": "accessibility",
    "title": "Color Contrast",
    "intent": "Meet WCAG AA for text, icons, and state colors.",
    "verify": "npx axe http://localhost:3000",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Color Contrast for a web or mobile interface: Meet WCAG AA for text, icons, and state colors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Meet WCAG AA for text, icons, and state colors.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-form-errors",
    "slug": "accessibility-form-errors",
    "category": "accessibility",
    "title": "Accessible Form Errors",
    "intent": "Associate errors with fields so screen readers announce them.",
    "verify": "npx playwright test form-a11y.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Accessible Form Errors for a web or mobile interface: Associate errors with fields so screen readers announce them.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test form-a11y.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Associate errors with fields so screen readers announce them.\n- The verification command or evidence path succeeds: `npx playwright test form-a11y.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test form-a11y.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-modal-trap",
    "slug": "accessibility-modal-trap",
    "category": "accessibility",
    "title": "Modal Focus Trap",
    "intent": "Focus opens, cycles, closes, and returns correctly.",
    "verify": "npx playwright test modal-a11y.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Modal Focus Trap for a web or mobile interface: Focus opens, cycles, closes, and returns correctly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test modal-a11y.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Focus opens, cycles, closes, and returns correctly.\n- The verification command or evidence path succeeds: `npx playwright test modal-a11y.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test modal-a11y.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-reduced-motion",
    "slug": "accessibility-reduced-motion",
    "category": "accessibility",
    "title": "Reduced Motion",
    "intent": "Respect prefers-reduced-motion for all nonessential motion.",
    "verify": "npx playwright test reduced-motion.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Reduced Motion for a web or mobile interface: Respect prefers-reduced-motion for all nonessential motion.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test reduced-motion.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Respect prefers-reduced-motion for all nonessential motion.\n- The verification command or evidence path succeeds: `npx playwright test reduced-motion.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test reduced-motion.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-alt-text",
    "slug": "accessibility-alt-text",
    "category": "accessibility",
    "title": "Alt Text Audit",
    "intent": "Separate decorative, content, and product images.",
    "verify": "npx axe http://localhost:3000",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Alt Text Audit for a web or mobile interface: Separate decorative, content, and product images.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Separate decorative, content, and product images.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-heading-order",
    "slug": "accessibility-heading-order",
    "category": "accessibility",
    "title": "Heading Order",
    "intent": "Fix skipped headings and fake styled headings.",
    "verify": "npx axe http://localhost:3000",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Heading Order for a web or mobile interface: Fix skipped headings and fake styled headings.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix skipped headings and fake styled headings.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-live-region",
    "slug": "accessibility-live-region",
    "category": "accessibility",
    "title": "Live Region Feedback",
    "intent": "Announce toasts, async completion, and errors accessibly.",
    "verify": "npx playwright test live-region.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Live Region Feedback for a web or mobile interface: Announce toasts, async completion, and errors accessibly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test live-region.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Announce toasts, async completion, and errors accessibly.\n- The verification command or evidence path succeeds: `npx playwright test live-region.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test live-region.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-touch-a11y",
    "slug": "accessibility-touch-a11y",
    "category": "accessibility",
    "title": "Touch Accessibility",
    "intent": "Check tap targets, zoom, and orientation on mobile.",
    "verify": "npx playwright test --project=mobile a11y.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Touch Accessibility for a web or mobile interface: Check tap targets, zoom, and orientation on mobile.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx playwright test --project=mobile a11y.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check tap targets, zoom, and orientation on mobile.\n- The verification command or evidence path succeeds: `npx playwright test --project=mobile a11y.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test --project=mobile a11y.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "accessibility-audit-report",
    "slug": "accessibility-audit-report",
    "category": "accessibility",
    "title": "Accessibility Audit Report",
    "intent": "Produce prioritized issues, impact, fixes, and acceptance checks.",
    "verify": "npx axe http://localhost:3000 --save results.json",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Accessibility Audit Report for a web or mobile interface: Produce prioritized issues, impact, fixes, and acceptance checks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `npx axe http://localhost:3000 --save results.json`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Produce prioritized issues, impact, fixes, and acceptance checks.\n- The verification command or evidence path succeeds: `npx axe http://localhost:3000 --save results.json`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx axe http://localhost:3000 --save results.json` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-lcp",
    "slug": "performance-lcp",
    "category": "performance",
    "title": "LCP Optimization",
    "intent": "Find and optimize the largest contentful paint element.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete LCP Optimization for a web application with measurable performance goals: Find and optimize the largest contentful paint element.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find and optimize the largest contentful paint element.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-cls",
    "slug": "performance-cls",
    "category": "performance",
    "title": "CLS Fix",
    "intent": "Reserve space for images, ads, and dynamic content.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete CLS Fix for a web application with measurable performance goals: Reserve space for images, ads, and dynamic content.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reserve space for images, ads, and dynamic content.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-inp",
    "slug": "performance-inp",
    "category": "performance",
    "title": "INP Optimization",
    "intent": "Reduce long tasks and blocking interaction handlers.",
    "verify": "npm run trace",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete INP Optimization for a web application with measurable performance goals: Reduce long tasks and blocking interaction handlers.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run trace`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce long tasks and blocking interaction handlers.\n- The verification command or evidence path succeeds: `npm run trace`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run trace` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-bundle-budget",
    "slug": "performance-bundle-budget",
    "category": "performance",
    "title": "Bundle Budget",
    "intent": "Set route and dependency size budgets in CI.",
    "verify": "npm run analyze",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Bundle Budget for a web application with measurable performance goals: Set route and dependency size budgets in CI.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run analyze`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Set route and dependency size budgets in CI.\n- The verification command or evidence path succeeds: `npm run analyze`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run analyze` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-code-splitting",
    "slug": "performance-code-splitting",
    "category": "performance",
    "title": "Code Splitting",
    "intent": "Lazy-load low-frequency routes, charts, and editors.",
    "verify": "npm run analyze",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Code Splitting for a web application with measurable performance goals: Lazy-load low-frequency routes, charts, and editors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run analyze`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Lazy-load low-frequency routes, charts, and editors.\n- The verification command or evidence path succeeds: `npm run analyze`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run analyze` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-image-pipeline",
    "slug": "performance-image-pipeline",
    "category": "performance",
    "title": "Image Pipeline",
    "intent": "Use srcset, modern formats, lazy loading, and cache headers.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Image Pipeline for a web application with measurable performance goals: Use srcset, modern formats, lazy loading, and cache headers.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use srcset, modern formats, lazy loading, and cache headers.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-font-loading",
    "slug": "performance-font-loading",
    "category": "performance",
    "title": "Font Loading",
    "intent": "Optimize font-display, subsets, and preload hints.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Font Loading for a web application with measurable performance goals: Optimize font-display, subsets, and preload hints.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Optimize font-display, subsets, and preload hints.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-api-waterfall",
    "slug": "performance-api-waterfall",
    "category": "performance",
    "title": "API Waterfall",
    "intent": "Remove serial requests and prefetch critical data.",
    "verify": "npx playwright test performance.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete API Waterfall for a web application with measurable performance goals: Remove serial requests and prefetch critical data.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npx playwright test performance.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Remove serial requests and prefetch critical data.\n- The verification command or evidence path succeeds: `npx playwright test performance.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test performance.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-cache-strategy",
    "slug": "performance-cache-strategy",
    "category": "performance",
    "title": "Cache Strategy",
    "intent": "Define browser, CDN, and service-worker cache boundaries.",
    "verify": "npx playwright test cache.spec.ts",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Cache Strategy for a web application with measurable performance goals: Define browser, CDN, and service-worker cache boundaries.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npx playwright test cache.spec.ts`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Define browser, CDN, and service-worker cache boundaries.\n- The verification command or evidence path succeeds: `npx playwright test cache.spec.ts`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test cache.spec.ts` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-memory-leaks",
    "slug": "performance-memory-leaks",
    "category": "performance",
    "title": "Memory Leak Audit",
    "intent": "Check long sessions, lists, subscriptions, and charts for leaks.",
    "verify": "npm run test:memory",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Memory Leak Audit for a web application with measurable performance goals: Check long sessions, lists, subscriptions, and charts for leaks.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run test:memory`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check long sessions, lists, subscriptions, and charts for leaks.\n- The verification command or evidence path succeeds: `npm run test:memory`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run test:memory` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-render-count",
    "slug": "performance-render-count",
    "category": "performance",
    "title": "Render Count Audit",
    "intent": "Find unnecessary React renders and expensive selectors.",
    "verify": "npm run profile",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Render Count Audit for a web application with measurable performance goals: Find unnecessary React renders and expensive selectors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run profile`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find unnecessary React renders and expensive selectors.\n- The verification command or evidence path succeeds: `npm run profile`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run profile` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "performance-ci-gate",
    "slug": "performance-ci-gate",
    "category": "performance",
    "title": "Performance CI Gate",
    "intent": "Add Lighthouse or trace thresholds to CI.",
    "verify": "npm run lighthouse:ci",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Performance CI Gate for a web application with measurable performance goals: Add Lighthouse or trace thresholds to CI.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse:ci`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add Lighthouse or trace thresholds to CI.\n- The verification command or evidence path succeeds: `npm run lighthouse:ci`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse:ci` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "goal-meta-prompt-writer",
    "slug": "goal-meta-prompt-writer",
    "category": "workflow",
    "title": "Goal Prompt Writer",
    "intent": "Ask the agent to inspect a repo and write a precise goal prompt before execution.",
    "verify": "markdownlint generated-goal.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Goal Prompt Writer for a coding-agent workflow repository: Ask the agent to inspect a repo and write a precise goal prompt before execution.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `markdownlint generated-goal.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ask the agent to inspect a repo and write a precise goal prompt before execution.\n- The verification command or evidence path succeeds: `markdownlint generated-goal.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `markdownlint generated-goal.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "goal-continuation-audit",
    "slug": "goal-continuation-audit",
    "category": "workflow",
    "title": "Goal Continuation Audit",
    "intent": "Check that a long-running goal keeps its done_when and verification contract after compaction.",
    "verify": "rg -e \"DONE WHEN\" -e \"VERIFY\" -e \"STOP RULES\" progress-log.md",
    "difficulty": "intermediate",
    "origin": "seed",
    "source_url": null,
    "source_name": null,
    "source_type": null,
    "evidence": null,
    "evidence_summary": null,
    "prompt": "/goal\nGOAL:\nComplete Goal Continuation Audit for a coding-agent workflow repository: Check that a long-running goal keeps its done_when and verification contract after compaction.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `rg -e \"DONE WHEN\" -e \"VERIFY\" -e \"STOP RULES\" progress-log.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Check that a long-running goal keeps its done_when and verification contract after compaction.\n- The verification command or evidence path succeeds: `rg -e \"DONE WHEN\" -e \"VERIFY\" -e \"STOP RULES\" progress-log.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `rg -e \"DONE WHEN\" -e \"VERIFY\" -e \"STOP RULES\" progress-log.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN."
  },
  {
    "id": "codex-verifiable-end-state",
    "slug": "codex-verifiable-end-state",
    "category": "workflow",
    "title": "Verifiable End-State Contract",
    "intent": "Complete one goal only when a verifiable end state is met.",
    "verify": "manual status plus repo-local verification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/follow-goals",
    "source_name": "OpenAI Codex docs",
    "source_type": "official-goal",
    "evidence": "verifiable stopping condition",
    "evidence_summary": "verifiable stopping condition; source: OpenAI Codex docs; type: official-goal; verification: manual status plus repo-local verification",
    "prompt": "/goal\nGOAL:\nComplete Verifiable End-State Contract for a coding-agent workflow repository: Complete one goal only when a verifiable end state is met.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `manual status plus repo-local verification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Complete one goal only when a verifiable end state is met.\n- The verification command or evidence path succeeds: `manual status plus repo-local verification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `manual status plus repo-local verification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/codex-verifiable-end-state.html"
  },
  {
    "id": "codex-visual-migration-playwright",
    "slug": "codex-visual-migration-playwright",
    "category": "migration",
    "title": "Visual Migration With Playwright",
    "intent": "Migrate a project while preserving screen output and checking it with Playwright.",
    "verify": "npx playwright test",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/follow-goals",
    "source_name": "OpenAI Codex docs",
    "source_type": "official-goal",
    "evidence": "visual migration",
    "evidence_summary": "visual migration; source: OpenAI Codex docs; type: official-goal; verification: npx playwright test",
    "prompt": "/goal\nGOAL:\nComplete Visual Migration With Playwright for a migration project: Migrate a project while preserving screen output and checking it with Playwright.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `npx playwright test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Migrate a project while preserving screen output and checking it with Playwright.\n- The verification command or evidence path succeeds: `npx playwright test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/codex-visual-migration-playwright.html"
  },
  {
    "id": "codex-plan-milestone-prototype",
    "slug": "codex-plan-milestone-prototype",
    "category": "prototype",
    "title": "PLAN.md Milestone Prototype",
    "intent": "Implement a PLAN.md-driven prototype with tests at each milestone and browser verification.",
    "verify": "npx playwright test",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/follow-goals",
    "source_name": "OpenAI Codex docs",
    "source_type": "official-goal",
    "evidence": "PLAN.md",
    "evidence_summary": "PLAN.md; source: OpenAI Codex docs; type: official-goal; verification: npx playwright test",
    "prompt": "/goal\nGOAL:\nComplete PLAN.md Milestone Prototype for a prototype project: Implement a PLAN.md-driven prototype with tests at each milestone and browser verification.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PLAN.md, milestones, app code, tests, browser checks, and demo notes.\n- Establish a baseline by running or locating evidence for: `npx playwright test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Follow the stated PLAN.md or acceptance criteria instead of adding unrequested features.\n- Keep the prototype runnable and demonstrable at every completed milestone.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement a PLAN.md-driven prototype with tests at each milestone and browser verification.\n- The verification command or evidence path succeeds: `npx playwright test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npx playwright test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/codex-plan-milestone-prototype.html"
  },
  {
    "id": "codex-eval-prompt-optimization",
    "slug": "codex-eval-prompt-optimization",
    "category": "prompt-optimization",
    "title": "Eval-Driven Prompt Optimization",
    "intent": "Optimize prompts against an eval suite until the target score or pass rate is reached.",
    "verify": "python -m pytest evals",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/follow-goals",
    "source_name": "OpenAI Codex docs",
    "source_type": "official-goal",
    "evidence": "eval suite",
    "evidence_summary": "eval suite; source: OpenAI Codex docs; type: official-goal; verification: python -m pytest evals",
    "prompt": "/goal\nGOAL:\nComplete Eval-Driven Prompt Optimization for an eval-backed prompt project: Optimize prompts against an eval suite until the target score or pass rate is reached.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompt files, eval cases, scoring reports, regressions, and failure examples.\n- Establish a baseline by running or locating evidence for: `python -m pytest evals`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete, weaken, or cherry-pick eval cases to improve the score.\n- Report representative failures as well as the final score.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Optimize prompts against an eval suite until the target score or pass rate is reached.\n- The verification command or evidence path succeeds: `python -m pytest evals`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `python -m pytest evals` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/codex-eval-prompt-optimization.html"
  },
  {
    "id": "claude-auth-tests-lint",
    "slug": "claude-auth-tests-lint",
    "category": "testing",
    "title": "Auth Tests And Lint Clean",
    "intent": "Keep working until auth tests pass and the lint step is clean.",
    "verify": "npm test -- test/auth && npm run lint",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "test/auth pass",
    "evidence_summary": "test/auth pass; source: Claude Code docs; type: official-goal; verification: npm test -- test/auth && npm run lint",
    "prompt": "/goal\nGOAL:\nComplete Auth Tests And Lint Clean for a project with failing or missing verification gates: Keep working until auth tests pass and the lint step is clean.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm test -- test/auth && npm run lint`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Keep working until auth tests pass and the lint step is clean.\n- The verification command or evidence path succeeds: `npm test -- test/auth && npm run lint`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- test/auth && npm run lint` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-auth-tests-lint.html"
  },
  {
    "id": "claude-weekly-changelog",
    "slug": "claude-weekly-changelog",
    "category": "docs",
    "title": "Weekly Changelog Coverage",
    "intent": "Ensure CHANGELOG.md includes an entry for every PR merged this week.",
    "verify": "git log --since='7 days ago' --merges && rg '^-' CHANGELOG.md",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "CHANGELOG.md has an entry",
    "evidence_summary": "CHANGELOG.md has an entry; source: Claude Code docs; type: official-goal; verification: git log --since='7 days ago' --merges && rg '^-' CHANGELOG.md",
    "prompt": "/goal\nGOAL:\nComplete Weekly Changelog Coverage for a developer-facing documentation site or repository: Ensure CHANGELOG.md includes an entry for every PR merged this week.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `git log --since='7 days ago' --merges && rg '^-' CHANGELOG.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ensure CHANGELOG.md includes an entry for every PR merged this week.\n- The verification command or evidence path succeeds: `git log --since='7 days ago' --merges && rg '^-' CHANGELOG.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `git log --since='7 days ago' --merges && rg '^-' CHANGELOG.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-weekly-changelog.html"
  },
  {
    "id": "hermes-ruff-src-clean",
    "slug": "hermes-ruff-src-clean",
    "category": "testing",
    "title": "Ruff Clean Source Tree",
    "intent": "Fix every lint error in src and prove ruff passes.",
    "verify": "ruff check src/",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "ruff check",
    "evidence_summary": "ruff check; source: Hermes docs; type: official-goal; verification: ruff check src/",
    "prompt": "/goal\nGOAL:\nComplete Ruff Clean Source Tree for a project with failing or missing verification gates: Fix every lint error in src and prove ruff passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `ruff check src/`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix every lint error in src and prove ruff passes.\n- The verification command or evidence path succeeds: `ruff check src/`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `ruff check src/` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-ruff-src-clean.html"
  },
  {
    "id": "hermes-feature-port-ci-green",
    "slug": "hermes-feature-port-ci-green",
    "category": "migration",
    "title": "Feature Port With CI Green",
    "intent": "Port a feature from another repo, include tests, and get CI green.",
    "verify": "pytest && npm test",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "CI green",
    "evidence_summary": "CI green; source: Hermes docs; type: official-goal; verification: pytest && npm test",
    "prompt": "/goal\nGOAL:\nComplete Feature Port With CI Green for a migration project: Port a feature from another repo, include tests, and get CI green.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `pytest && npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Port a feature from another repo, include tests, and get CI green.\n- The verification command or evidence path succeeds: `pytest && npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest && npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-feature-port-ci-green.html"
  },
  {
    "id": "hermes-session-drift-report",
    "slug": "hermes-session-drift-report",
    "category": "investigation",
    "title": "Session Drift Report",
    "intent": "Investigate session ID drift during mid-run compression and write a report.",
    "verify": "test -f reports/session-drift.md",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "write up a report",
    "evidence_summary": "write up a report; source: Hermes docs; type: official-goal; verification: test -f reports/session-drift.md",
    "prompt": "/goal\nGOAL:\nComplete Session Drift Report for an investigation task: Investigate session ID drift during mid-run compression and write a report.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect logs, traces, reproduction notes, source paths, and the final report.\n- Establish a baseline by running or locating evidence for: `test -f reports/session-drift.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Separate observed evidence from hypotheses.\n- Do not patch production code until the root cause is reproduced or strongly evidenced.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Investigate session ID drift during mid-run compression and write a report.\n- The verification command or evidence path succeeds: `test -f reports/session-drift.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `test -f reports/session-drift.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-session-drift-report.html"
  },
  {
    "id": "hermes-exif-rename-cli",
    "slug": "hermes-exif-rename-cli",
    "category": "cli",
    "title": "EXIF Rename CLI",
    "intent": "Build a small CLI that renames photos by EXIF date and test it on a photos folder.",
    "verify": "pytest tests/cli && ./rename-exif photos/ --dry-run",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "photos/ folder",
    "evidence_summary": "photos/ folder; source: Hermes docs; type: official-goal; verification: pytest tests/cli && ./rename-exif photos/ --dry-run",
    "prompt": "/goal\nGOAL:\nComplete EXIF Rename CLI for a command-line tool: Build a small CLI that renames photos by EXIF date and test it on a photos folder.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect CLI entrypoints, argument parsing, filesystem behavior, dry-run mode, and fixtures.\n- Establish a baseline by running or locating evidence for: `pytest tests/cli && ./rename-exif photos/ --dry-run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not perform destructive filesystem operations without a dry-run or explicit confirmation.\n- Keep command output deterministic enough for tests.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build a small CLI that renames photos by EXIF date and test it on a photos folder.\n- The verification command or evidence path succeeds: `pytest tests/cli && ./rename-exif photos/ --dry-run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest tests/cli && ./rename-exif photos/ --dry-run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-exif-rename-cli.html"
  },
  {
    "id": "hermes-four-files-walkthrough",
    "slug": "hermes-four-files-walkthrough",
    "category": "workflow",
    "title": "Four Files Walkthrough",
    "intent": "Create four note files across turns and verify each contains its number.",
    "verify": "for i in 1 2 3 4; do test \"$(cat /tmp/note_$i.txt)\" = \"$i\"; done",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "Create four files",
    "evidence_summary": "Create four files; source: Hermes docs; type: official-goal; verification: for i in 1 2 3 4; do test \"$(cat /tmp/note_$i.txt)\" = \"$i\"; done",
    "prompt": "/goal\nGOAL:\nComplete Four Files Walkthrough for a coding-agent workflow repository: Create four note files across turns and verify each contains its number.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `for i in 1 2 3 4; do test \"$(cat /tmp/note_$i.txt)\" = \"$i\"; done`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create four note files across turns and verify each contains its number.\n- The verification command or evidence path succeeds: `for i in 1 2 3 4; do test \"$(cat /tmp/note_$i.txt)\" = \"$i\"; done`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `for i in 1 2 3 4; do test \"$(cat /tmp/note_$i.txt)\" = \"$i\"; done` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-four-files-walkthrough.html"
  },
  {
    "id": "explainx-typescript-eslint-coverage",
    "slug": "explainx-typescript-eslint-coverage",
    "category": "testing",
    "title": "TypeScript ESLint Coverage Gate",
    "intent": "Resolve TypeScript errors, pass tests, clear ESLint warnings, and keep coverage above a threshold.",
    "verify": "npm run typecheck && npm test && npm run lint && npm run coverage",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "TypeScript errors resolved",
    "evidence_summary": "TypeScript errors resolved; source: ExplainX blog; type: third-party-tutorial; verification: npm run typecheck && npm test && npm run lint && npm run coverage",
    "prompt": "/goal\nGOAL:\nComplete TypeScript ESLint Coverage Gate for a project with failing or missing verification gates: Resolve TypeScript errors, pass tests, clear ESLint warnings, and keep coverage above a threshold.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm run typecheck && npm test && npm run lint && npm run coverage`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Resolve TypeScript errors, pass tests, clear ESLint warnings, and keep coverage above a threshold.\n- The verification command or evidence path succeeds: `npm run typecheck && npm test && npm run lint && npm run coverage`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run typecheck && npm test && npm run lint && npm run coverage` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-typescript-eslint-coverage.html"
  },
  {
    "id": "explainx-auth-di-refactor",
    "slug": "explainx-auth-di-refactor",
    "category": "refactor",
    "title": "Auth Dependency Injection Refactor",
    "intent": "Refactor auth code to dependency injection while preserving tests, coverage, and public API.",
    "verify": "npm test -- auth && npm run coverage",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "auth.ts dependency injection",
    "evidence_summary": "auth.ts dependency injection; source: ExplainX blog; type: third-party-tutorial; verification: npm test -- auth && npm run coverage",
    "prompt": "/goal\nGOAL:\nComplete Auth Dependency Injection Refactor for a refactoring task: Refactor auth code to dependency injection while preserving tests, coverage, and public API.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect the target module, call sites, public API, tests, and compatibility notes.\n- Establish a baseline by running or locating evidence for: `npm test -- auth && npm run coverage`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change public APIs, data formats, or user-visible behavior unless the goal requires it.\n- Keep behavior characterization tests before large internal changes.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Refactor auth code to dependency injection while preserving tests, coverage, and public API.\n- The verification command or evidence path succeeds: `npm test -- auth && npm run coverage`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- auth && npm run coverage` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-auth-di-refactor.html"
  },
  {
    "id": "explainx-npm-audit-clean",
    "slug": "explainx-npm-audit-clean",
    "category": "security-ops",
    "title": "NPM Audit Clean Remediation",
    "intent": "Patch npm audit vulnerabilities without breaking tests or public APIs.",
    "verify": "npm audit && npm test",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "npm audit vulnerabilities patched",
    "evidence_summary": "npm audit vulnerabilities patched; source: ExplainX blog; type: third-party-tutorial; verification: npm audit && npm test",
    "prompt": "/goal\nGOAL:\nComplete NPM Audit Clean Remediation for a production operations environment: Patch npm audit vulnerabilities without breaking tests or public APIs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow permissions, cloud IAM, release artifacts, and audit evidence.\n- Establish a baseline by running or locating evidence for: `npm audit && npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not print, copy, rotate, or exfiltrate real secrets.\n- Do not widen production permissions without a documented least-privilege reason.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Patch npm audit vulnerabilities without breaking tests or public APIs.\n- The verification command or evidence path succeeds: `npm audit && npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm audit && npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-npm-audit-clean.html"
  },
  {
    "id": "explainx-lighthouse-core-web-vitals",
    "slug": "explainx-lighthouse-core-web-vitals",
    "category": "performance",
    "title": "Lighthouse And Core Web Vitals Gate",
    "intent": "Improve Lighthouse and Core Web Vitals to explicit thresholds without regressions.",
    "verify": "npm run lighthouse",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "Lighthouse performance score >95",
    "evidence_summary": "Lighthouse performance score >95; source: ExplainX blog; type: third-party-tutorial; verification: npm run lighthouse",
    "prompt": "/goal\nGOAL:\nComplete Lighthouse And Core Web Vitals Gate for a web application with measurable performance goals: Improve Lighthouse and Core Web Vitals to explicit thresholds without regressions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run lighthouse`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Improve Lighthouse and Core Web Vitals to explicit thresholds without regressions.\n- The verification command or evidence path succeeds: `npm run lighthouse`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run lighthouse` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-lighthouse-core-web-vitals.html"
  },
  {
    "id": "qiita-vue2-vue3-visual-unit",
    "slug": "qiita-vue2-vue3-visual-unit",
    "category": "migration",
    "title": "Vue 2 To Vue 3 Visual And Unit Gate",
    "intent": "Migrate listed Vue screens and stop only when visual and unit tests pass.",
    "verify": "pnpm test:visual && pnpm test:unit",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://qiita.com/y-morimatsu/items/a314e5bbfdc83616d3ae",
    "source_name": "Qiita article",
    "source_type": "third-party-tutorial",
    "evidence": "pnpm test:visual",
    "evidence_summary": "pnpm test:visual; source: Qiita article; type: third-party-tutorial; verification: pnpm test:visual && pnpm test:unit",
    "prompt": "/goal\nGOAL:\nComplete Vue 2 To Vue 3 Visual And Unit Gate for a migration project: Migrate listed Vue screens and stop only when visual and unit tests pass.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `pnpm test:visual && pnpm test:unit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Migrate listed Vue screens and stop only when visual and unit tests pass.\n- The verification command or evidence path succeeds: `pnpm test:visual && pnpm test:unit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pnpm test:visual && pnpm test:unit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-vue2-vue3-visual-unit.html"
  },
  {
    "id": "qiita-canvas-puzzle-plan",
    "slug": "qiita-canvas-puzzle-plan",
    "category": "prototype",
    "title": "Canvas Puzzle PLAN.md Prototype",
    "intent": "Implement PLAN.md milestones for a canvas puzzle prototype and prove e2e passes.",
    "verify": "pnpm e2e",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://qiita.com/y-morimatsu/items/a314e5bbfdc83616d3ae",
    "source_name": "Qiita article",
    "source_type": "third-party-tutorial",
    "evidence": "canvas puzzle",
    "evidence_summary": "canvas puzzle; source: Qiita article; type: third-party-tutorial; verification: pnpm e2e",
    "prompt": "/goal\nGOAL:\nComplete Canvas Puzzle PLAN.md Prototype for a prototype project: Implement PLAN.md milestones for a canvas puzzle prototype and prove e2e passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PLAN.md, milestones, app code, tests, browser checks, and demo notes.\n- Establish a baseline by running or locating evidence for: `pnpm e2e`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Follow the stated PLAN.md or acceptance criteria instead of adding unrequested features.\n- Keep the prototype runnable and demonstrable at every completed milestone.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement PLAN.md milestones for a canvas puzzle prototype and prove e2e passes.\n- The verification command or evidence path succeeds: `pnpm e2e`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pnpm e2e` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-canvas-puzzle-plan.html"
  },
  {
    "id": "qiita-router-eval-score",
    "slug": "qiita-router-eval-score",
    "category": "prompt-optimization",
    "title": "Router Prompt Eval Score",
    "intent": "Improve a router prompt against an eval directory until the result score reaches a target.",
    "verify": "python -m pytest evals/router",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://qiita.com/y-morimatsu/items/a314e5bbfdc83616d3ae",
    "source_name": "Qiita article",
    "source_type": "third-party-tutorial",
    "evidence": "router prompt",
    "evidence_summary": "router prompt; source: Qiita article; type: third-party-tutorial; verification: python -m pytest evals/router",
    "prompt": "/goal\nGOAL:\nComplete Router Prompt Eval Score for an eval-backed prompt project: Improve a router prompt against an eval directory until the result score reaches a target.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompt files, eval cases, scoring reports, regressions, and failure examples.\n- Establish a baseline by running or locating evidence for: `python -m pytest evals/router`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete, weaken, or cherry-pick eval cases to improve the score.\n- Report representative failures as well as the final score.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Improve a router prompt against an eval directory until the result score reaches a target.\n- The verification command or evidence path succeeds: `python -m pytest evals/router`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `python -m pytest evals/router` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-router-eval-score.html"
  },
  {
    "id": "openai-slash-finish-migration",
    "slug": "openai-slash-finish-migration",
    "category": "migration",
    "title": "Finish Migration Keep Tests Green",
    "intent": "Use `/goal` to complete a migration while keeping the relevant tests green.",
    "verify": "repo-local migration tests",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/cli/slash-commands#set-an-experimental-goal-with-goal",
    "source_name": "OpenAI Codex slash commands",
    "source_type": "official-goal",
    "evidence": "Finish the migration",
    "evidence_summary": "Finish the migration; source: OpenAI Codex slash commands; type: official-goal; verification: repo-local migration tests",
    "prompt": "/goal\nGOAL:\nComplete Finish Migration Keep Tests Green for a migration project: Use `/goal` to complete a migration while keeping the relevant tests green.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `repo-local migration tests`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use `/goal` to complete a migration while keeping the relevant tests green.\n- The verification command or evidence path succeeds: `repo-local migration tests`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `repo-local migration tests` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-slash-finish-migration.html"
  },
  {
    "id": "openai-long-horizon-design-tool",
    "slug": "openai-long-horizon-design-tool",
    "category": "greenfield-build",
    "title": "Build Design Tool From Scratch",
    "intent": "Run a long-horizon Codex task to build a design tool with milestone verification.",
    "verify": "tests, lint, and typecheck per milestone",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/blog/run-long-horizon-tasks-with-codex",
    "source_name": "OpenAI Codex blog",
    "source_type": "official-workflow",
    "evidence": "verification steps",
    "evidence_summary": "verification steps; source: OpenAI Codex blog; type: official-workflow; verification: tests, lint, and typecheck per milestone",
    "prompt": "/goal\nGOAL:\nComplete Build Design Tool From Scratch for a greenfield implementation task: Run a long-horizon Codex task to build a design tool with milestone verification.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect product requirements, milestones, tests, and verification notes.\n- Establish a baseline by running or locating evidence for: `tests, lint, and typecheck per milestone`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Keep implementation tied to the stated product requirements.\n- Do not ship a demo-only path without tests or runnable verification.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a long-horizon Codex task to build a design tool with milestone verification.\n- The verification command or evidence path succeeds: `tests, lint, and typecheck per milestone`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests, lint, and typecheck per milestone` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-long-horizon-design-tool.html"
  },
  {
    "id": "claude-module-api-migration",
    "slug": "claude-module-api-migration",
    "category": "migration",
    "title": "Module API Migration",
    "intent": "Migrate a module to a new API while keeping call sites compiling and tests passing.",
    "verify": "compile call sites && tests pass",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "new API",
    "evidence_summary": "new API; source: Claude Code docs; type: official-goal; verification: compile call sites && tests pass",
    "prompt": "/goal\nGOAL:\nComplete Module API Migration for a migration project: Migrate a module to a new API while keeping call sites compiling and tests passing.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `compile call sites && tests pass`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Migrate a module to a new API while keeping call sites compiling and tests passing.\n- The verification command or evidence path succeeds: `compile call sites && tests pass`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `compile call sites && tests pass` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-module-api-migration.html"
  },
  {
    "id": "claude-design-doc-acceptance",
    "slug": "claude-design-doc-acceptance",
    "category": "product",
    "title": "Design Doc Acceptance Complete",
    "intent": "Implement a design document until every acceptance criterion is satisfied.",
    "verify": "acceptance criteria review",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "acceptance criteria",
    "evidence_summary": "acceptance criteria; source: Claude Code docs; type: official-goal; verification: acceptance criteria review",
    "prompt": "/goal\nGOAL:\nComplete Design Doc Acceptance Complete for a product planning and implementation repo: Implement a design document until every acceptance criterion is satisfied.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `acceptance criteria review`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement a design document until every acceptance criterion is satisfied.\n- The verification command or evidence path succeeds: `acceptance criteria review`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `acceptance criteria review` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-design-doc-acceptance.html"
  },
  {
    "id": "claude-split-oversized-file",
    "slug": "claude-split-oversized-file",
    "category": "refactor",
    "title": "Split Oversized File",
    "intent": "Split an oversized source file into focused modules while preserving behavior.",
    "verify": "module size budget && tests pass",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "size budget",
    "evidence_summary": "size budget; source: Claude Code docs; type: official-goal; verification: module size budget && tests pass",
    "prompt": "/goal\nGOAL:\nComplete Split Oversized File for a refactoring task: Split an oversized source file into focused modules while preserving behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect the target module, call sites, public API, tests, and compatibility notes.\n- Establish a baseline by running or locating evidence for: `module size budget && tests pass`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change public APIs, data formats, or user-visible behavior unless the goal requires it.\n- Keep behavior characterization tests before large internal changes.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Split an oversized source file into focused modules while preserving behavior.\n- The verification command or evidence path succeeds: `module size budget && tests pass`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `module size budget && tests pass` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-split-oversized-file.html"
  },
  {
    "id": "claude-clear-labeled-issues",
    "slug": "claude-clear-labeled-issues",
    "category": "backlog",
    "title": "Clear Labeled Issue Backlog",
    "intent": "Work through a labeled issue queue until no matching issues remain.",
    "verify": "issue queue empty",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/goal",
    "source_name": "Claude Code docs",
    "source_type": "official-goal",
    "evidence": "queue is empty",
    "evidence_summary": "queue is empty; source: Claude Code docs; type: official-goal; verification: issue queue empty",
    "prompt": "/goal\nGOAL:\nComplete Clear Labeled Issue Backlog for a backlog execution task: Work through a labeled issue queue until no matching issues remain.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect roadmaps, backlog files, issue queues, acceptance criteria, and CI evidence.\n- Establish a baseline by running or locating evidence for: `issue queue empty`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not expand the backlog while executing it.\n- Keep each finished item tied to its original acceptance criteria.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Work through a labeled issue queue until no matching issues remain.\n- The verification command or evidence path succeeds: `issue queue empty`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `issue queue empty` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-clear-labeled-issues.html"
  },
  {
    "id": "hermes-cli-tests-pass",
    "slug": "hermes-cli-tests-pass",
    "category": "testing",
    "title": "Fix Hermes CLI Tests",
    "intent": "Fix failing Hermes CLI tests until the project test script passes.",
    "verify": "scripts/run_tests.sh",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://hermes-agent.nousresearch.com/docs/user-guide/features/goals",
    "source_name": "Hermes docs",
    "source_type": "official-goal",
    "evidence": "scripts/run_tests.sh passes",
    "evidence_summary": "scripts/run_tests.sh passes; source: Hermes docs; type: official-goal; verification: scripts/run_tests.sh",
    "prompt": "/goal\nGOAL:\nComplete Fix Hermes CLI Tests for a project with failing or missing verification gates: Fix failing Hermes CLI tests until the project test script passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `scripts/run_tests.sh`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix failing Hermes CLI tests until the project test script passes.\n- The verification command or evidence path succeeds: `scripts/run_tests.sh`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `scripts/run_tests.sh` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hermes-cli-tests-pass.html"
  },
  {
    "id": "cursor-usage-pattern-analysis",
    "slug": "cursor-usage-pattern-analysis",
    "category": "data-analytics",
    "title": "Analyze Product Usage Patterns",
    "intent": "Analyze product usage patterns between tab view and agent panels.",
    "verify": "analysis files and tests shown",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://cursor.com/en-US/product",
    "source_name": "Cursor product page",
    "source_type": "official-agent-task",
    "evidence": "Analyze Tab vs Agent Usage Patterns",
    "evidence_summary": "Analyze Tab vs Agent Usage Patterns; source: Cursor product page; type: official-agent-task; verification: analysis files and tests shown",
    "prompt": "/goal\nGOAL:\nComplete Analyze Product Usage Patterns for an analytics or BI project: Analyze product usage patterns between tab view and agent panels.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `analysis files and tests shown`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Analyze product usage patterns between tab view and agent panels.\n- The verification command or evidence path succeeds: `analysis files and tests shown`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `analysis files and tests shown` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/cursor-usage-pattern-analysis.html"
  },
  {
    "id": "cursor-chart-tooltip-freeze",
    "slug": "cursor-chart-tooltip-freeze",
    "category": "frontend",
    "title": "Fix Freezing Chart Tooltips",
    "intent": "Debug and fix chart tooltips that freeze on hover.",
    "verify": "frontend diff plus interaction verification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://cursor.com/en-US/product",
    "source_name": "Cursor product page",
    "source_type": "official-agent-task",
    "evidence": "Chart tooltips freeze",
    "evidence_summary": "Chart tooltips freeze; source: Cursor product page; type: official-agent-task; verification: frontend diff plus interaction verification",
    "prompt": "/goal\nGOAL:\nComplete Fix Freezing Chart Tooltips for a web frontend application: Debug and fix chart tooltips that freeze on hover.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `frontend diff plus interaction verification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Debug and fix chart tooltips that freeze on hover.\n- The verification command or evidence path succeeds: `frontend diff plus interaction verification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `frontend diff plus interaction verification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/cursor-chart-tooltip-freeze.html"
  },
  {
    "id": "github-copilot-error-messages",
    "slug": "github-copilot-error-messages",
    "category": "frontend",
    "title": "Improve Common Error Messages",
    "intent": "Use a cloud coding agent to implement user-friendly messages for common errors.",
    "verify": "pushed code changes",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/how-tos/use-copilot-agents/cloud-agent/start-copilot-sessions",
    "source_name": "GitHub Copilot docs",
    "source_type": "official-agent-task",
    "evidence": "user friendly message",
    "evidence_summary": "user friendly message; source: GitHub Copilot docs; type: official-agent-task; verification: pushed code changes",
    "prompt": "/goal\nGOAL:\nComplete Improve Common Error Messages for a web frontend application: Use a cloud coding agent to implement user-friendly messages for common errors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `pushed code changes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a cloud coding agent to implement user-friendly messages for common errors.\n- The verification command or evidence path succeeds: `pushed code changes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pushed code changes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-error-messages.html"
  },
  {
    "id": "google-jules-auth-tests",
    "slug": "google-jules-auth-tests",
    "category": "testing",
    "title": "Add Authentication Tests",
    "intent": "Create unit tests for an authentication module in a Jules session.",
    "verify": "session completed with PR output",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://jules.google/docs/api/reference/sessions/",
    "source_name": "Google Jules sessions docs",
    "source_type": "official-agent-task",
    "evidence": "Add auth tests",
    "evidence_summary": "Add auth tests; source: Google Jules sessions docs; type: official-agent-task; verification: session completed with PR output",
    "prompt": "/goal\nGOAL:\nComplete Add Authentication Tests for a project with failing or missing verification gates: Create unit tests for an authentication module in a Jules session.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `session completed with PR output`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create unit tests for an authentication module in a Jules session.\n- The verification command or evidence path succeeds: `session completed with PR output`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `session completed with PR output` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/google-jules-auth-tests.html"
  },
  {
    "id": "openhands-userservice-tests",
    "slug": "openhands-userservice-tests",
    "category": "testing",
    "title": "Add UserService Unit Tests",
    "intent": "Add unit tests for UserService and raise target coverage to the documented threshold.",
    "verify": "coverage target evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorials",
    "source_type": "official-agent-task",
    "evidence": "Target coverage: 80%",
    "evidence_summary": "Target coverage: 80%; source: OpenHands tutorials; type: official-agent-task; verification: coverage target evidence",
    "prompt": "/goal\nGOAL:\nComplete Add UserService Unit Tests for a project with failing or missing verification gates: Add unit tests for UserService and raise target coverage to the documented threshold.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `coverage target evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add unit tests for UserService and raise target coverage to the documented threshold.\n- The verification command or evidence path succeeds: `coverage target evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `coverage target evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-userservice-tests.html"
  },
  {
    "id": "devin-parallel-coverage-recovery",
    "slug": "devin-parallel-coverage-recovery",
    "category": "testing",
    "title": "Parallel Test Coverage Recovery",
    "intent": "Find low-coverage modules and open separate test-improvement PRs for each module.",
    "verify": "separate PR per module",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.devin.ai/product-guides/advanced-mode",
    "source_name": "Devin advanced capabilities",
    "source_type": "official-agent-task",
    "evidence": "below 50% coverage",
    "evidence_summary": "below 50% coverage; source: Devin advanced capabilities; type: official-agent-task; verification: separate PR per module",
    "prompt": "/goal\nGOAL:\nComplete Parallel Test Coverage Recovery for a project with failing or missing verification gates: Find low-coverage modules and open separate test-improvement PRs for each module.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `separate PR per module`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find low-coverage modules and open separate test-improvement PRs for each module.\n- The verification command or evidence path succeeds: `separate PR per module`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `separate PR per module` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/devin-parallel-coverage-recovery.html"
  },
  {
    "id": "qiita-aochan-single-vitest-fix",
    "slug": "qiita-aochan-single-vitest-fix",
    "category": "testing",
    "title": "Single Vitest Case Fix",
    "intent": "Fix a quiz application until one named Vitest case passes.",
    "verify": "pnpm exec vitest run -t \"increments score only on correct answer\"",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://qiita.com/Aochan0604/items/8cc5f28901455097095c",
    "source_name": "Qiita Aochan0604",
    "source_type": "third-party-tutorial",
    "evidence": "pnpm exec vitest run -t",
    "evidence_summary": "pnpm exec vitest run -t; source: Qiita Aochan0604; type: third-party-tutorial; verification: pnpm exec vitest run -t \"increments score only on correct answer\"",
    "prompt": "/goal\nGOAL:\nComplete Single Vitest Case Fix for a project with failing or missing verification gates: Fix a quiz application until one named Vitest case passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `pnpm exec vitest run -t \"increments score only on correct answer\"`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix a quiz application until one named Vitest case passes.\n- The verification command or evidence path succeeds: `pnpm exec vitest run -t \"increments score only on correct answer\"`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pnpm exec vitest run -t \"increments score only on correct answer\"` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-aochan-single-vitest-fix.html"
  },
  {
    "id": "qiita-aochan-full-vitest-recovery",
    "slug": "qiita-aochan-full-vitest-recovery",
    "category": "testing",
    "title": "Full Quiz Test Recovery",
    "intent": "Repair the quiz app until the full Vitest suite exits cleanly.",
    "verify": "pnpm exec vitest run",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://qiita.com/Aochan0604/items/8cc5f28901455097095c",
    "source_name": "Qiita Aochan0604",
    "source_type": "third-party-tutorial",
    "evidence": "pnpm exec vitest run exits 0",
    "evidence_summary": "pnpm exec vitest run exits 0; source: Qiita Aochan0604; type: third-party-tutorial; verification: pnpm exec vitest run",
    "prompt": "/goal\nGOAL:\nComplete Full Quiz Test Recovery for a project with failing or missing verification gates: Repair the quiz app until the full Vitest suite exits cleanly.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `pnpm exec vitest run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Repair the quiz app until the full Vitest suite exits cleanly.\n- The verification command or evidence path succeeds: `pnpm exec vitest run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pnpm exec vitest run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-aochan-full-vitest-recovery.html"
  },
  {
    "id": "qiita-aochan-visual-feedback",
    "slug": "qiita-aochan-visual-feedback",
    "category": "frontend",
    "title": "Visual Feedback With Test Guard",
    "intent": "Add correct and wrong answer visual feedback while keeping tests green.",
    "verify": "pnpm exec vitest run && git status --short",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://qiita.com/Aochan0604/items/8cc5f28901455097095c",
    "source_name": "Qiita Aochan0604",
    "source_type": "third-party-tutorial",
    "evidence": ".correct and .wrong",
    "evidence_summary": ".correct and .wrong; source: Qiita Aochan0604; type: third-party-tutorial; verification: pnpm exec vitest run && git status --short",
    "prompt": "/goal\nGOAL:\nComplete Visual Feedback With Test Guard for a web frontend application: Add correct and wrong answer visual feedback while keeping tests green.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `pnpm exec vitest run && git status --short`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add correct and wrong answer visual feedback while keeping tests green.\n- The verification command or evidence path succeeds: `pnpm exec vitest run && git status --short`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pnpm exec vitest run && git status --short` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/qiita-aochan-visual-feedback.html"
  },
  {
    "id": "jdhodges-read-only-font-match",
    "slug": "jdhodges-read-only-font-match",
    "category": "research",
    "title": "Read-Only Font Match",
    "intent": "Research font matches in read-only mode and produce a report without purchasing or downloading assets.",
    "verify": "written report",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.jdhodges.com/blog/codex-goal-feature-review/",
    "source_name": "J.D. Hodges blog",
    "source_type": "third-party-review",
    "evidence": "read-only font-match",
    "evidence_summary": "read-only font-match; source: J.D. Hodges blog; type: third-party-review; verification: written report",
    "prompt": "/goal\nGOAL:\nComplete Read-Only Font Match for a research task: Research font matches in read-only mode and produce a report without purchasing or downloading assets.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `written report`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Research font matches in read-only mode and produce a report without purchasing or downloading assets.\n- The verification command or evidence path succeeds: `written report`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `written report` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/jdhodges-read-only-font-match.html"
  },
  {
    "id": "jdhodges-auth-coverage-lift",
    "slug": "jdhodges-auth-coverage-lift",
    "category": "testing",
    "title": "Auth Coverage Lift",
    "intent": "Raise authentication code coverage from the documented baseline to the documented target within a scoped edit boundary.",
    "verify": "npm test",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.jdhodges.com/blog/codex-goal-feature-review/",
    "source_name": "J.D. Hodges blog",
    "source_type": "third-party-review",
    "evidence": "coverage from 38% to 75%",
    "evidence_summary": "coverage from 38% to 75%; source: J.D. Hodges blog; type: third-party-review; verification: npm test",
    "prompt": "/goal\nGOAL:\nComplete Auth Coverage Lift for a project with failing or missing verification gates: Raise authentication code coverage from the documented baseline to the documented target within a scoped edit boundary.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Raise authentication code coverage from the documented baseline to the documented target within a scoped edit boundary.\n- The verification command or evidence path succeeds: `npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/jdhodges-auth-coverage-lift.html"
  },
  {
    "id": "apidog-auth-test-repair",
    "slug": "apidog-auth-test-repair",
    "category": "testing",
    "title": "Auth Test Repair Boundary",
    "intent": "Fix failing auth tests while preserving the documented file boundary.",
    "verify": "npm test",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://apidog.com/blog/goal-command-codex-claude-code-autonomous-agents/",
    "source_name": "Apidog blog",
    "source_type": "third-party-tutorial",
    "evidence": "npm test exits 0",
    "evidence_summary": "npm test exits 0; source: Apidog blog; type: third-party-tutorial; verification: npm test",
    "prompt": "/goal\nGOAL:\nComplete Auth Test Repair Boundary for a project with failing or missing verification gates: Fix failing auth tests while preserving the documented file boundary.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fix failing auth tests while preserving the documented file boundary.\n- The verification command or evidence path succeeds: `npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/apidog-auth-test-repair.html"
  },
  {
    "id": "apidog-benchmark-table",
    "slug": "apidog-benchmark-table",
    "category": "research",
    "title": "Public Benchmark Table",
    "intent": "Collect distinct public benchmarks and build a date-sorted comparison table.",
    "verify": "table covers 10 sources",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://apidog.com/blog/goal-command-codex-claude-code-autonomous-agents/",
    "source_name": "Apidog blog",
    "source_type": "third-party-tutorial",
    "evidence": "10 distinct benchmarks",
    "evidence_summary": "10 distinct benchmarks; source: Apidog blog; type: third-party-tutorial; verification: table covers 10 sources",
    "prompt": "/goal\nGOAL:\nComplete Public Benchmark Table for a research task: Collect distinct public benchmarks and build a date-sorted comparison table.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `table covers 10 sources`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Collect distinct public benchmarks and build a date-sorted comparison table.\n- The verification command or evidence path succeeds: `table covers 10 sources`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `table covers 10 sources` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/apidog-benchmark-table.html"
  },
  {
    "id": "apidog-repo-maintenance-audit",
    "slug": "apidog-repo-maintenance-audit",
    "category": "maintenance",
    "title": "Repo Maintenance Audit",
    "intent": "Find dead code, unused dependencies, and stale files, then produce a PR-ready justification list.",
    "verify": "each item has justification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://apidog.com/blog/goal-command-codex-claude-code-autonomous-agents/",
    "source_name": "Apidog blog",
    "source_type": "third-party-tutorial",
    "evidence": "dead code, unused dependencies",
    "evidence_summary": "dead code, unused dependencies; source: Apidog blog; type: third-party-tutorial; verification: each item has justification",
    "prompt": "/goal\nGOAL:\nComplete Repo Maintenance Audit for a repository maintenance task: Find dead code, unused dependencies, and stale files, then produce a PR-ready justification list.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect dead code, dependencies, file structure, scripts, and PR notes.\n- Establish a baseline by running or locating evidence for: `each item has justification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete files, dependencies, or scripts without evidence that they are unused.\n- Keep every proposed removal tied to a specific verification step.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find dead code, unused dependencies, and stale files, then produce a PR-ready justification list.\n- The verification command or evidence path succeeds: `each item has justification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `each item has justification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/apidog-repo-maintenance-audit.html"
  },
  {
    "id": "apidog-contributor-readme",
    "slug": "apidog-contributor-readme",
    "category": "docs",
    "title": "Contributor README Rewrite",
    "intent": "Rewrite README installation, run, test, and architecture guidance for new contributors.",
    "verify": "commands and expected output documented",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://apidog.com/blog/goal-command-codex-claude-code-autonomous-agents/",
    "source_name": "Apidog blog",
    "source_type": "third-party-tutorial",
    "evidence": "README.md install/run/test",
    "evidence_summary": "README.md install/run/test; source: Apidog blog; type: third-party-tutorial; verification: commands and expected output documented",
    "prompt": "/goal\nGOAL:\nComplete Contributor README Rewrite for a developer-facing documentation site or repository: Rewrite README installation, run, test, and architecture guidance for new contributors.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `commands and expected output documented`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Rewrite README installation, run, test, and architecture guidance for new contributors.\n- The verification command or evidence path succeeds: `commands and expected output documented`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `commands and expected output documented` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/apidog-contributor-readme.html"
  },
  {
    "id": "apidog-theme-toggle",
    "slug": "apidog-theme-toggle",
    "category": "frontend",
    "title": "Theme Toggle Persistence",
    "intent": "Add a dark and light theme toggle that persists across refreshes.",
    "verify": "browser refresh verification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://apidog.com/blog/goal-command-codex-claude-code-autonomous-agents/",
    "source_name": "Apidog blog",
    "source_type": "third-party-tutorial",
    "evidence": "dark/light theme toggle",
    "evidence_summary": "dark/light theme toggle; source: Apidog blog; type: third-party-tutorial; verification: browser refresh verification",
    "prompt": "/goal\nGOAL:\nComplete Theme Toggle Persistence for a web frontend application: Add a dark and light theme toggle that persists across refreshes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `browser refresh verification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add a dark and light theme toggle that persists across refreshes.\n- The verification command or evidence path succeeds: `browser refresh verification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `browser refresh verification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/apidog-theme-toggle.html"
  },
  {
    "id": "explainx-ci-pipeline-green",
    "slug": "explainx-ci-pipeline-green",
    "category": "devops-ci",
    "title": "CI Pipeline Green",
    "intent": "Repair CI test, lint, typecheck, and security scan failures until checks pass.",
    "verify": "local CI rerun and remote CI",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "All CI checks passing",
    "evidence_summary": "All CI checks passing; source: ExplainX blog; type: third-party-tutorial; verification: local CI rerun and remote CI",
    "prompt": "/goal\nGOAL:\nComplete CI Pipeline Green for a repository with CI/CD automation: Repair CI test, lint, typecheck, and security scan failures until checks pass.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `local CI rerun and remote CI`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Repair CI test, lint, typecheck, and security scan failures until checks pass.\n- The verification command or evidence path succeeds: `local CI rerun and remote CI`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `local CI rerun and remote CI` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-ci-pipeline-green.html"
  },
  {
    "id": "explainx-moment-dayjs-migration",
    "slug": "explainx-moment-dayjs-migration",
    "category": "migration",
    "title": "Moment To Day.js Migration",
    "intent": "Replace Moment.js with Day.js while preserving date output across edge cases.",
    "verify": "tests and edge-case output compare",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "Moment.js usage with Day.js",
    "evidence_summary": "Moment.js usage with Day.js; source: ExplainX blog; type: third-party-tutorial; verification: tests and edge-case output compare",
    "prompt": "/goal\nGOAL:\nComplete Moment To Day.js Migration for a migration project: Replace Moment.js with Day.js while preserving date output across edge cases.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `tests and edge-case output compare`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace Moment.js with Day.js while preserving date output across edge cases.\n- The verification command or evidence path succeeds: `tests and edge-case output compare`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests and edge-case output compare` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-moment-dayjs-migration.html"
  },
  {
    "id": "explainx-public-api-jsdoc",
    "slug": "explainx-public-api-jsdoc",
    "category": "docs",
    "title": "Public API Docs Coverage",
    "intent": "Add JSDoc and examples for public functions while keeping documentation links valid.",
    "verify": "docs coverage and broken link check",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://explainx.ai/blog/goal-mode-ai-agents-complete-guide-2026",
    "source_name": "ExplainX blog",
    "source_type": "third-party-tutorial",
    "evidence": "public functions ... JSDoc",
    "evidence_summary": "public functions ... JSDoc; source: ExplainX blog; type: third-party-tutorial; verification: docs coverage and broken link check",
    "prompt": "/goal\nGOAL:\nComplete Public API Docs Coverage for a developer-facing documentation site or repository: Add JSDoc and examples for public functions while keeping documentation links valid.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `docs coverage and broken link check`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add JSDoc and examples for public functions while keeping documentation links valid.\n- The verification command or evidence path succeeds: `docs coverage and broken link check`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `docs coverage and broken link check` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/explainx-public-api-jsdoc.html"
  },
  {
    "id": "udit-coverage-autoresearch",
    "slug": "udit-coverage-autoresearch",
    "category": "testing",
    "title": "Coverage Autoresearch Loop",
    "intent": "Iterate on tests until coverage reaches the documented target.",
    "verify": "npm test -- --coverage",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://udit.co/projects/autoresearch",
    "source_name": "Udit Autoresearch",
    "source_type": "third-party-project",
    "evidence": "Increase test coverage to 95%",
    "evidence_summary": "Increase test coverage to 95%; source: Udit Autoresearch; type: third-party-project; verification: npm test -- --coverage",
    "prompt": "/goal\nGOAL:\nComplete Coverage Autoresearch Loop for a project with failing or missing verification gates: Iterate on tests until coverage reaches the documented target.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm test -- --coverage`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Iterate on tests until coverage reaches the documented target.\n- The verification command or evidence path succeeds: `npm test -- --coverage`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test -- --coverage` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/udit-coverage-autoresearch.html"
  },
  {
    "id": "udit-bundle-size-reduction",
    "slug": "udit-bundle-size-reduction",
    "category": "performance",
    "title": "Bundle Size Reduction",
    "intent": "Iteratively reduce bundle size below the documented threshold.",
    "verify": "npm run build and size report",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://udit.co/projects/autoresearch",
    "source_name": "Udit Autoresearch",
    "source_type": "third-party-project",
    "evidence": "Reduce bundle size below 200KB",
    "evidence_summary": "Reduce bundle size below 200KB; source: Udit Autoresearch; type: third-party-project; verification: npm run build and size report",
    "prompt": "/goal\nGOAL:\nComplete Bundle Size Reduction for a web application with measurable performance goals: Iteratively reduce bundle size below the documented threshold.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run build and size report`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Iteratively reduce bundle size below the documented threshold.\n- The verification command or evidence path succeeds: `npm run build and size report`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run build and size report` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/udit-bundle-size-reduction.html"
  },
  {
    "id": "udit-benchmark-optimization",
    "slug": "udit-benchmark-optimization",
    "category": "performance",
    "title": "Benchmark Optimization",
    "intent": "Optimize performance against a benchmark command until the goal is reached.",
    "verify": "npm run bench",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://udit.co/projects/autoresearch",
    "source_name": "Udit Autoresearch",
    "source_type": "third-party-project",
    "evidence": "npm run bench",
    "evidence_summary": "npm run bench; source: Udit Autoresearch; type: third-party-project; verification: npm run bench",
    "prompt": "/goal\nGOAL:\nComplete Benchmark Optimization for a web application with measurable performance goals: Optimize performance against a benchmark command until the goal is reached.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `npm run bench`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Optimize performance against a benchmark command until the goal is reached.\n- The verification command or evidence path succeeds: `npm run bench`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm run bench` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/udit-benchmark-optimization.html"
  },
  {
    "id": "theaidaily-test-typescript-clean",
    "slug": "theaidaily-test-typescript-clean",
    "category": "testing",
    "title": "Test And TypeScript Clean",
    "intent": "Keep working until tests exit cleanly and TypeScript errors are gone.",
    "verify": "npm test && npx tsc --noEmit",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://theaidaily.nl/zo-gebruik-je-claude-code-goal-slash-command/",
    "source_name": "TheAIDaily",
    "source_type": "third-party-tutorial",
    "evidence": "npm test exit code 0",
    "evidence_summary": "npm test exit code 0; source: TheAIDaily; type: third-party-tutorial; verification: npm test && npx tsc --noEmit",
    "prompt": "/goal\nGOAL:\nComplete Test And TypeScript Clean for a project with failing or missing verification gates: Keep working until tests exit cleanly and TypeScript errors are gone.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `npm test && npx tsc --noEmit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Keep working until tests exit cleanly and TypeScript errors are gone.\n- The verification command or evidence path succeeds: `npm test && npx tsc --noEmit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test && npx tsc --noEmit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/theaidaily-test-typescript-clean.html"
  },
  {
    "id": "theaidaily-clean-worktree-budget",
    "slug": "theaidaily-clean-worktree-budget",
    "category": "maintenance",
    "title": "Clean Worktree File Budget",
    "intent": "Keep the worktree clean and enforce a source file size budget.",
    "verify": "git status --short && file length check",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://theaidaily.nl/zo-gebruik-je-claude-code-goal-slash-command/",
    "source_name": "TheAIDaily",
    "source_type": "third-party-tutorial",
    "evidence": "git status is clean",
    "evidence_summary": "git status is clean; source: TheAIDaily; type: third-party-tutorial; verification: git status --short && file length check",
    "prompt": "/goal\nGOAL:\nComplete Clean Worktree File Budget for a repository maintenance task: Keep the worktree clean and enforce a source file size budget.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect dead code, dependencies, file structure, scripts, and PR notes.\n- Establish a baseline by running or locating evidence for: `git status --short && file length check`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete files, dependencies, or scripts without evidence that they are unused.\n- Keep every proposed removal tied to a specific verification step.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Keep the worktree clean and enforce a source file size budget.\n- The verification command or evidence path succeeds: `git status --short && file length check`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `git status --short && file length check` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/theaidaily-clean-worktree-budget.html"
  },
  {
    "id": "cursor-forum-react19-migration",
    "slug": "cursor-forum-react19-migration",
    "category": "migration",
    "title": "React 19 Migration",
    "intent": "Migrate a project to React 19 and continue until the build passes.",
    "verify": "build passes",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://forum.cursor.com/t/add-autonomous-goal-mode-similar-to-claude-code-s-goal/160374",
    "source_name": "Cursor Forum",
    "source_type": "public-forum",
    "evidence": "React 19 until build passes",
    "evidence_summary": "React 19 until build passes; source: Cursor Forum; type: public-forum; verification: build passes",
    "prompt": "/goal\nGOAL:\nComplete React 19 Migration for a migration project: Migrate a project to React 19 and continue until the build passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `build passes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Migrate a project to React 19 and continue until the build passes.\n- The verification command or evidence path succeeds: `build passes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `build passes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/cursor-forum-react19-migration.html"
  },
  {
    "id": "cursor-forum-go-race-cleanup",
    "slug": "cursor-forum-go-race-cleanup",
    "category": "testing",
    "title": "Go Race Cleanup",
    "intent": "Eliminate data races detected by the Go race detector.",
    "verify": "go test -race",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://forum.cursor.com/t/add-autonomous-goal-mode-similar-to-claude-code-s-goal/160374",
    "source_name": "Cursor Forum",
    "source_type": "public-forum",
    "evidence": "go test -race",
    "evidence_summary": "go test -race; source: Cursor Forum; type: public-forum; verification: go test -race",
    "prompt": "/goal\nGOAL:\nComplete Go Race Cleanup for a project with failing or missing verification gates: Eliminate data races detected by the Go race detector.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `go test -race`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Eliminate data races detected by the Go race detector.\n- The verification command or evidence path succeeds: `go test -race`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `go test -race` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/cursor-forum-go-race-cleanup.html"
  },
  {
    "id": "x-meta-goal-prompt-generator",
    "slug": "x-meta-goal-prompt-generator",
    "category": "workflow",
    "title": "Meta Goal Prompt Generator",
    "intent": "Ask the agent to inspect the session, repo, history, and docs before writing the actual `/goal` prompt.",
    "verify": "generated goal prompt with clarified uncertainties",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/meta_alchemist/status/2054214497443995694",
    "source_name": "@meta_alchemist on X",
    "source_type": "x-post",
    "evidence": "write me the /goal prompt for this",
    "evidence_summary": "write me the /goal prompt for this; source: @meta_alchemist on X; type: x-post; verification: generated goal prompt with clarified uncertainties",
    "prompt": "/goal\nGOAL:\nComplete Meta Goal Prompt Generator for a coding-agent workflow repository: Ask the agent to inspect the session, repo, history, and docs before writing the actual `/goal` prompt.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `generated goal prompt with clarified uncertainties`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ask the agent to inspect the session, repo, history, and docs before writing the actual `/goal` prompt.\n- The verification command or evidence path succeeds: `generated goal prompt with clarified uncertainties`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `generated goal prompt with clarified uncertainties` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-meta-goal-prompt-generator.html"
  },
  {
    "id": "x-tests-lint-completion",
    "slug": "x-tests-lint-completion",
    "category": "testing",
    "title": "Tests And Lint Completion",
    "intent": "Run a `/goal` loop until all tests pass and lint is clean.",
    "verify": "tests pass && lint clean",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/sairahul1/status/2054821159066386482",
    "source_name": "@sairahul1 on X",
    "source_type": "x-post",
    "evidence": "/goal all tests pass and lint is clean",
    "evidence_summary": "/goal all tests pass and lint is clean; source: @sairahul1 on X; type: x-post; verification: tests pass && lint clean",
    "prompt": "/goal\nGOAL:\nComplete Tests And Lint Completion for a project with failing or missing verification gates: Run a `/goal` loop until all tests pass and lint is clean.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `tests pass && lint clean`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a `/goal` loop until all tests pass and lint is clean.\n- The verification command or evidence path succeeds: `tests pass && lint clean`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests pass && lint clean` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-tests-lint-completion.html"
  },
  {
    "id": "x-goal-escape-hatch",
    "slug": "x-goal-escape-hatch",
    "category": "goal-maintenance",
    "title": "Goal Escape Hatch",
    "intent": "Add an explicit incomplete state for impossible subtasks so a goal loop can stop safely.",
    "verify": "incomplete marker and rationale",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/KingBootoshi/status/2054837169748152645",
    "source_name": "@KingBootoshi on X",
    "source_type": "x-post",
    "evidence": "/GOAL NEEDED AN ESCAPE HATCH",
    "evidence_summary": "/GOAL NEEDED AN ESCAPE HATCH; source: @KingBootoshi on X; type: x-post; verification: incomplete marker and rationale",
    "prompt": "/goal\nGOAL:\nComplete Goal Escape Hatch for a goal-management workflow: Add an explicit incomplete state for impossible subtasks so a goal loop can stop safely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `incomplete marker and rationale`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add an explicit incomplete state for impossible subtasks so a goal loop can stop safely.\n- The verification command or evidence path succeeds: `incomplete marker and rationale`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `incomplete marker and rationale` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-goal-escape-hatch.html"
  },
  {
    "id": "x-agentsmd-goal-workflow",
    "slug": "x-agentsmd-goal-workflow",
    "category": "workflow",
    "title": "AGENTS.md Goal Workflow",
    "intent": "Use AGENTS.md rules together with `/goal` so long-running work keeps repo-specific constraints.",
    "verify": "AGENTS.md rules honored",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/dhruvbaldawa/status/2053745268118733252",
    "source_name": "@dhruvbaldawa on X",
    "source_type": "x-post",
    "evidence": "combine it with /goal",
    "evidence_summary": "combine it with /goal; source: @dhruvbaldawa on X; type: x-post; verification: AGENTS.md rules honored",
    "prompt": "/goal\nGOAL:\nComplete AGENTS.md Goal Workflow for a coding-agent workflow repository: Use AGENTS.md rules together with `/goal` so long-running work keeps repo-specific constraints.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `AGENTS.md rules honored`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use AGENTS.md rules together with `/goal` so long-running work keeps repo-specific constraints.\n- The verification command or evidence path succeeds: `AGENTS.md rules honored`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `AGENTS.md rules honored` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-agentsmd-goal-workflow.html"
  },
  {
    "id": "x-goal-forge-done-when",
    "slug": "x-goal-forge-done-when",
    "category": "goal-maintenance",
    "title": "Goal-Forge Done-When Loop",
    "intent": "Write a GOAL.md-style contract where `done_when` controls completion instead of vague success claims.",
    "verify": "done_when audit",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/Michaelzsguo/status/2053508788431511637",
    "source_name": "@Michaelzsguo on X",
    "source_type": "x-post",
    "evidence": "done_when is intrinsic",
    "evidence_summary": "done_when is intrinsic; source: @Michaelzsguo on X; type: x-post; verification: done_when audit",
    "prompt": "/goal\nGOAL:\nComplete Goal-Forge Done-When Loop for a goal-management workflow: Write a GOAL.md-style contract where `done_when` controls completion instead of vague success claims.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `done_when audit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write a GOAL.md-style contract where `done_when` controls completion instead of vague success claims.\n- The verification command or evidence path succeeds: `done_when audit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `done_when audit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-goal-forge-done-when.html"
  },
  {
    "id": "x-plan-then-goal-execution",
    "slug": "x-plan-then-goal-execution",
    "category": "workflow",
    "title": "Plan-Then-Goal Execution",
    "intent": "Use plan mode to define the work, then start a new goal session to implement the plan completely.",
    "verify": "plan completed against checklist",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/ivangdavila/status/2053867892064616481",
    "source_name": "@ivangdavila on X",
    "source_type": "x-post",
    "evidence": "Use /plan mode to define the goal",
    "evidence_summary": "Use /plan mode to define the goal; source: @ivangdavila on X; type: x-post; verification: plan completed against checklist",
    "prompt": "/goal\nGOAL:\nComplete Plan-Then-Goal Execution for a coding-agent workflow repository: Use plan mode to define the work, then start a new goal session to implement the plan completely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `plan completed against checklist`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use plan mode to define the work, then start a new goal session to implement the plan completely.\n- The verification command or evidence path succeeds: `plan completed against checklist`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `plan completed against checklist` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-plan-then-goal-execution.html"
  },
  {
    "id": "x-measurable-goal-structure",
    "slug": "x-measurable-goal-structure",
    "category": "workflow",
    "title": "Measurable Goal Structure",
    "intent": "Write goals with a clear target, proof requirement, and explicit limits.",
    "verify": "proof and limits present",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/Arslandev97/status/2054781760194711978",
    "source_name": "@Arslandev97 on X",
    "source_type": "x-post",
    "evidence": "Set a clear goal. Make it measurable.",
    "evidence_summary": "Set a clear goal. Make it measurable.; source: @Arslandev97 on X; type: x-post; verification: proof and limits present",
    "prompt": "/goal\nGOAL:\nComplete Measurable Goal Structure for a coding-agent workflow repository: Write goals with a clear target, proof requirement, and explicit limits.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `proof and limits present`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write goals with a clear target, proof requirement, and explicit limits.\n- The verification command or evidence path succeeds: `proof and limits present`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `proof and limits present` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-measurable-goal-structure.html"
  },
  {
    "id": "x-qa-engineer-simulation",
    "slug": "x-qa-engineer-simulation",
    "category": "qa",
    "title": "QA Engineer Simulation",
    "intent": "Use `/goal` as a quality loop until tests pass and lint is clean.",
    "verify": "tests pass && lint clean",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/LenaWithAI/status/2054845479502930372",
    "source_name": "@LenaWithAI on X",
    "source_type": "x-post",
    "evidence": "runs until tests pass and lint is clean",
    "evidence_summary": "runs until tests pass and lint is clean; source: @LenaWithAI on X; type: x-post; verification: tests pass && lint clean",
    "prompt": "/goal\nGOAL:\nComplete QA Engineer Simulation for a product with automated and manual QA coverage: Use `/goal` as a quality loop until tests pass and lint is clean.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `tests pass && lint clean`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use `/goal` as a quality loop until tests pass and lint is clean.\n- The verification command or evidence path succeeds: `tests pass && lint clean`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests pass && lint clean` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-qa-engineer-simulation.html"
  },
  {
    "id": "reddit-trading-backlog-clearance",
    "slug": "reddit-trading-backlog-clearance",
    "category": "backlog",
    "title": "Clear Trading App Backlog",
    "intent": "Generate a roadmap backlog for a trading app and then clear it with goals.",
    "verify": "backlog cleared",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.reddit.com/r/codex/comments/1t7b3x1/goal_in_the_codex_app_is_amazing/",
    "source_name": "Reddit r/codex",
    "source_type": "public-forum",
    "evidence": "210 task backlog",
    "evidence_summary": "210 task backlog; source: Reddit r/codex; type: public-forum; verification: backlog cleared",
    "prompt": "/goal\nGOAL:\nComplete Clear Trading App Backlog for a backlog execution task: Generate a roadmap backlog for a trading app and then clear it with goals.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect roadmaps, backlog files, issue queues, acceptance criteria, and CI evidence.\n- Establish a baseline by running or locating evidence for: `backlog cleared`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not expand the backlog while executing it.\n- Keep each finished item tied to its original acceptance criteria.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Generate a roadmap backlog for a trading app and then clear it with goals.\n- The verification command or evidence path succeeds: `backlog cleared`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `backlog cleared` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/reddit-trading-backlog-clearance.html"
  },
  {
    "id": "reddit-ship-backlog-features",
    "slug": "reddit-ship-backlog-features",
    "category": "backlog",
    "title": "Ship Backlog Features",
    "intent": "Implement the feature list from BACKLOG.md until CI is green.",
    "verify": "CI green",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.reddit.com/r/WebAfterAI/comments/1t6lgsb/openai_just_dropped_goal_in_codex_set_a_goal_and/",
    "source_name": "Reddit r/WebAfterAI",
    "source_type": "public-forum",
    "evidence": "/goal ship the 18 features",
    "evidence_summary": "/goal ship the 18 features; source: Reddit r/WebAfterAI; type: public-forum; verification: CI green",
    "prompt": "/goal\nGOAL:\nComplete Ship Backlog Features for a backlog execution task: Implement the feature list from BACKLOG.md until CI is green.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect roadmaps, backlog files, issue queues, acceptance criteria, and CI evidence.\n- Establish a baseline by running or locating evidence for: `CI green`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not expand the backlog while executing it.\n- Keep each finished item tied to its original acceptance criteria.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement the feature list from BACKLOG.md until CI is green.\n- The verification command or evidence path succeeds: `CI green`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `CI green` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/reddit-ship-backlog-features.html"
  },
  {
    "id": "reddit-tests-pass-pr-ready",
    "slug": "reddit-tests-pass-pr-ready",
    "category": "testing",
    "title": "Tests Pass And PR Ready",
    "intent": "Keep Claude Code working until tests pass and the PR is ready for review.",
    "verify": "tests pass",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.reddit.com/r/ClaudeCode/comments/1taty8a/claude_code_just_shipped_a_run_until_done_mode/",
    "source_name": "Reddit r/ClaudeCode",
    "source_type": "public-forum",
    "evidence": "all tests pass and the PR is ready",
    "evidence_summary": "all tests pass and the PR is ready; source: Reddit r/ClaudeCode; type: public-forum; verification: tests pass",
    "prompt": "/goal\nGOAL:\nComplete Tests Pass And PR Ready for a project with failing or missing verification gates: Keep Claude Code working until tests pass and the PR is ready for review.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `tests pass`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Keep Claude Code working until tests pass and the PR is ready for review.\n- The verification command or evidence path succeeds: `tests pass`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests pass` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/reddit-tests-pass-pr-ready.html"
  },
  {
    "id": "x-interview-driven-goal-prompt-generator",
    "slug": "x-interview-driven-goal-prompt-generator",
    "category": "workflow",
    "title": "Interview-Driven Goal Prompt Generator",
    "intent": "Use a meta prompt to interview the user with clarifying questions until 'done' can be expressed in specific, measurable, verifiable terms, then output a high-quality structured /goal prompt.",
    "verify": "generated goal contains clear, binary, verifiable DONE WHEN criteria after clarification interview",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/itsolelehmann/status/2054649363234992401",
    "source_name": "@itsolelehmann on X",
    "source_type": "x-post",
    "evidence": "Write me a /goal prompt. Ask me what I'm trying to do first, then keep asking follow-up questions until you can describe 'done' in specific, measurable terms.",
    "evidence_summary": "Write me a /goal prompt. Ask me what I'm trying to do first, then keep asking follow-up questions until you can describe 'done' in specific, measurable terms.; source: @itsolelehmann on X; type: x-post; verification: generated goal contains clear, binary, verifiable DONE WHEN criteria after clarification interview",
    "prompt": "/goal\nGOAL:\nComplete Interview-Driven Goal Prompt Generator for a coding-agent workflow repository: Use a meta prompt to interview the user with clarifying questions until 'done' can be expressed in specific, measurable, verifiable terms, then output a high-quality structured /goal prompt.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `generated goal contains clear, binary, verifiable DONE WHEN criteria after clarification interview`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a meta prompt to interview the user with clarifying questions until 'done' can be expressed in specific, measurable, verifiable terms, then output a high-quality structured /goal prompt.\n- The verification command or evidence path succeeds: `generated goal contains clear, binary, verifiable DONE WHEN criteria after clarification interview`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `generated goal contains clear, binary, verifiable DONE WHEN criteria after clarification interview` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-interview-driven-goal-prompt-generator.html"
  },
  {
    "id": "reddit-billing-empty-state",
    "slug": "reddit-billing-empty-state",
    "category": "investigation",
    "title": "Billing Empty State Root Cause",
    "intent": "Find why active subscriptions show an empty state without changing pricing or webhook code.",
    "verify": "npm test",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.reddit.com/r/ClaudeAI/comments/1taelgl/what_improved_my_claude_code_workflow_stop/",
    "source_name": "Reddit r/ClaudeAI",
    "source_type": "public-forum",
    "evidence": "billing page shows an empty state",
    "evidence_summary": "billing page shows an empty state; source: Reddit r/ClaudeAI; type: public-forum; verification: npm test",
    "prompt": "/goal\nGOAL:\nComplete Billing Empty State Root Cause for an investigation task: Find why active subscriptions show an empty state without changing pricing or webhook code.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect logs, traces, reproduction notes, source paths, and the final report.\n- Establish a baseline by running or locating evidence for: `npm test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Separate observed evidence from hypotheses.\n- Do not patch production code until the root cause is reproduced or strongly evidenced.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find why active subscriptions show an empty state without changing pricing or webhook code.\n- The verification command or evidence path succeeds: `npm test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `npm test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/reddit-billing-empty-state.html"
  },
  {
    "id": "reddit-rag-chat-flywheel",
    "slug": "reddit-rag-chat-flywheel",
    "category": "prompt-optimization",
    "title": "RAG Chat Flywheel",
    "intent": "Iterate on code, tests, and metrics to improve a document-chat RAG system.",
    "verify": "Playwright tests and metric review",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.reddit.com/r/ClaudeCode/comments/1pe5nnw/update_1_creating_a_claude_code_flywheel/",
    "source_name": "Reddit r/ClaudeCode",
    "source_type": "public-forum",
    "evidence": "continually improve my RAG based document chat",
    "evidence_summary": "continually improve my RAG based document chat; source: Reddit r/ClaudeCode; type: public-forum; verification: Playwright tests and metric review",
    "prompt": "/goal\nGOAL:\nComplete RAG Chat Flywheel for an eval-backed prompt project: Iterate on code, tests, and metrics to improve a document-chat RAG system.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompt files, eval cases, scoring reports, regressions, and failure examples.\n- Establish a baseline by running or locating evidence for: `Playwright tests and metric review`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete, weaken, or cherry-pick eval cases to improve the score.\n- Report representative failures as well as the final score.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Iterate on code, tests, and metrics to improve a document-chat RAG system.\n- The verification command or evidence path succeeds: `Playwright tests and metric review`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `Playwright tests and metric review` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/reddit-rag-chat-flywheel.html"
  },
  {
    "id": "hn-button-console-error-fix",
    "slug": "hn-button-console-error-fix",
    "category": "frontend",
    "title": "Button Console Error Fix",
    "intent": "Use browser automation to click a button, inspect console errors, fix the issue, and prove it.",
    "verify": "Playwright interaction",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://news.ycombinator.com/item?id=45642911",
    "source_name": "HN Playwright Skill",
    "source_type": "public-forum",
    "evidence": "console error when you click the button",
    "evidence_summary": "console error when you click the button; source: HN Playwright Skill; type: public-forum; verification: Playwright interaction",
    "prompt": "/goal\nGOAL:\nComplete Button Console Error Fix for a web frontend application: Use browser automation to click a button, inspect console errors, fix the issue, and prove it.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `Playwright interaction`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use browser automation to click a button, inspect console errors, fix the issue, and prove it.\n- The verification command or evidence path succeeds: `Playwright interaction`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `Playwright interaction` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hn-button-console-error-fix.html"
  },
  {
    "id": "hn-review-sentiment-json-agent",
    "slug": "hn-review-sentiment-json-agent",
    "category": "research",
    "title": "Review Sentiment JSON Agent",
    "intent": "Fetch reviews with browser automation, classify sentiment, and write structured JSON output.",
    "verify": "JSON files written",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://news.ycombinator.com/item?id=45840088",
    "source_name": "HN You Should Write An Agent",
    "source_type": "public-forum",
    "evidence": "fetch ten reviews",
    "evidence_summary": "fetch ten reviews; source: HN You Should Write An Agent; type: public-forum; verification: JSON files written",
    "prompt": "/goal\nGOAL:\nComplete Review Sentiment JSON Agent for a research task: Fetch reviews with browser automation, classify sentiment, and write structured JSON output.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `JSON files written`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Fetch reviews with browser automation, classify sentiment, and write structured JSON output.\n- The verification command or evidence path succeeds: `JSON files written`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `JSON files written` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hn-review-sentiment-json-agent.html"
  },
  {
    "id": "hn-dag-agent-dispatch",
    "slug": "hn-dag-agent-dispatch",
    "category": "orchestration",
    "title": "DAG Agent Dispatch",
    "intent": "Split a goal into a dependency graph and dispatch independent agents into isolated worktrees.",
    "verify": "PR output",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://news.ycombinator.com/item?id=47355676",
    "source_name": "HN Astro",
    "source_type": "public-forum",
    "evidence": "isolated git worktree and opens a PR",
    "evidence_summary": "isolated git worktree and opens a PR; source: HN Astro; type: public-forum; verification: PR output",
    "prompt": "/goal\nGOAL:\nComplete DAG Agent Dispatch for an agent orchestration task: Split a goal into a dependency graph and dispatch independent agents into isolated worktrees.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect plans, worktrees, subtask ownership, PRs, and coordination notes.\n- Establish a baseline by running or locating evidence for: `PR output`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Keep subtask ownership explicit and avoid overlapping write scopes.\n- Do not merge or deploy automatically unless the goal explicitly allows it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Split a goal into a dependency graph and dispatch independent agents into isolated worktrees.\n- The verification command or evidence path succeeds: `PR output`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `PR output` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/hn-dag-agent-dispatch.html"
  },
  {
    "id": "video-nextjs-chat-sidebar",
    "slug": "video-nextjs-chat-sidebar",
    "category": "frontend",
    "title": "Next.js Chat History Sidebar",
    "intent": "Replace a Next.js sidebar with chat history, then test, fix build issues, and push.",
    "verify": "tests and build",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://videohighlight.com/v/AJpK3YTTKZ4",
    "source_name": "VideoHighlight YouTube summary",
    "source_type": "video-summary",
    "evidence": "replace a sidebar with chat history",
    "evidence_summary": "replace a sidebar with chat history; source: VideoHighlight YouTube summary; type: video-summary; verification: tests and build",
    "prompt": "/goal\nGOAL:\nComplete Next.js Chat History Sidebar for a web frontend application: Replace a Next.js sidebar with chat history, then test, fix build issues, and push.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect routes, components, state, stories, tests, and screenshots.\n- Establish a baseline by running or locating evidence for: `tests and build`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change unrelated routes or rewrite the design system.\n- Preserve existing accessibility and keyboard behavior unless the goal explicitly improves it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Replace a Next.js sidebar with chat history, then test, fix build issues, and push.\n- The verification command or evidence path succeeds: `tests and build`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tests and build` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/video-nextjs-chat-sidebar.html"
  },
  {
    "id": "video-rift-salvage-game",
    "slug": "video-rift-salvage-game",
    "category": "prototype",
    "title": "Rift Salvage Game Goal",
    "intent": "Build a 2D combat game prototype with assets, combat, boss logic, and browser verification.",
    "verify": "browser verification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://pogovet.com/youtube/codex-just-became-the-best-long-running-agentic-harness",
    "source_name": "Pogovet YouTube summary",
    "source_type": "video-summary",
    "evidence": "2D combat game Rift Salvage",
    "evidence_summary": "2D combat game Rift Salvage; source: Pogovet YouTube summary; type: video-summary; verification: browser verification",
    "prompt": "/goal\nGOAL:\nComplete Rift Salvage Game Goal for a prototype project: Build a 2D combat game prototype with assets, combat, boss logic, and browser verification.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PLAN.md, milestones, app code, tests, browser checks, and demo notes.\n- Establish a baseline by running or locating evidence for: `browser verification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Follow the stated PLAN.md or acceptance criteria instead of adding unrequested features.\n- Keep the prototype runnable and demonstrable at every completed milestone.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build a 2D combat game prototype with assets, combat, boss logic, and browser verification.\n- The verification command or evidence path succeeds: `browser verification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `browser verification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/video-rift-salvage-game.html"
  },
  {
    "id": "github-claude-goal-flaky-auth",
    "slug": "github-claude-goal-flaky-auth",
    "category": "testing",
    "title": "Flaky Auth Tests Goal",
    "intent": "Use a Claude goal plugin example to find and fix flaky authentication tests.",
    "verify": "python3 -m pytest tests",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/jthack/claude-goal",
    "source_name": "jthack/claude-goal",
    "source_type": "tool-readme",
    "evidence": "find and fix the flaky auth tests",
    "evidence_summary": "find and fix the flaky auth tests; source: jthack/claude-goal; type: tool-readme; verification: python3 -m pytest tests",
    "prompt": "/goal\nGOAL:\nComplete Flaky Auth Tests Goal for a project with failing or missing verification gates: Use a Claude goal plugin example to find and fix flaky authentication tests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `python3 -m pytest tests`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a Claude goal plugin example to find and fix flaky authentication tests.\n- The verification command or evidence path succeeds: `python3 -m pytest tests`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `python3 -m pytest tests` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-claude-goal-flaky-auth.html"
  },
  {
    "id": "github-pydantic-v2-migration",
    "slug": "github-pydantic-v2-migration",
    "category": "migration",
    "title": "Pydantic V1 To V2 Migration",
    "intent": "Migrate a project from Pydantic v1 to v2 while preserving API behavior.",
    "verify": "pytest -q",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://github.com/davidondrej/jailbreak-autoresearch/blob/main/docs-slash-goal.md",
    "source_name": "jailbreak-autoresearch docs",
    "source_type": "tool-readme",
    "evidence": "Migrate this project from Pydantic v1 to v2",
    "evidence_summary": "Migrate this project from Pydantic v1 to v2; source: jailbreak-autoresearch docs; type: tool-readme; verification: pytest -q",
    "prompt": "/goal\nGOAL:\nComplete Pydantic V1 To V2 Migration for a migration project: Migrate a project from Pydantic v1 to v2 while preserving API behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `pytest -q`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Migrate a project from Pydantic v1 to v2 while preserving API behavior.\n- The verification command or evidence path succeeds: `pytest -q`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `pytest -q` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-pydantic-v2-migration.html"
  },
  {
    "id": "github-review-plan-no-gaps",
    "slug": "github-review-plan-no-gaps",
    "category": "goal-maintenance",
    "title": "Review Plan Until No Gaps",
    "intent": "Loop on implementation-plan review until a fresh review finds no remaining gaps.",
    "verify": "fresh plan review has no new gaps",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/issues/21176",
    "source_name": "openai/codex issue 21176",
    "source_type": "github-issue",
    "evidence": "review the plan ImplementationPlan.md",
    "evidence_summary": "review the plan ImplementationPlan.md; source: openai/codex issue 21176; type: github-issue; verification: fresh plan review has no new gaps",
    "prompt": "/goal\nGOAL:\nComplete Review Plan Until No Gaps for a goal-management workflow: Loop on implementation-plan review until a fresh review finds no remaining gaps.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `fresh plan review has no new gaps`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Loop on implementation-plan review until a fresh review finds no remaining gaps.\n- The verification command or evidence path succeeds: `fresh plan review has no new gaps`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `fresh plan review has no new gaps` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-review-plan-no-gaps.html"
  },
  {
    "id": "github-noninteractive-goal-creation",
    "slug": "github-noninteractive-goal-creation",
    "category": "workflow",
    "title": "Non-Interactive Goal Creation",
    "intent": "Create and confirm an active goal during non-interactive Codex execution before continuing.",
    "verify": "get_goal and thread_goals evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/discussions/21764",
    "source_name": "openai/codex discussion 21764",
    "source_type": "github-discussion",
    "evidence": "Build the Meta0 LifeOS ontology boundary artifact",
    "evidence_summary": "Build the Meta0 LifeOS ontology boundary artifact; source: openai/codex discussion 21764; type: github-discussion; verification: get_goal and thread_goals evidence",
    "prompt": "/goal\nGOAL:\nComplete Non-Interactive Goal Creation for a coding-agent workflow repository: Create and confirm an active goal during non-interactive Codex execution before continuing.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `get_goal and thread_goals evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create and confirm an active goal during non-interactive Codex execution before continuing.\n- The verification command or evidence path succeeds: `get_goal and thread_goals evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `get_goal and thread_goals evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-noninteractive-goal-creation.html"
  },
  {
    "id": "github-long-task-verification",
    "slug": "github-long-task-verification",
    "category": "goal-maintenance",
    "title": "Long Task Until Verification",
    "intent": "Continue a long-running task until final verification passes rather than stopping on partial progress.",
    "verify": "final verification",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/issues/22049",
    "source_name": "openai/codex issue 22049",
    "source_type": "github-issue",
    "evidence": "Complete a long-running task until final verification passes",
    "evidence_summary": "Complete a long-running task until final verification passes; source: openai/codex issue 22049; type: github-issue; verification: final verification",
    "prompt": "/goal\nGOAL:\nComplete Long Task Until Verification for a goal-management workflow: Continue a long-running task until final verification passes rather than stopping on partial progress.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `final verification`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Continue a long-running task until final verification passes rather than stopping on partial progress.\n- The verification command or evidence path succeeds: `final verification`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `final verification` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-long-task-verification.html"
  },
  {
    "id": "github-benchmark-coverage-goal",
    "slug": "github-benchmark-coverage-goal",
    "category": "testing",
    "title": "Improve Benchmark Coverage",
    "intent": "Use `/goal` to improve benchmark coverage and persist the command in history.",
    "verify": "cargo test -p codex-tui goal_slash_command -- --nocapture",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/pull/21860",
    "source_name": "openai/codex PR 21860",
    "source_type": "github-pr",
    "evidence": "/goal improve benchmark coverage",
    "evidence_summary": "/goal improve benchmark coverage; source: openai/codex PR 21860; type: github-pr; verification: cargo test -p codex-tui goal_slash_command -- --nocapture",
    "prompt": "/goal\nGOAL:\nComplete Improve Benchmark Coverage for a project with failing or missing verification gates: Use `/goal` to improve benchmark coverage and persist the command in history.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `cargo test -p codex-tui goal_slash_command -- --nocapture`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use `/goal` to improve benchmark coverage and persist the command in history.\n- The verification command or evidence path succeeds: `cargo test -p codex-tui goal_slash_command -- --nocapture`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `cargo test -p codex-tui goal_slash_command -- --nocapture` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-benchmark-coverage-goal.html"
  },
  {
    "id": "github-completion-audit-before-done",
    "slug": "github-completion-audit-before-done",
    "category": "goal-maintenance",
    "title": "Completion Audit Before Done",
    "intent": "Audit completion criteria before calling the goal complete.",
    "verify": "focused coverage and evals",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/pull/22045",
    "source_name": "openai/codex PR 22045",
    "source_type": "github-pr",
    "evidence": "completion audits before calling update_goal",
    "evidence_summary": "completion audits before calling update_goal; source: openai/codex PR 22045; type: github-pr; verification: focused coverage and evals",
    "prompt": "/goal\nGOAL:\nComplete Completion Audit Before Done for a goal-management workflow: Audit completion criteria before calling the goal complete.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `focused coverage and evals`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Audit completion criteria before calling the goal complete.\n- The verification command or evidence path succeeds: `focused coverage and evals`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `focused coverage and evals` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-completion-audit-before-done.html"
  },
  {
    "id": "github-goal-permission-context",
    "slug": "github-goal-permission-context",
    "category": "goal-maintenance",
    "title": "Goal Permission Context Sync",
    "intent": "Ensure goal continuation uses the current permission context after approval mode changes.",
    "verify": "cargo check focused crates",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/codex/issues/22090",
    "source_name": "openai/codex issue 22090",
    "source_type": "github-issue",
    "evidence": "uses stale permission context",
    "evidence_summary": "uses stale permission context; source: openai/codex issue 22090; type: github-issue; verification: cargo check focused crates",
    "prompt": "/goal\nGOAL:\nComplete Goal Permission Context Sync for a goal-management workflow: Ensure goal continuation uses the current permission context after approval mode changes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `cargo check focused crates`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Ensure goal continuation uses the current permission context after approval mode changes.\n- The verification command or evidence path succeeds: `cargo check focused crates`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `cargo check focused crates` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-goal-permission-context.html"
  },
  {
    "id": "github-goalbuddy-workspace",
    "slug": "github-goalbuddy-workspace",
    "category": "workflow",
    "title": "Prep A Goal Workspace",
    "intent": "Prepare a goal workspace with board, notes, receipts, and an exact `/goal` command.",
    "verify": "board, receipts, and verify files",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/tolibear/goalbuddy",
    "source_name": "tolibear/goalbuddy",
    "source_type": "tool-readme",
    "evidence": "prints the exact /goal command",
    "evidence_summary": "prints the exact /goal command; source: tolibear/goalbuddy; type: tool-readme; verification: board, receipts, and verify files",
    "prompt": "/goal\nGOAL:\nComplete Prep A Goal Workspace for a coding-agent workflow repository: Prepare a goal workspace with board, notes, receipts, and an exact `/goal` command.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `board, receipts, and verify files`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prepare a goal workspace with board, notes, receipts, and an exact `/goal` command.\n- The verification command or evidence path succeeds: `board, receipts, and verify files`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `board, receipts, and verify files` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-goalbuddy-workspace.html"
  },
  {
    "id": "github-claude-batch-bugs",
    "slug": "github-claude-batch-bugs",
    "category": "testing",
    "title": "Batch Fix Bugs",
    "intent": "Use a Claude Code goal to fix a numbered batch of bugs without looping on missing skills.",
    "verify": "no unsatisfied skill loop",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/anthropics/claude-code/issues/58348",
    "source_name": "anthropics/claude-code issue 58348",
    "source_type": "github-issue",
    "evidence": "/goal Fix bugs #1-#6",
    "evidence_summary": "/goal Fix bugs #1-#6; source: anthropics/claude-code issue 58348; type: github-issue; verification: no unsatisfied skill loop",
    "prompt": "/goal\nGOAL:\nComplete Batch Fix Bugs for a project with failing or missing verification gates: Use a Claude Code goal to fix a numbered batch of bugs without looping on missing skills.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `no unsatisfied skill loop`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a Claude Code goal to fix a numbered batch of bugs without looping on missing skills.\n- The verification command or evidence path succeeds: `no unsatisfied skill loop`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `no unsatisfied skill loop` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-claude-batch-bugs.html"
  },
  {
    "id": "github-claude-long-goal-template",
    "slug": "github-claude-long-goal-template",
    "category": "workflow",
    "title": "Long Goal With Constraints",
    "intent": "Use a longer goal template with repo path, constraints, plan pointer, and execution order.",
    "verify": "stop hook evaluates cleanly",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/anthropics/claude-code/issues/58192",
    "source_name": "anthropics/claude-code issue 58192",
    "source_type": "github-issue",
    "evidence": "Goal: <several lines of overarching aim>",
    "evidence_summary": "Goal: <several lines of overarching aim>; source: anthropics/claude-code issue 58192; type: github-issue; verification: stop hook evaluates cleanly",
    "prompt": "/goal\nGOAL:\nComplete Long Goal With Constraints for a coding-agent workflow repository: Use a longer goal template with repo path, constraints, plan pointer, and execution order.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `stop hook evaluates cleanly`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a longer goal template with repo path, constraints, plan pointer, and execution order.\n- The verification command or evidence path succeeds: `stop hook evaluates cleanly`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `stop hook evaluates cleanly` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-claude-long-goal-template.html"
  },
  {
    "id": "github-hermes-real-cli-loop",
    "slug": "github-hermes-real-cli-loop",
    "category": "goal-maintenance",
    "title": "Real CLI Goal Loop",
    "intent": "Verify a real CLI goal loop where the second judge round confirms completion.",
    "verify": "live judge round-trip",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/NousResearch/hermes-agent/pull/18262",
    "source_name": "NousResearch/hermes-agent PR 18262",
    "source_type": "github-pr",
    "evidence": "print hello, Ralph loop",
    "evidence_summary": "print hello, Ralph loop; source: NousResearch/hermes-agent PR 18262; type: github-pr; verification: live judge round-trip",
    "prompt": "/goal\nGOAL:\nComplete Real CLI Goal Loop for a goal-management workflow: Verify a real CLI goal loop where the second judge round confirms completion.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `live judge round-trip`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify a real CLI goal loop where the second judge round confirms completion.\n- The verification command or evidence path succeeds: `live judge round-trip`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `live judge round-trip` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-hermes-real-cli-loop.html"
  },
  {
    "id": "github-hermes-file-verification",
    "slug": "github-hermes-file-verification",
    "category": "goal-maintenance",
    "title": "Verify File Creation",
    "intent": "Verify that a requested file was actually created instead of trusting the agent claim.",
    "verify": "find and read_file evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/NousResearch/hermes-agent/issues/18421",
    "source_name": "NousResearch/hermes-agent issue 18421",
    "source_type": "github-issue",
    "evidence": "/home/ubuntu/ml-resumo.md",
    "evidence_summary": "/home/ubuntu/ml-resumo.md; source: NousResearch/hermes-agent issue 18421; type: github-issue; verification: find and read_file evidence",
    "prompt": "/goal\nGOAL:\nComplete Verify File Creation for a goal-management workflow: Verify that a requested file was actually created instead of trusting the agent claim.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `find and read_file evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Verify that a requested file was actually created instead of trusting the agent claim.\n- The verification command or evidence path succeeds: `find and read_file evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `find and read_file evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-hermes-file-verification.html"
  },
  {
    "id": "github-hermes-goal-queue",
    "slug": "github-hermes-goal-queue",
    "category": "goal-maintenance",
    "title": "Queue Follow-Up Goals",
    "intent": "Promote queued follow-up goals: fix tests, run full tests, then produce coverage.",
    "verify": "queue promotion evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/NousResearch/hermes-agent/issues/22617",
    "source_name": "NousResearch/hermes-agent issue 22617",
    "source_type": "github-issue",
    "evidence": "/goal Fix failing tests",
    "evidence_summary": "/goal Fix failing tests; source: NousResearch/hermes-agent issue 22617; type: github-issue; verification: queue promotion evidence",
    "prompt": "/goal\nGOAL:\nComplete Queue Follow-Up Goals for a goal-management workflow: Promote queued follow-up goals: fix tests, run full tests, then produce coverage.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `queue promotion evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Promote queued follow-up goals: fix tests, run full tests, then produce coverage.\n- The verification command or evidence path succeeds: `queue promotion evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `queue promotion evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-hermes-goal-queue.html"
  },
  {
    "id": "openhands-api-integration-tests",
    "slug": "openhands-api-integration-tests",
    "category": "backend-api",
    "title": "API Integration Tests",
    "intent": "Add end-to-end tests for product API endpoints with success and error cases.",
    "verify": "jest integration tests with test database",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Add integration tests for the /api/products endpoints",
    "evidence_summary": "Add integration tests for the /api/products endpoints; source: OpenHands tutorial library; type: official-agent-task; verification: jest integration tests with test database",
    "prompt": "/goal\nGOAL:\nComplete API Integration Tests for a backend API service: Add end-to-end tests for product API endpoints with success and error cases.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `jest integration tests with test database`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add end-to-end tests for product API endpoints with success and error cases.\n- The verification command or evidence path succeeds: `jest integration tests with test database`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `jest integration tests with test database` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-api-integration-tests.html"
  },
  {
    "id": "claude-dev-database-migration",
    "slug": "claude-dev-database-migration",
    "category": "backend-data",
    "title": "Dev Database Migration Proof",
    "intent": "Write a migration, run it against the dev database, and confirm the schema matches.",
    "verify": "migration applied to dev DB and schema comparison",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/prompt-library",
    "source_name": "Claude Code prompt library",
    "source_type": "official-agent-task",
    "evidence": "write the migration, run it against the dev database, and confirm the schema matches",
    "evidence_summary": "write the migration, run it against the dev database, and confirm the schema matches; source: Claude Code prompt library; type: official-agent-task; verification: migration applied to dev DB and schema comparison",
    "prompt": "/goal\nGOAL:\nComplete Dev Database Migration Proof for a data-backed backend service: Write a migration, run it against the dev database, and confirm the schema matches.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `migration applied to dev DB and schema comparison`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write a migration, run it against the dev database, and confirm the schema matches.\n- The verification command or evidence path succeeds: `migration applied to dev DB and schema comparison`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `migration applied to dev DB and schema comparison` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-dev-database-migration.html"
  },
  {
    "id": "github-accessibility-html-wcag",
    "slug": "github-accessibility-html-wcag",
    "category": "accessibility",
    "title": "HTML WCAG Instruction Audit",
    "intent": "Audit HTML changes against WCAG guidance and prove the Lighthouse accessibility audit passes.",
    "verify": "Lighthouse accessibility audit",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/customization-library/custom-instructions/accessibility-auditor",
    "source_name": "GitHub Copilot accessibility auditor",
    "source_type": "official-agent-task",
    "evidence": "generate accessible, inclusive HTML that follows WCAG guidelines",
    "evidence_summary": "generate accessible, inclusive HTML that follows WCAG guidelines; source: GitHub Copilot accessibility auditor; type: official-agent-task; verification: Lighthouse accessibility audit",
    "prompt": "/goal\nGOAL:\nComplete HTML WCAG Instruction Audit for a web or mobile interface: Audit HTML changes against WCAG guidance and prove the Lighthouse accessibility audit passes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect interactive elements, semantics, focus management, and a11y reports.\n- Establish a baseline by running or locating evidence for: `Lighthouse accessibility audit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not hide controls from assistive technology to silence audit findings.\n- Keep keyboard, focus, semantic, and visual checks together.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Audit HTML changes against WCAG guidance and prove the Lighthouse accessibility audit passes.\n- The verification command or evidence path succeeds: `Lighthouse accessibility audit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `Lighthouse accessibility audit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-accessibility-html-wcag.html"
  },
  {
    "id": "claude-reference-layout-design",
    "slug": "claude-reference-layout-design",
    "category": "design",
    "title": "Reference Layout Match",
    "intent": "Build a settings page that follows an existing profile page layout instead of inventing a new pattern.",
    "verify": "visual comparison against profile page",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/prompt-library",
    "source_name": "Claude Code prompt library",
    "source_type": "official-agent-task",
    "evidence": "add a settings page that follows the same layout as the profile page",
    "evidence_summary": "add a settings page that follows the same layout as the profile page; source: Claude Code prompt library; type: official-agent-task; verification: visual comparison against profile page",
    "prompt": "/goal\nGOAL:\nComplete Reference Layout Match for a product UI codebase: Build a settings page that follows an existing profile page layout instead of inventing a new pattern.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `visual comparison against profile page`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build a settings page that follows an existing profile page layout instead of inventing a new pattern.\n- The verification command or evidence path succeeds: `visual comparison against profile page`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `visual comparison against profile page` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-reference-layout-design.html"
  },
  {
    "id": "github-mobile-agent-task-handoff",
    "slug": "github-mobile-agent-task-handoff",
    "category": "mobile",
    "title": "Mobile Agent Task Handoff",
    "intent": "Prepare and track a coding-agent task started from GitHub Mobile with review-ready evidence.",
    "verify": "GitHub Mobile agent task creates a PR",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/assign-copilot-to-an-issue",
    "source_name": "GitHub Copilot coding agent docs",
    "source_type": "official-agent-task",
    "evidence": "assign an issue to Copilot on GitHub Mobile",
    "evidence_summary": "assign an issue to Copilot on GitHub Mobile; source: GitHub Copilot coding agent docs; type: official-agent-task; verification: GitHub Mobile agent task creates a PR",
    "prompt": "/goal\nGOAL:\nComplete Mobile Agent Task Handoff for a mobile or responsive application: Prepare and track a coding-agent task started from GitHub Mobile with review-ready evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `GitHub Mobile agent task creates a PR`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prepare and track a coding-agent task started from GitHub Mobile with review-ready evidence.\n- The verification command or evidence path succeeds: `GitHub Mobile agent task creates a PR`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `GitHub Mobile agent task creates a PR` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-mobile-agent-task-handoff.html"
  },
  {
    "id": "openai-agent-trace-evals",
    "slug": "openai-agent-trace-evals",
    "category": "ai-evals",
    "title": "Trace-Graded Agent Regression",
    "intent": "Create trace-based evals that catch workflow regressions across tool calls and handoffs.",
    "verify": "agent eval report with graded traces",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://platform.openai.com/docs/guides/agent-evals",
    "source_name": "OpenAI agent evals docs",
    "source_type": "official-workflow",
    "evidence": "trace grading functionality",
    "evidence_summary": "trace grading functionality; source: OpenAI agent evals docs; type: official-workflow; verification: agent eval report with graded traces",
    "prompt": "/goal\nGOAL:\nComplete Trace-Graded Agent Regression for an AI evaluation project: Create trace-based evals that catch workflow regressions across tool calls and handoffs.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `agent eval report with graded traces`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create trace-based evals that catch workflow regressions across tool calls and handoffs.\n- The verification command or evidence path succeeds: `agent eval report with graded traces`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `agent eval report with graded traces` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-agent-trace-evals.html"
  },
  {
    "id": "openai-agent-tracing-observability",
    "slug": "openai-agent-tracing-observability",
    "category": "ai-ops",
    "title": "Agent Trace Observability",
    "intent": "Instrument agent runs so LLM generations, tool calls, handoffs, guardrails, and custom events are traceable.",
    "verify": "trace dashboard shows spans for one agent run",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://openai.github.io/openai-agents-python/tracing/",
    "source_name": "OpenAI Agents SDK tracing docs",
    "source_type": "official-workflow",
    "evidence": "built-in tracing collects LLM generations, tool calls, handoffs, guardrails",
    "evidence_summary": "built-in tracing collects LLM generations, tool calls, handoffs, guardrails; source: OpenAI Agents SDK tracing docs; type: official-workflow; verification: trace dashboard shows spans for one agent run",
    "prompt": "/goal\nGOAL:\nComplete Agent Trace Observability for an AI application runtime: Instrument agent runs so LLM generations, tool calls, handoffs, guardrails, and custom events are traceable.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `trace dashboard shows spans for one agent run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Instrument agent runs so LLM generations, tool calls, handoffs, guardrails, and custom events are traceable.\n- The verification command or evidence path succeeds: `trace dashboard shows spans for one agent run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `trace dashboard shows spans for one agent run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-agent-tracing-observability.html"
  },
  {
    "id": "openhands-csv-processing-report",
    "slug": "openhands-csv-processing-report",
    "category": "data-eng",
    "title": "CSV Processing Report",
    "intent": "Create a data processing script that validates CSV input and generates an analysis report.",
    "verify": "script output report and validation checks",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Process CSV data and generate a report",
    "evidence_summary": "Process CSV data and generate a report; source: OpenHands tutorial library; type: official-agent-task; verification: script output report and validation checks",
    "prompt": "/goal\nGOAL:\nComplete CSV Processing Report for a data pipeline project: Create a data processing script that validates CSV input and generates an analysis report.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `script output report and validation checks`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create a data processing script that validates CSV input and generates an analysis report.\n- The verification command or evidence path succeeds: `script output report and validation checks`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `script output report and validation checks` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-csv-processing-report.html"
  },
  {
    "id": "openhands-remote-agent-server-smoke",
    "slug": "openhands-remote-agent-server-smoke",
    "category": "devops-runtime",
    "title": "Remote Agent Server Smoke",
    "intent": "Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.",
    "verify": "remote server smoke run and websocket event evidence",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/sdk/guides/agent-server/overview",
    "source_name": "OpenHands remote agent server docs",
    "source_type": "official-workflow",
    "evidence": "Remote Agent Servers package the Software Agent SDK into containers",
    "evidence_summary": "Remote Agent Servers package the Software Agent SDK into containers; source: OpenHands remote agent server docs; type: official-workflow; verification: remote server smoke run and websocket event evidence",
    "prompt": "/goal\nGOAL:\nComplete Remote Agent Server Smoke for a deployed service: Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Dockerfiles, deployment manifests, runtime config, and health checks.\n- Establish a baseline by running or locating evidence for: `remote server smoke run and websocket event evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not deploy to production automatically; stop with a verified plan if live credentials are required.\n- Keep rollback and health-check evidence attached to the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Deploy an isolated remote agent server and prove event streaming, workspace access, and command execution work.\n- The verification command or evidence path succeeds: `remote server smoke run and websocket event evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `remote server smoke run and websocket event evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-remote-agent-server-smoke.html"
  },
  {
    "id": "openai-tool-guardrails-appsec",
    "slug": "openai-tool-guardrails-appsec",
    "category": "security-appsec",
    "title": "Tool Guardrails For AppSec",
    "intent": "Add tool guardrails around high-risk agent tool calls and stop unsafe input or output before execution continues.",
    "verify": "guardrail tests trigger on unsafe tool input/output",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://openai.github.io/openai-agents-python/guardrails/",
    "source_name": "OpenAI Agents SDK guardrails docs",
    "source_type": "official-workflow",
    "evidence": "tool guardrails run on every custom function-tool invocation",
    "evidence_summary": "tool guardrails run on every custom function-tool invocation; source: OpenAI Agents SDK guardrails docs; type: official-workflow; verification: guardrail tests trigger on unsafe tool input/output",
    "prompt": "/goal\nGOAL:\nComplete Tool Guardrails For AppSec for an application with security-sensitive code paths: Add tool guardrails around high-risk agent tool calls and stop unsafe input or output before execution continues.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `guardrail tests trigger on unsafe tool input/output`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add tool guardrails around high-risk agent tool calls and stop unsafe input or output before execution continues.\n- The verification command or evidence path succeeds: `guardrail tests trigger on unsafe tool input/output`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `guardrail tests trigger on unsafe tool input/output` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-tool-guardrails-appsec.html"
  },
  {
    "id": "openhands-slow-query-optimization",
    "slug": "openhands-slow-query-optimization",
    "category": "backend-data",
    "title": "Slow Query Optimization Report",
    "intent": "Analyze slow query logs, explain bottlenecks, recommend indexes or rewrites, and produce prioritized SQL changes.",
    "verify": "EXPLAIN plans and reports/query_optimization.md",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Analyze our slow query log and identify optimization opportunities",
    "evidence_summary": "Analyze our slow query log and identify optimization opportunities; source: OpenHands tutorial library; type: official-agent-task; verification: EXPLAIN plans and reports/query_optimization.md",
    "prompt": "/goal\nGOAL:\nComplete Slow Query Optimization Report for a data-backed backend service: Analyze slow query logs, explain bottlenecks, recommend indexes or rewrites, and produce prioritized SQL changes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `EXPLAIN plans and reports/query_optimization.md`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Analyze slow query logs, explain bottlenecks, recommend indexes or rewrites, and produce prioritized SQL changes.\n- The verification command or evidence path succeeds: `EXPLAIN plans and reports/query_optimization.md`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `EXPLAIN plans and reports/query_optimization.md` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-slow-query-optimization.html"
  },
  {
    "id": "openhands-rate-limited-web-scraper",
    "slug": "openhands-rate-limited-web-scraper",
    "category": "data-eng",
    "title": "Rate-Limited Web Scraper",
    "intent": "Build a scraper that extracts product data across paginated pages while respecting rate limits and logging progress.",
    "verify": "scraper smoke run and products.json schema check",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Create a web scraper to extract product information",
    "evidence_summary": "Create a web scraper to extract product information; source: OpenHands tutorial library; type: official-agent-task; verification: scraper smoke run and products.json schema check",
    "prompt": "/goal\nGOAL:\nComplete Rate-Limited Web Scraper for a data pipeline project: Build a scraper that extracts product data across paginated pages while respecting rate limits and logging progress.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect ETL jobs, schemas, source contracts, transformations, and data quality tests.\n- Establish a baseline by running or locating evidence for: `scraper smoke run and products.json schema check`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build a scraper that extracts product data across paginated pages while respecting rate limits and logging progress.\n- The verification command or evidence path succeeds: `scraper smoke run and products.json schema check`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `scraper smoke run and products.json schema check` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-rate-limited-web-scraper.html"
  },
  {
    "id": "openhands-security-pr-review",
    "slug": "openhands-security-pr-review",
    "category": "security-appsec",
    "title": "Security PR Review",
    "intent": "Review a pull request for input validation, authentication, injection, XSS, and secrets risks with file-level fixes.",
    "verify": "Markdown PR review with severity, affected lines, and suggested fixes",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Review this pull request for security issues",
    "evidence_summary": "Review this pull request for security issues; source: OpenHands tutorial library; type: official-agent-task; verification: Markdown PR review with severity, affected lines, and suggested fixes",
    "prompt": "/goal\nGOAL:\nComplete Security PR Review for an application with security-sensitive code paths: Review a pull request for input validation, authentication, injection, XSS, and secrets risks with file-level fixes.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `Markdown PR review with severity, affected lines, and suggested fixes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Review a pull request for input validation, authentication, injection, XSS, and secrets risks with file-level fixes.\n- The verification command or evidence path succeeds: `Markdown PR review with severity, affected lines, and suggested fixes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `Markdown PR review with severity, affected lines, and suggested fixes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-security-pr-review.html"
  },
  {
    "id": "openhands-orderservice-performance-review",
    "slug": "openhands-orderservice-performance-review",
    "category": "performance",
    "title": "Order Service Performance Review",
    "intent": "Inspect service code for N+1 queries, missing indexes, inefficient loops, missing caches, and unnecessary fetching.",
    "verify": "performance review report with impact and optimized code paths",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Review the OrderService class for performance issues",
    "evidence_summary": "Review the OrderService class for performance issues; source: OpenHands tutorial library; type: official-agent-task; verification: performance review report with impact and optimized code paths",
    "prompt": "/goal\nGOAL:\nComplete Order Service Performance Review for a web application with measurable performance goals: Inspect service code for N+1 queries, missing indexes, inefficient loops, missing caches, and unnecessary fetching.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `performance review report with impact and optimized code paths`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Inspect service code for N+1 queries, missing indexes, inefficient loops, missing caches, and unnecessary fetching.\n- The verification command or evidence path succeeds: `performance review report with impact and optimized code paths`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `performance review report with impact and optimized code paths` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-orderservice-performance-review.html"
  },
  {
    "id": "openhands-checkout-crash-regression",
    "slug": "openhands-checkout-crash-regression",
    "category": "investigation",
    "title": "Checkout Crash Regression Fix",
    "intent": "Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.",
    "verify": "crash reproduction test and checkout regression test",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Fix the crash in the checkout process",
    "evidence_summary": "Fix the crash in the checkout process; source: OpenHands tutorial library; type: official-agent-task; verification: crash reproduction test and checkout regression test",
    "prompt": "/goal\nGOAL:\nComplete Checkout Crash Regression Fix for an investigation task: Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect logs, traces, reproduction notes, source paths, and the final report.\n- Establish a baseline by running or locating evidence for: `crash reproduction test and checkout regression test`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Separate observed evidence from hypotheses.\n- Do not patch production code until the root cause is reproduced or strongly evidenced.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reproduce a checkout crash from a stack trace, identify the root cause, fix it, and add a regression test.\n- The verification command or evidence path succeeds: `crash reproduction test and checkout regression test`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `crash reproduction test and checkout regression test` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-checkout-crash-regression.html"
  },
  {
    "id": "openhands-node-memory-leak-fix",
    "slug": "openhands-node-memory-leak-fix",
    "category": "performance",
    "title": "Node Memory Leak Fix",
    "intent": "Investigate a growing-memory Node.js process, isolate the leak source, fix it, and add monitoring for recurrence.",
    "verify": "heap comparison or load test plus monitoring evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Investigate and fix the memory leak in our Node.js application",
    "evidence_summary": "Investigate and fix the memory leak in our Node.js application; source: OpenHands tutorial library; type: official-agent-task; verification: heap comparison or load test plus monitoring evidence",
    "prompt": "/goal\nGOAL:\nComplete Node Memory Leak Fix for a web application with measurable performance goals: Investigate a growing-memory Node.js process, isolate the leak source, fix it, and add monitoring for recurrence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `heap comparison or load test plus monitoring evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Investigate a growing-memory Node.js process, isolate the leak source, fix it, and add monitoring for recurrence.\n- The verification command or evidence path succeeds: `heap comparison or load test plus monitoring evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `heap comparison or load test plus monitoring evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-node-memory-leak-fix.html"
  },
  {
    "id": "openhands-user-preferences-api",
    "slug": "openhands-user-preferences-api",
    "category": "backend-api",
    "title": "User Preferences API",
    "intent": "Add GET, PUT, and PATCH endpoints for user preferences with validation, service logic, OpenAPI docs, and tests.",
    "verify": "unit and integration tests plus OpenAPI endpoint documentation",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Add a user preferences API endpoint",
    "evidence_summary": "Add a user preferences API endpoint; source: OpenHands tutorial library; type: official-agent-task; verification: unit and integration tests plus OpenAPI endpoint documentation",
    "prompt": "/goal\nGOAL:\nComplete User Preferences API for a backend API service: Add GET, PUT, and PATCH endpoints for user preferences with validation, service logic, OpenAPI docs, and tests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `unit and integration tests plus OpenAPI endpoint documentation`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add GET, PUT, and PATCH endpoints for user preferences with validation, service logic, OpenAPI docs, and tests.\n- The verification command or evidence path succeeds: `unit and integration tests plus OpenAPI endpoint documentation`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `unit and integration tests plus OpenAPI endpoint documentation` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-user-preferences-api.html"
  },
  {
    "id": "openhands-feature-flag-system",
    "slug": "openhands-feature-flag-system",
    "category": "product",
    "title": "Feature Flag System",
    "intent": "Implement boolean, percentage, and user-based feature flags with service logic, API middleware, a React hook, docs, and tests.",
    "verify": "feature flag service, hook, middleware, and rollout tests",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.openhands.dev/openhands/usage/get-started/tutorials",
    "source_name": "OpenHands tutorial library",
    "source_type": "official-agent-task",
    "evidence": "Implement a feature flag system for our application",
    "evidence_summary": "Implement a feature flag system for our application; source: OpenHands tutorial library; type: official-agent-task; verification: feature flag service, hook, middleware, and rollout tests",
    "prompt": "/goal\nGOAL:\nComplete Feature Flag System for a product planning and implementation repo: Implement boolean, percentage, and user-based feature flags with service logic, API middleware, a React hook, docs, and tests.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `feature flag service, hook, middleware, and rollout tests`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement boolean, percentage, and user-based feature flags with service logic, API middleware, a React hook, docs, and tests.\n- The verification command or evidence path succeeds: `feature flag service, hook, middleware, and rollout tests`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `feature flag service, hook, middleware, and rollout tests` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openhands-feature-flag-system.html"
  },
  {
    "id": "claude-build-log-diagnosis",
    "slug": "claude-build-log-diagnosis",
    "category": "investigation",
    "title": "Build Log Failure Diagnosis",
    "intent": "Use a provided build log to explain why the build fails and identify the smallest verified fix path.",
    "verify": "failing build command reproduced or build.log root-cause report",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/prompt-library",
    "source_name": "Claude Code prompt library",
    "source_type": "official-agent-task",
    "evidence": "why is the build failing? @build.log",
    "evidence_summary": "why is the build failing? @build.log; source: Claude Code prompt library; type: official-agent-task; verification: failing build command reproduced or build.log root-cause report",
    "prompt": "/goal\nGOAL:\nComplete Build Log Failure Diagnosis for an investigation task: Use a provided build log to explain why the build fails and identify the smallest verified fix path.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect logs, traces, reproduction notes, source paths, and the final report.\n- Establish a baseline by running or locating evidence for: `failing build command reproduced or build.log root-cause report`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Separate observed evidence from hypotheses.\n- Do not patch production code until the root cause is reproduced or strongly evidenced.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a provided build log to explain why the build fails and identify the smallest verified fix path.\n- The verification command or evidence path succeeds: `failing build command reproduced or build.log root-cause report`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `failing build command reproduced or build.log root-cause report` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-build-log-diagnosis.html"
  },
  {
    "id": "claude-payment-retry-diagram",
    "slug": "claude-payment-retry-diagram",
    "category": "docs",
    "title": "Payment Retry Logic Diagram",
    "intent": "Explain payment retry behavior as a browsable HTML page with a diagram for developer or support review.",
    "verify": "HTML page opens locally and diagram matches the retry code path",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://code.claude.com/docs/en/prompt-library",
    "source_name": "Claude Code prompt library",
    "source_type": "official-agent-task",
    "evidence": "explain how the payment retry logic works as an HTML page with a diagram",
    "evidence_summary": "explain how the payment retry logic works as an HTML page with a diagram; source: Claude Code prompt library; type: official-agent-task; verification: HTML page opens locally and diagram matches the retry code path",
    "prompt": "/goal\nGOAL:\nComplete Payment Retry Logic Diagram for a developer-facing documentation site or repository: Explain payment retry behavior as a browsable HTML page with a diagram for developer or support review.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `HTML page opens locally and diagram matches the retry code path`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Explain payment retry behavior as a browsable HTML page with a diagram for developer or support review.\n- The verification command or evidence path succeeds: `HTML page opens locally and diagram matches the retry code path`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `HTML page opens locally and diagram matches the retry code path` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-payment-retry-diagram.html"
  },
  {
    "id": "deadreckon-coherence-closure",
    "slug": "deadreckon-coherence-closure",
    "category": "workflow",
    "title": "User-Facing Coherence Closure",
    "intent": "Finish a coherence pass so CLI help, docs, JSON/plain output, colors, prompts, flags, and next-action grammar stay aligned.",
    "verify": "snapshot tests, JSON leak tests, TUI render tests, docs examples, cargo workspace checks",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/gregce/deadreckon/blob/main/docs/goals/2026-05-17-1403-deadreckon-coherence-closure-goal.md",
    "source_name": "deadreckon goal corpus",
    "source_type": "third-party-project",
    "evidence": "same words, colors, streams, flags, prompts, and next-action grammar",
    "evidence_summary": "same words, colors, streams, flags, prompts, and next-action grammar; source: deadreckon goal corpus; type: third-party-project; verification: snapshot tests, JSON leak tests, TUI render tests, docs examples, cargo workspace checks",
    "prompt": "/goal\nGOAL:\nComplete User-Facing Coherence Closure for a coding-agent workflow repository: Finish a coherence pass so CLI help, docs, JSON/plain output, colors, prompts, flags, and next-action grammar stay aligned.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `snapshot tests, JSON leak tests, TUI render tests, docs examples, cargo workspace checks`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Finish a coherence pass so CLI help, docs, JSON/plain output, colors, prompts, flags, and next-action grammar stay aligned.\n- The verification command or evidence path succeeds: `snapshot tests, JSON leak tests, TUI render tests, docs examples, cargo workspace checks`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `snapshot tests, JSON leak tests, TUI render tests, docs examples, cargo workspace checks` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/deadreckon-coherence-closure.html"
  },
  {
    "id": "deadreckon-semantic-merge-repair",
    "slug": "deadreckon-semantic-merge-repair",
    "category": "orchestration",
    "title": "DAG-Aware Semantic Merge Repair",
    "intent": "Make orchestration merge failures repairable by using plan DAG context, conflict bundles, planner-mediated repair, and bounded retry.",
    "verify": "DAG smoke, repair smoke, refusal smoke, cargo build/test/clippy/fmt",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/gregce/deadreckon/blob/main/docs/goals/2026-05-16-1122-deadreckon-semantic-merge-repair-goal.md",
    "source_name": "deadreckon goal corpus",
    "source_type": "third-party-project",
    "evidence": "Land DAG-aware merge plus automatic planner-mediated repair for true conflicts",
    "evidence_summary": "Land DAG-aware merge plus automatic planner-mediated repair for true conflicts; source: deadreckon goal corpus; type: third-party-project; verification: DAG smoke, repair smoke, refusal smoke, cargo build/test/clippy/fmt",
    "prompt": "/goal\nGOAL:\nComplete DAG-Aware Semantic Merge Repair for an agent orchestration task: Make orchestration merge failures repairable by using plan DAG context, conflict bundles, planner-mediated repair, and bounded retry.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect plans, worktrees, subtask ownership, PRs, and coordination notes.\n- Establish a baseline by running or locating evidence for: `DAG smoke, repair smoke, refusal smoke, cargo build/test/clippy/fmt`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Keep subtask ownership explicit and avoid overlapping write scopes.\n- Do not merge or deploy automatically unless the goal explicitly allows it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Make orchestration merge failures repairable by using plan DAG context, conflict bundles, planner-mediated repair, and bounded retry.\n- The verification command or evidence path succeeds: `DAG smoke, repair smoke, refusal smoke, cargo build/test/clippy/fmt`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `DAG smoke, repair smoke, refusal smoke, cargo build/test/clippy/fmt` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/deadreckon-semantic-merge-repair.html"
  },
  {
    "id": "deadreckon-orchestration-eventbus",
    "slug": "deadreckon-orchestration-eventbus",
    "category": "orchestration",
    "title": "Plan EventBus Live UX",
    "intent": "Unify plan, fork, merge, and orchestrate around shared builders and a live plan event stream.",
    "verify": "orchestrate, coherence, attach_plan, plan_event_bus, plan_event, fmt, targeted clippy",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/gregce/deadreckon/blob/main/docs/goals/2026-05-18-2226-deadreckon-orchestration-eventbus-goal.md",
    "source_name": "deadreckon goal corpus",
    "source_type": "third-party-project",
    "evidence": "move plan attach onto a shared plan event stream",
    "evidence_summary": "move plan attach onto a shared plan event stream; source: deadreckon goal corpus; type: third-party-project; verification: orchestrate, coherence, attach_plan, plan_event_bus, plan_event, fmt, targeted clippy",
    "prompt": "/goal\nGOAL:\nComplete Plan EventBus Live UX for an agent orchestration task: Unify plan, fork, merge, and orchestrate around shared builders and a live plan event stream.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect plans, worktrees, subtask ownership, PRs, and coordination notes.\n- Establish a baseline by running or locating evidence for: `orchestrate, coherence, attach_plan, plan_event_bus, plan_event, fmt, targeted clippy`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Keep subtask ownership explicit and avoid overlapping write scopes.\n- Do not merge or deploy automatically unless the goal explicitly allows it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Unify plan, fork, merge, and orchestrate around shared builders and a live plan event stream.\n- The verification command or evidence path succeeds: `orchestrate, coherence, attach_plan, plan_event_bus, plan_event, fmt, targeted clippy`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `orchestrate, coherence, attach_plan, plan_event_bus, plan_event, fmt, targeted clippy` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/deadreckon-orchestration-eventbus.html"
  },
  {
    "id": "deadreckon-implementation-notes-ledger",
    "slug": "deadreckon-implementation-notes-ledger",
    "category": "docs",
    "title": "Implementation Notes Decision Ledger",
    "intent": "Keep live implementation notes and the final run decisions document aligned around decisions, deviations, tradeoffs, and open questions.",
    "verify": "self-documenting run tests, doc kind tests, implementation notes freshness smoke, fmt, targeted clippy",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/gregce/deadreckon/blob/main/docs/goals/2026-05-18-2336-deadreckon-implementation-notes-goal.md",
    "source_name": "deadreckon goal corpus",
    "source_type": "third-party-project",
    "evidence": "canonical implementation decision ledger",
    "evidence_summary": "canonical implementation decision ledger; source: deadreckon goal corpus; type: third-party-project; verification: self-documenting run tests, doc kind tests, implementation notes freshness smoke, fmt, targeted clippy",
    "prompt": "/goal\nGOAL:\nComplete Implementation Notes Decision Ledger for a developer-facing documentation site or repository: Keep live implementation notes and the final run decisions document aligned around decisions, deviations, tradeoffs, and open questions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `self-documenting run tests, doc kind tests, implementation notes freshness smoke, fmt, targeted clippy`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Keep live implementation notes and the final run decisions document aligned around decisions, deviations, tradeoffs, and open questions.\n- The verification command or evidence path succeeds: `self-documenting run tests, doc kind tests, implementation notes freshness smoke, fmt, targeted clippy`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `self-documenting run tests, doc kind tests, implementation notes freshness smoke, fmt, targeted clippy` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/deadreckon-implementation-notes-ledger.html"
  },
  {
    "id": "goal-agent-daily-priority-loop",
    "slug": "goal-agent-daily-priority-loop",
    "category": "goal-maintenance",
    "title": "Daily Goal Priority Loop",
    "intent": "Use a persistent goal profile to compute daily priorities, execute them, log progress, and refresh status across sessions.",
    "verify": "/goal:next priorities, /goal:log entry, /goal:status dashboard, progress-tracker.md updated",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ishaquehassan/goal-agent",
    "source_name": "Goal Agent README",
    "source_type": "tool-readme",
    "evidence": "Your daily loop: /goal:next to see what to do, execute it, /goal:log to record it",
    "evidence_summary": "Your daily loop: /goal:next to see what to do, execute it, /goal:log to record it; source: Goal Agent README; type: tool-readme; verification: /goal:next priorities, /goal:log entry, /goal:status dashboard, progress-tracker.md updated",
    "prompt": "/goal\nGOAL:\nComplete Daily Goal Priority Loop for a goal-management workflow: Use a persistent goal profile to compute daily priorities, execute them, log progress, and refresh status across sessions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `/goal:next priorities, /goal:log entry, /goal:status dashboard, progress-tracker.md updated`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Use a persistent goal profile to compute daily priorities, execute them, log progress, and refresh status across sessions.\n- The verification command or evidence path succeeds: `/goal:next priorities, /goal:log entry, /goal:status dashboard, progress-tracker.md updated`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `/goal:next priorities, /goal:log entry, /goal:status dashboard, progress-tracker.md updated` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-agent-daily-priority-loop.html"
  },
  {
    "id": "goal-agent-profile-optimization",
    "slug": "goal-agent-profile-optimization",
    "category": "goal-maintenance",
    "title": "Goal-Aligned Profile Optimization",
    "intent": "Audit and update professional profiles against a stated goal while recording the resulting progress and gaps.",
    "verify": "/goal:optimize platform output plus updated goal memory files",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ishaquehassan/goal-agent",
    "source_name": "Goal Agent README",
    "source_type": "tool-readme",
    "evidence": "/goal:optimize [platform]",
    "evidence_summary": "/goal:optimize [platform]; source: Goal Agent README; type: tool-readme; verification: /goal:optimize platform output plus updated goal memory files",
    "prompt": "/goal\nGOAL:\nComplete Goal-Aligned Profile Optimization for a goal-management workflow: Audit and update professional profiles against a stated goal while recording the resulting progress and gaps.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `/goal:optimize platform output plus updated goal memory files`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Audit and update professional profiles against a stated goal while recording the resulting progress and gaps.\n- The verification command or evidence path succeeds: `/goal:optimize platform output plus updated goal memory files`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `/goal:optimize platform output plus updated goal memory files` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-agent-profile-optimization.html"
  },
  {
    "id": "goal-agent-content-engagement-loop",
    "slug": "goal-agent-content-engagement-loop",
    "category": "goal-maintenance",
    "title": "Content And Audience Engagement Loop",
    "intent": "Generate goal-aligned content, publish or promote it, engage with target audience posts, and log the session outcome.",
    "verify": "/goal:write output, /goal:engage actions, /goal:log entry, content-calendar.md updated",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ishaquehassan/goal-agent",
    "source_name": "Goal Agent README",
    "source_type": "tool-readme",
    "evidence": "/goal:write article",
    "evidence_summary": "/goal:write article; source: Goal Agent README; type: tool-readme; verification: /goal:write output, /goal:engage actions, /goal:log entry, content-calendar.md updated",
    "prompt": "/goal\nGOAL:\nComplete Content And Audience Engagement Loop for a goal-management workflow: Generate goal-aligned content, publish or promote it, engage with target audience posts, and log the session outcome.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `/goal:write output, /goal:engage actions, /goal:log entry, content-calendar.md updated`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Generate goal-aligned content, publish or promote it, engage with target audience posts, and log the session outcome.\n- The verification command or evidence path succeeds: `/goal:write output, /goal:engage actions, /goal:log entry, content-calendar.md updated`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `/goal:write output, /goal:engage actions, /goal:log entry, content-calendar.md updated` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-agent-content-engagement-loop.html"
  },
  {
    "id": "claude-flow-sparc-payment-plan",
    "slug": "claude-flow-sparc-payment-plan",
    "category": "backend-api",
    "title": "SPARC Payment Processing Plan",
    "intent": "Plan and implement payment processing through SPARC phases with requirements, pseudocode, architecture, TDD refinement, and integration.",
    "verify": "acceptance criteria, API contracts, unit and integration tests, coverage target, integration validation",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ruvnet/claude-flow/blob/main/.agents/skills/agent-code-goal-planner/SKILL.md",
    "source_name": "claude-flow code-goal-planner skill",
    "source_type": "tool-readme",
    "evidence": "goal: implement_payment_processing_with_sparc",
    "evidence_summary": "goal: implement_payment_processing_with_sparc; source: claude-flow code-goal-planner skill; type: tool-readme; verification: acceptance criteria, API contracts, unit and integration tests, coverage target, integration validation",
    "prompt": "/goal\nGOAL:\nComplete SPARC Payment Processing Plan for a backend API service: Plan and implement payment processing through SPARC phases with requirements, pseudocode, architecture, TDD refinement, and integration.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect API routes, OpenAPI specs, handlers, middleware, and API tests.\n- Establish a baseline by running or locating evidence for: `acceptance criteria, API contracts, unit and integration tests, coverage target, integration validation`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Plan and implement payment processing through SPARC phases with requirements, pseudocode, architecture, TDD refinement, and integration.\n- The verification command or evidence path succeeds: `acceptance criteria, API contracts, unit and integration tests, coverage target, integration validation`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `acceptance criteria, API contracts, unit and integration tests, coverage target, integration validation` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-flow-sparc-payment-plan.html"
  },
  {
    "id": "claude-flow-api-latency-goap",
    "slug": "claude-flow-api-latency-goap",
    "category": "performance",
    "title": "GOAP API Latency Reduction",
    "intent": "Reduce API latency by profiling current performance, optimizing database queries, adding caching, and improving code paths.",
    "verify": "p50 latency, p99 latency, throughput, database explain, before/after performance evidence",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ruvnet/claude-flow/blob/main/.agents/skills/agent-code-goal-planner/SKILL.md",
    "source_name": "claude-flow code-goal-planner skill",
    "source_type": "tool-readme",
    "evidence": "goal: reduce_api_latency_50_percent",
    "evidence_summary": "goal: reduce_api_latency_50_percent; source: claude-flow code-goal-planner skill; type: tool-readme; verification: p50 latency, p99 latency, throughput, database explain, before/after performance evidence",
    "prompt": "/goal\nGOAL:\nComplete GOAP API Latency Reduction for a web application with measurable performance goals: Reduce API latency by profiling current performance, optimizing database queries, adding caching, and improving code paths.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `p50 latency, p99 latency, throughput, database explain, before/after performance evidence`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce API latency by profiling current performance, optimizing database queries, adding caching, and improving code paths.\n- The verification command or evidence path succeeds: `p50 latency, p99 latency, throughput, database explain, before/after performance evidence`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `p50 latency, p99 latency, throughput, database explain, before/after performance evidence` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-flow-api-latency-goap.html"
  },
  {
    "id": "claude-flow-coverage-goap",
    "slug": "claude-flow-coverage-goap",
    "category": "testing",
    "title": "GOAP Coverage Target Plan",
    "intent": "Raise test coverage with an explicit test pyramid across unit, integration, and end-to-end coverage targets.",
    "verify": "coverage report reaches target and critical paths have passing unit, integration, and e2e tests",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/ruvnet/claude-flow/blob/main/.agents/skills/agent-code-goal-planner/SKILL.md",
    "source_name": "claude-flow code-goal-planner skill",
    "source_type": "tool-readme",
    "evidence": "goal: achieve_80_percent_coverage",
    "evidence_summary": "goal: achieve_80_percent_coverage; source: claude-flow code-goal-planner skill; type: tool-readme; verification: coverage report reaches target and critical paths have passing unit, integration, and e2e tests",
    "prompt": "/goal\nGOAL:\nComplete GOAP Coverage Target Plan for a project with failing or missing verification gates: Raise test coverage with an explicit test pyramid across unit, integration, and end-to-end coverage targets.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `coverage report reaches target and critical paths have passing unit, integration, and e2e tests`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Raise test coverage with an explicit test pyramid across unit, integration, and end-to-end coverage targets.\n- The verification command or evidence path succeeds: `coverage report reaches target and critical paths have passing unit, integration, and e2e tests`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `coverage report reaches target and critical paths have passing unit, integration, and e2e tests` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-flow-coverage-goap.html"
  },
  {
    "id": "claude-recipes-okr-development",
    "slug": "claude-recipes-okr-development",
    "category": "product",
    "title": "OKR Development From Vague Priorities",
    "intent": "Turn vague strategic priorities into measurable OKRs with objectives, key results, alignment, scoring, guardrails, and a communication summary.",
    "verify": "3-5 objectives, 2-4 measurable key results each, alignment notes, scoring guide, red flags, one-page summary",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/sgharlow/claude-code-recipes/blob/main/recipes/Recipe-017-OKR-Goal-Setting.md",
    "source_name": "claude-code-recipes",
    "source_type": "third-party-tutorial",
    "evidence": "PRIMARY PROMPT: OKR Development",
    "evidence_summary": "PRIMARY PROMPT: OKR Development; source: claude-code-recipes; type: third-party-tutorial; verification: 3-5 objectives, 2-4 measurable key results each, alignment notes, scoring guide, red flags, one-page summary",
    "prompt": "/goal\nGOAL:\nComplete OKR Development From Vague Priorities for a product planning and implementation repo: Turn vague strategic priorities into measurable OKRs with objectives, key results, alignment, scoring, guardrails, and a communication summary.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect PRDs, analytics events, permission models, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `3-5 objectives, 2-4 measurable key results each, alignment notes, scoring guide, red flags, one-page summary`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not implement new product scope unless it is in the stated acceptance criteria.\n- Separate product decisions from engineering assumptions.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Turn vague strategic priorities into measurable OKRs with objectives, key results, alignment, scoring, guardrails, and a communication summary.\n- The verification command or evidence path succeeds: `3-5 objectives, 2-4 measurable key results each, alignment notes, scoring guide, red flags, one-page summary`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `3-5 objectives, 2-4 measurable key results each, alignment notes, scoring guide, red flags, one-page summary` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/claude-recipes-okr-development.html"
  },
  {
    "id": "clinical-research-ai-safety-boundary",
    "slug": "clinical-research-ai-safety-boundary",
    "category": "research",
    "title": "Clinical Research AI Safety Boundary",
    "intent": "Review clinical research AI work with evidence-first boundaries so agents do not invent medical sources, expose private data, or turn research notes into patient-specific advice.",
    "verify": "manual review checklist for source facts, uncertainty, safety note, inspected files, and human-review needs",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/2023Anita/clinical-ai-agent-skills",
    "source_name": "Clinical AI Agent Skills README",
    "source_type": "tool-readme",
    "evidence": "Evidence Before Confidence",
    "evidence_summary": "Evidence Before Confidence; source: Clinical AI Agent Skills README; type: tool-readme; verification: manual review checklist for source facts, uncertainty, safety note, inspected files, and human-review needs",
    "prompt": "/goal\nGOAL:\nComplete Clinical Research AI Safety Boundary for a research task: Review clinical research AI work with evidence-first boundaries so agents do not invent medical sources, expose private data, or turn research notes into patient-specific advice.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `manual review checklist for source facts, uncertainty, safety note, inspected files, and human-review needs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Review clinical research AI work with evidence-first boundaries so agents do not invent medical sources, expose private data, or turn research notes into patient-specific advice.\n- The verification command or evidence path succeeds: `manual review checklist for source facts, uncertainty, safety note, inspected files, and human-review needs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `manual review checklist for source facts, uncertainty, safety note, inspected files, and human-review needs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/clinical-research-ai-safety-boundary.html"
  },
  {
    "id": "openai-code-migration-checkpoints",
    "slug": "openai-code-migration-checkpoints",
    "category": "migration",
    "title": "Code Migration Checkpoints",
    "intent": "Inventory legacy assumptions, map them to a target stack, and execute the migration through validated checkpoints.",
    "verify": "legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/code-migrations",
    "source_name": "OpenAI Codex code migrations use case",
    "source_type": "official-agent-task",
    "evidence": "Migrate this codebase from [legacy stack or system] to [target stack or system]",
    "evidence_summary": "Migrate this codebase from [legacy stack or system] to [target stack or system]; source: OpenAI Codex code migrations use case; type: official-agent-task; verification: legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes",
    "prompt": "/goal\nGOAL:\nComplete Code Migration Checkpoints for a migration project: Inventory legacy assumptions, map them to a target stack, and execute the migration through validated checkpoints.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect legacy code, target implementation, compatibility tests, visual snapshots, and migration notes.\n- Establish a baseline by running or locating evidence for: `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Preserve existing user-visible behavior unless the goal explicitly names a behavior change.\n- Keep compatibility evidence for the old and new paths until the migration is verified.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Inventory legacy assumptions, map them to a target stack, and execute the migration through validated checkpoints.\n- The verification command or evidence path succeeds: `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `legacy assumption inventory, checkpoint migration plan, lint, type-check, focused tests after each milestone, rollback notes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-code-migration-checkpoints.html"
  },
  {
    "id": "openai-difficult-task-eval-loop",
    "slug": "openai-difficult-task-eval-loop",
    "category": "prompt-optimization",
    "title": "Difficult Task Eval Loop",
    "intent": "Run a difficult task as an eval-driven improvement loop with one focused change, rerun scores, and direct artifact inspection each iteration.",
    "verify": "score command found, per-iteration score log, artifact inspection, overall score and LLM average above target",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/iterate-on-difficult-problems",
    "source_name": "OpenAI Codex difficult problems use case",
    "source_type": "official-agent-task",
    "evidence": "run it as an eval-driven improvement loop",
    "evidence_summary": "run it as an eval-driven improvement loop; source: OpenAI Codex difficult problems use case; type: official-agent-task; verification: score command found, per-iteration score log, artifact inspection, overall score and LLM average above target",
    "prompt": "/goal\nGOAL:\nComplete Difficult Task Eval Loop for an eval-backed prompt project: Run a difficult task as an eval-driven improvement loop with one focused change, rerun scores, and direct artifact inspection each iteration.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompt files, eval cases, scoring reports, regressions, and failure examples.\n- Establish a baseline by running or locating evidence for: `score command found, per-iteration score log, artifact inspection, overall score and LLM average above target`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete, weaken, or cherry-pick eval cases to improve the score.\n- Report representative failures as well as the final score.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a difficult task as an eval-driven improvement loop with one focused change, rerun scores, and direct artifact inspection each iteration.\n- The verification command or evidence path succeeds: `score command found, per-iteration score log, artifact inspection, overall score and LLM average above target`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `score command found, per-iteration score log, artifact inspection, overall score and LLM average above target` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-difficult-task-eval-loop.html"
  },
  {
    "id": "openai-promptfoo-eval-suite",
    "slug": "openai-promptfoo-eval-suite",
    "category": "ai-evals",
    "title": "Promptfoo Eval Suite",
    "intent": "Add a runnable Promptfoo eval suite for an AI application before changing production prompts or model behavior.",
    "verify": "target adapter, seed cases, assertions, files, env requirements, local eval command, passing and failing cases",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/ai-app-evals",
    "source_name": "OpenAI Codex AI app evals use case",
    "source_type": "official-agent-task",
    "evidence": "Use $promptfoo-evals to add a Promptfoo eval suite",
    "evidence_summary": "Use $promptfoo-evals to add a Promptfoo eval suite; source: OpenAI Codex AI app evals use case; type: official-agent-task; verification: target adapter, seed cases, assertions, files, env requirements, local eval command, passing and failing cases",
    "prompt": "/goal\nGOAL:\nComplete Promptfoo Eval Suite for an AI evaluation project: Add a runnable Promptfoo eval suite for an AI application before changing production prompts or model behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect eval datasets, rubrics, model outputs, judge code, and regression reports.\n- Establish a baseline by running or locating evidence for: `target adapter, seed cases, assertions, files, env requirements, local eval command, passing and failing cases`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not tune prompts against hidden labels or delete failing eval cases to improve the score.\n- Keep before/after eval evidence and representative failures.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add a runnable Promptfoo eval suite for an AI application before changing production prompts or model behavior.\n- The verification command or evidence path succeeds: `target adapter, seed cases, assertions, files, env requirements, local eval command, passing and failing cases`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `target adapter, seed cases, assertions, files, env requirements, local eval command, passing and failing cases` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-promptfoo-eval-suite.html"
  },
  {
    "id": "openai-expo-react-native-app",
    "slug": "openai-expo-react-native-app",
    "category": "mobile",
    "title": "Expo React Native App Slice",
    "intent": "Build a working React Native app slice with Expo Router conventions, Expo-compatible packages, and native-feeling UI states.",
    "verify": "working app slice, run command, verification path with Expo Go, device, simulator, dev client, or EAS",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/react-native-expo-apps",
    "source_name": "OpenAI Codex Expo app use case",
    "source_type": "official-agent-task",
    "evidence": "Use the Expo plugin to build a React Native app with Expo",
    "evidence_summary": "Use the Expo plugin to build a React Native app with Expo; source: OpenAI Codex Expo app use case; type: official-agent-task; verification: working app slice, run command, verification path with Expo Go, device, simulator, dev client, or EAS",
    "prompt": "/goal\nGOAL:\nComplete Expo React Native App Slice for a mobile or responsive application: Build a working React Native app slice with Expo Router conventions, Expo-compatible packages, and native-feeling UI states.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect mobile routes, forms, gestures, device matrix, and viewport tests.\n- Establish a baseline by running or locating evidence for: `working app slice, run command, verification path with Expo Go, device, simulator, dev client, or EAS`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not optimize only desktop behavior.\n- Keep touch targets, safe areas, and keyboard overlap in scope.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Build a working React Native app slice with Expo Router conventions, Expo-compatible packages, and native-feeling UI states.\n- The verification command or evidence path succeeds: `working app slice, run command, verification path with Expo Go, device, simulator, dev client, or EAS`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `working app slice, run command, verification path with Expo Go, device, simulator, dev client, or EAS` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-expo-react-native-app.html"
  },
  {
    "id": "openai-agent-friendly-cli-skill",
    "slug": "openai-agent-friendly-cli-skill",
    "category": "cli",
    "title": "Agent-Friendly CLI And Skill",
    "intent": "Create a composable CLI and companion skill so future agent tasks can search, read, download, or draft against a recurring source safely.",
    "verify": "proposed command surface, command installed on PATH, help output, setup check, safe discovery command, exact read command, companion skill",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://developers.openai.com/codex/use-cases/agent-friendly-clis",
    "source_name": "OpenAI Codex agent-friendly CLI use case",
    "source_type": "official-agent-task",
    "evidence": "Use $cli-creator to create a CLI you can use, and use $skill-creator to create the companion skill",
    "evidence_summary": "Use $cli-creator to create a CLI you can use, and use $skill-creator to create the companion skill; source: OpenAI Codex agent-friendly CLI use case; type: official-agent-task; verification: proposed command surface, command installed on PATH, help output, setup check, safe discovery command, exact read command, companion skill",
    "prompt": "/goal\nGOAL:\nComplete Agent-Friendly CLI And Skill for a command-line tool: Create a composable CLI and companion skill so future agent tasks can search, read, download, or draft against a recurring source safely.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect CLI entrypoints, argument parsing, filesystem behavior, dry-run mode, and fixtures.\n- Establish a baseline by running or locating evidence for: `proposed command surface, command installed on PATH, help output, setup check, safe discovery command, exact read command, companion skill`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not perform destructive filesystem operations without a dry-run or explicit confirmation.\n- Keep command output deterministic enough for tests.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create a composable CLI and companion skill so future agent tasks can search, read, download, or draft against a recurring source safely.\n- The verification command or evidence path succeeds: `proposed command surface, command installed on PATH, help output, setup check, safe discovery command, exact read command, companion skill`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `proposed command surface, command installed on PATH, help output, setup check, safe discovery command, exact read command, companion skill` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-agent-friendly-cli-skill.html"
  },
  {
    "id": "openai-define-goal-quality-bar",
    "slug": "openai-define-goal-quality-bar",
    "category": "goal-maintenance",
    "title": "Define Goal Quality Bar",
    "intent": "Turn a fuzzy intention into a concrete measurable goal with evidence, scope boundaries, and honest stop conditions before creating it.",
    "verify": "objective names outcome, evidence, success threshold, scope boundaries, and stop condition before create_goal",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/openai/skills/blob/main/skills/.curated/define-goal/SKILL.md",
    "source_name": "OpenAI define-goal skill",
    "source_type": "tool-readme",
    "evidence": "Before create_goal, the objective should answer",
    "evidence_summary": "Before create_goal, the objective should answer; source: OpenAI define-goal skill; type: tool-readme; verification: objective names outcome, evidence, success threshold, scope boundaries, and stop condition before create_goal",
    "prompt": "/goal\nGOAL:\nComplete Define Goal Quality Bar for a goal-management workflow: Turn a fuzzy intention into a concrete measurable goal with evidence, scope boundaries, and honest stop conditions before creating it.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `objective names outcome, evidence, success threshold, scope boundaries, and stop condition before create_goal`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Turn a fuzzy intention into a concrete measurable goal with evidence, scope boundaries, and honest stop conditions before creating it.\n- The verification command or evidence path succeeds: `objective names outcome, evidence, success threshold, scope boundaries, and stop condition before create_goal`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `objective names outcome, evidence, success threshold, scope boundaries, and stop condition before create_goal` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/openai-define-goal-quality-bar.html"
  },
  {
    "id": "x-three-questions-goal-framework",
    "slug": "x-three-questions-goal-framework",
    "category": "workflow",
    "title": "Three Questions Goal Framework",
    "intent": "Write higher quality goals by explicitly answering three core questions: what needs to be done, how success will be measured, and what is off-limits.",
    "verify": "goal explicitly addresses what to do, how it will be verified as done, and clear boundaries",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/aashatwt/status/2054810622131585515",
    "source_name": "@aashatwt on X",
    "source_type": "x-post",
    "evidence": "A good /goal prompt answers these three questions: What needs to be done? How will we know it's done? What's off-limits?",
    "evidence_summary": "A good /goal prompt answers these three questions: What needs to be done? How will we know it's done? What's off-limits?; source: @aashatwt on X; type: x-post; verification: goal explicitly addresses what to do, how it will be verified as done, and clear boundaries",
    "prompt": "/goal\nGOAL:\nComplete Three Questions Goal Framework for a coding-agent workflow repository: Write higher quality goals by explicitly answering three core questions: what needs to be done, how success will be measured, and what is off-limits.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `goal explicitly addresses what to do, how it will be verified as done, and clear boundaries`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write higher quality goals by explicitly answering three core questions: what needs to be done, how success will be measured, and what is off-limits.\n- The verification command or evidence path succeeds: `goal explicitly addresses what to do, how it will be verified as done, and clear boundaries`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `goal explicitly addresses what to do, how it will be verified as done, and clear boundaries` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-three-questions-goal-framework.html"
  },
  {
    "id": "x-explicit-stop-rules-goal-loops",
    "slug": "x-explicit-stop-rules-goal-loops",
    "category": "workflow",
    "title": "Explicit Stop Rules for Goal Loops",
    "intent": "Prevent infinite loops, cost overruns, and unsafe behavior in autonomous /goal executions by defining clear, explicit stop conditions and escalation rules.",
    "verify": "goal prompt contains a dedicated STOP RULES section with concrete halt conditions (turns, cost, repeated failures, risk triggers)",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/_avichawla/status/2055930732930122158",
    "source_name": "@_avichawla on X",
    "source_type": "x-post",
    "evidence": "Without strong stop rules a slightly wrong condition loops forever",
    "evidence_summary": "Without strong stop rules a slightly wrong condition loops forever; source: @_avichawla on X; type: x-post; verification: goal prompt contains a dedicated STOP RULES section with concrete halt conditions (turns, cost, repeated failures, risk triggers)",
    "prompt": "/goal\nGOAL:\nComplete Explicit Stop Rules for Goal Loops for a coding-agent workflow repository: Prevent infinite loops, cost overruns, and unsafe behavior in autonomous /goal executions by defining clear, explicit stop conditions and escalation rules.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `goal prompt contains a dedicated STOP RULES section with concrete halt conditions (turns, cost, repeated failures, risk triggers)`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Prevent infinite loops, cost overruns, and unsafe behavior in autonomous /goal executions by defining clear, explicit stop conditions and escalation rules.\n- The verification command or evidence path succeeds: `goal prompt contains a dedicated STOP RULES section with concrete halt conditions (turns, cost, repeated failures, risk triggers)`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `goal prompt contains a dedicated STOP RULES section with concrete halt conditions (turns, cost, repeated failures, risk triggers)` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-explicit-stop-rules-goal-loops.html"
  },
  {
    "id": "x-dual-model-evaluator-goal-loop",
    "slug": "x-dual-model-evaluator-goal-loop",
    "category": "workflow",
    "title": "Dual-Model Evaluator Loop for Goals",
    "intent": "Run long /goal sessions reliably and cost-effectively by using a strong worker model for execution paired with a cheap fast evaluator model (typically Haiku) that periodically judges progress against the goal criteria and decides whether to continue or stop.",
    "verify": "goal execution uses distinct worker and evaluator models with the evaluator checking against explicit DONE WHEN conditions",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/_avichawla/status/2055930732930122158",
    "source_name": "@_avichawla on X",
    "source_type": "x-post",
    "evidence": "worker model + cheap Haiku evaluator loop for goal completion decisions",
    "evidence_summary": "worker model + cheap Haiku evaluator loop for goal completion decisions; source: @_avichawla on X; type: x-post; verification: goal execution uses distinct worker and evaluator models with the evaluator checking against explicit DONE WHEN conditions",
    "prompt": "/goal\nGOAL:\nComplete Dual-Model Evaluator Loop for Goals for a coding-agent workflow repository: Run long /goal sessions reliably and cost-effectively by using a strong worker model for execution paired with a cheap fast evaluator model (typically Haiku) that periodically judges progress against the goal criteria and decides whether to continue or stop.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `goal execution uses distinct worker and evaluator models with the evaluator checking against explicit DONE WHEN conditions`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run long /goal sessions reliably and cost-effectively by using a strong worker model for execution paired with a cheap fast evaluator model (typically Haiku) that periodically judges progress against the goal criteria and decides whether to continue or stop.\n- The verification command or evidence path succeeds: `goal execution uses distinct worker and evaluator models with the evaluator checking against explicit DONE WHEN conditions`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `goal execution uses distinct worker and evaluator models with the evaluator checking against explicit DONE WHEN conditions` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-dual-model-evaluator-goal-loop.html"
  },
  {
    "id": "x-claude-md-goal-workflow",
    "slug": "x-claude-md-goal-workflow",
    "category": "workflow",
    "title": "CLAUDE.md + Goal Workflow",
    "intent": "Combine a persistent project-level CLAUDE.md (or AGENTS.md) file containing rules, standards, and context with /goal commands so long-running autonomous agent work stays aligned with repository-specific constraints and learned lessons.",
    "verify": "CLAUDE.md is present and referenced; /goal executions respect the documented rules and patterns",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/nateherk/status/2059377638896971985",
    "source_name": "@nateherk on X",
    "source_type": "x-post",
    "evidence": "CLAUDE.md as persistent context paired with /goal for autonomous execution",
    "evidence_summary": "CLAUDE.md as persistent context paired with /goal for autonomous execution; source: @nateherk on X; type: x-post; verification: CLAUDE.md is present and referenced; /goal executions respect the documented rules and patterns",
    "prompt": "/goal\nGOAL:\nComplete CLAUDE.md + Goal Workflow for a coding-agent workflow repository: Combine a persistent project-level CLAUDE.md (or AGENTS.md) file containing rules, standards, and context with /goal commands so long-running autonomous agent work stays aligned with repository-specific constraints and learned lessons.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `CLAUDE.md is present and referenced; /goal executions respect the documented rules and patterns`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Combine a persistent project-level CLAUDE.md (or AGENTS.md) file containing rules, standards, and context with /goal commands so long-running autonomous agent work stays aligned with repository-specific constraints and learned lessons.\n- The verification command or evidence path succeeds: `CLAUDE.md is present and referenced; /goal executions respect the documented rules and patterns`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `CLAUDE.md is present and referenced; /goal executions respect the documented rules and patterns` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-claude-md-goal-workflow.html"
  },
  {
    "id": "x-goal-ledger",
    "slug": "x-goal-ledger",
    "category": "workflow",
    "title": "Goal Ledger for Long-Running Runs",
    "intent": "Maintain a live, browser-viewable HTML progress ledger during extended /goal executions to provide visibility, persistent memory, decision logging, and self-reflection, reducing drift in long autonomous sessions.",
    "verify": "an updatable HTML ledger file is created and actively maintained by the agent throughout the goal run",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://x.com/KingBootoshi/status/2056876283204866293",
    "source_name": "@KingBootoshi on X",
    "source_type": "x-post",
    "evidence": "single-file HTML progress tracker and ledger for /goal runs",
    "evidence_summary": "single-file HTML progress tracker and ledger for /goal runs; source: @KingBootoshi on X; type: x-post; verification: an updatable HTML ledger file is created and actively maintained by the agent throughout the goal run",
    "prompt": "/goal\nGOAL:\nComplete Goal Ledger for Long-Running Runs for a coding-agent workflow repository: Maintain a live, browser-viewable HTML progress ledger during extended /goal executions to provide visibility, persistent memory, decision logging, and self-reflection, reducing drift in long autonomous sessions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `an updatable HTML ledger file is created and actively maintained by the agent throughout the goal run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Maintain a live, browser-viewable HTML progress ledger during extended /goal executions to provide visibility, persistent memory, decision logging, and self-reflection, reducing drift in long autonomous sessions.\n- The verification command or evidence path succeeds: `an updatable HTML ledger file is created and actively maintained by the agent throughout the goal run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `an updatable HTML ledger file is created and actively maintained by the agent throughout the goal run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/x-goal-ledger.html"
  },
  {
    "id": "github-supergoal-artifact-backed-phase-runner",
    "slug": "github-supergoal-artifact-backed-phase-runner",
    "category": "workflow",
    "title": "Artifact-Backed Phase Runner",
    "intent": "Run a long-horizon task from one short /goal by storing the roadmap, state, protocol, and phase specs on disk, then auditing final deliverables against the original plan.",
    "verify": "test -f .supergoal/ROADMAP.md && test -f .supergoal/STATE.md && test -f .supergoal/PROTOCOL.md && find .supergoal/phases -name \"phase-*.md\" -print -quit | grep -q . && grep -R -E \"SUPERGOAL_PHASE_DONE|AUDIT_COMPLETE\" .supergoal",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/robzilla1738/supergoal",
    "source_name": "supergoal README",
    "source_type": "tool-readme",
    "evidence": "one /goal covers the whole run; phase work lives in files the agent reads from disk",
    "evidence_summary": "one /goal covers the whole run; phase work lives in files the agent reads from disk; source: supergoal README; type: tool-readme; verification: test -f .supergoal/ROADMAP.md && test -f .supergoal/STATE.md && test -f .supergoal/PROTOCOL.md && find .supergoal/phases -name \"phase-*.md\" -print -quit | grep -q . && grep -R -E \"SUPERGOAL_PHASE_DONE|AUDIT_COMPLETE\" .supergoal",
    "prompt": "/goal\nGOAL:\nComplete Artifact-Backed Phase Runner for a coding-agent workflow repository: Run a long-horizon task from one short /goal by storing the roadmap, state, protocol, and phase specs on disk, then auditing final deliverables against the original plan.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `test -f .supergoal/ROADMAP.md && test -f .supergoal/STATE.md && test -f .supergoal/PROTOCOL.md && find .supergoal/phases -name \"phase-*.md\" -print -quit | grep -q . && grep -R -E \"SUPERGOAL_PHASE_DONE|AUDIT_COMPLETE\" .supergoal`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a long-horizon task from one short /goal by storing the roadmap, state, protocol, and phase specs on disk, then auditing final deliverables against the original plan.\n- The verification command or evidence path succeeds: `test -f .supergoal/ROADMAP.md && test -f .supergoal/STATE.md && test -f .supergoal/PROTOCOL.md && find .supergoal/phases -name \"phase-*.md\" -print -quit | grep -q . && grep -R -E \"SUPERGOAL_PHASE_DONE|AUDIT_COMPLETE\" .supergoal`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `test -f .supergoal/ROADMAP.md && test -f .supergoal/STATE.md && test -f .supergoal/PROTOCOL.md && find .supergoal/phases -name \"phase-*.md\" -print -quit | grep -q . && grep -R -E \"SUPERGOAL_PHASE_DONE|AUDIT_COMPLETE\" .supergoal` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-supergoal-artifact-backed-phase-runner.html"
  },
  {
    "id": "goal-builder-audit-friendly-template",
    "slug": "goal-builder-audit-friendly-template",
    "category": "goal-maintenance",
    "title": "Audit-Friendly Goal Template",
    "intent": "Rewrite a vague /goal into a mappable contract with objective, scope, constraints, done-when evidence, stop rules, and token budget.",
    "verify": "audit-friendliness score, rendered /goal, Objective/Scope/Constraints/Done when/Stop if sections",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://github.com/win4r/goal-prompt-builder",
    "source_name": "goal-prompt-builder README",
    "source_type": "tool-readme",
    "evidence": "5-section golden template (Objective / Scope / Constraints / Done when / Stop if)",
    "evidence_summary": "5-section golden template (Objective / Scope / Constraints / Done when / Stop if); source: goal-prompt-builder README; type: tool-readme; verification: audit-friendliness score, rendered /goal, Objective/Scope/Constraints/Done when/Stop if sections",
    "prompt": "/goal\nGOAL:\nComplete Audit-Friendly Goal Template for a goal-management workflow: Rewrite a vague /goal into a mappable contract with objective, scope, constraints, done-when evidence, stop rules, and token budget.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `audit-friendliness score, rendered /goal, Objective/Scope/Constraints/Done when/Stop if sections`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Rewrite a vague /goal into a mappable contract with objective, scope, constraints, done-when evidence, stop rules, and token budget.\n- The verification command or evidence path succeeds: `audit-friendliness score, rendered /goal, Objective/Scope/Constraints/Done when/Stop if sections`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `audit-friendliness score, rendered /goal, Objective/Scope/Constraints/Done when/Stop if sections` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-builder-audit-friendly-template.html"
  },
  {
    "id": "goal-builder-openspec-rerank-provider",
    "slug": "goal-builder-openspec-rerank-provider",
    "category": "ai-ops",
    "title": "OpenSpec Rerank Provider Goal",
    "intent": "Implement an OpenSpec feature change exactly as specified, adding a new rerank provider with contract tests, integration coverage, docs, and changelog evidence.",
    "verify": "tasks checked off with file evidence, SHALL tests, GIVEN/WHEN/THEN integration tests, npx tsc --noEmit, npm test, README and CHANGELOG updates",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://github.com/win4r/goal-prompt-builder",
    "source_name": "goal-prompt-builder README",
    "source_type": "tool-readme",
    "evidence": "Implement openspec/changes/add-cohere-rerank/ exactly as specified",
    "evidence_summary": "Implement openspec/changes/add-cohere-rerank/ exactly as specified; source: goal-prompt-builder README; type: tool-readme; verification: tasks checked off with file evidence, SHALL tests, GIVEN/WHEN/THEN integration tests, npx tsc --noEmit, npm test, README and CHANGELOG updates",
    "prompt": "/goal\nGOAL:\nComplete OpenSpec Rerank Provider Goal for an AI application runtime: Implement an OpenSpec feature change exactly as specified, adding a new rerank provider with contract tests, integration coverage, docs, and changelog evidence.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompts, retrieval code, routing policies, tracing, and cost logs.\n- Establish a baseline by running or locating evidence for: `tasks checked off with file evidence, SHALL tests, GIVEN/WHEN/THEN integration tests, npx tsc --noEmit, npm test, README and CHANGELOG updates`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not silently fall back to a lower-quality model for user-visible critical paths.\n- Keep request IDs, cost evidence, and schema validation errors visible.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Implement an OpenSpec feature change exactly as specified, adding a new rerank provider with contract tests, integration coverage, docs, and changelog evidence.\n- The verification command or evidence path succeeds: `tasks checked off with file evidence, SHALL tests, GIVEN/WHEN/THEN integration tests, npx tsc --noEmit, npm test, README and CHANGELOG updates`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `tasks checked off with file evidence, SHALL tests, GIVEN/WHEN/THEN integration tests, npx tsc --noEmit, npm test, README and CHANGELOG updates` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-builder-openspec-rerank-provider.html"
  },
  {
    "id": "github-copilot-well-scoped-agent-issue",
    "slug": "github-copilot-well-scoped-agent-issue",
    "category": "workflow",
    "title": "Well-Scoped Agent Issue",
    "intent": "Turn a backlog item into a coding-agent-ready issue with a clear problem statement, acceptance criteria, file directions, and test expectations.",
    "verify": "issue includes problem description, acceptance criteria, file hints, expected tests, and review notes",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/cloud-agent/get-the-best-results",
    "source_name": "GitHub Copilot cloud agent best practices",
    "source_type": "official-agent-task",
    "evidence": "clear description of the problem to be solved or the work required",
    "evidence_summary": "clear description of the problem to be solved or the work required; source: GitHub Copilot cloud agent best practices; type: official-agent-task; verification: issue includes problem description, acceptance criteria, file hints, expected tests, and review notes",
    "prompt": "/goal\nGOAL:\nComplete Well-Scoped Agent Issue for a coding-agent workflow repository: Turn a backlog item into a coding-agent-ready issue with a clear problem statement, acceptance criteria, file directions, and test expectations.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `issue includes problem description, acceptance criteria, file hints, expected tests, and review notes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Turn a backlog item into a coding-agent-ready issue with a clear problem statement, acceptance criteria, file directions, and test expectations.\n- The verification command or evidence path succeeds: `issue includes problem description, acceptance criteria, file hints, expected tests, and review notes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `issue includes problem description, acceptance criteria, file hints, expected tests, and review notes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-well-scoped-agent-issue.html"
  },
  {
    "id": "github-copilot-plan-before-pr",
    "slug": "github-copilot-plan-before-pr",
    "category": "workflow",
    "title": "Research And Plan Before PR",
    "intent": "Have an agent research the repository, create an implementation plan, and iterate on a branch before deciding whether to open a pull request.",
    "verify": "implementation plan, reviewed diff, branch commits, explicit PR-open decision, and remaining-risk notes",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/cloud-agent/get-the-best-results",
    "source_name": "GitHub Copilot cloud agent best practices",
    "source_type": "official-agent-task",
    "evidence": "research a repository, create an implementation plan, and make iterative code changes on a branch first",
    "evidence_summary": "research a repository, create an implementation plan, and make iterative code changes on a branch first; source: GitHub Copilot cloud agent best practices; type: official-agent-task; verification: implementation plan, reviewed diff, branch commits, explicit PR-open decision, and remaining-risk notes",
    "prompt": "/goal\nGOAL:\nComplete Research And Plan Before PR for a coding-agent workflow repository: Have an agent research the repository, create an implementation plan, and iterate on a branch before deciding whether to open a pull request.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `implementation plan, reviewed diff, branch commits, explicit PR-open decision, and remaining-risk notes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Have an agent research the repository, create an implementation plan, and iterate on a branch before deciding whether to open a pull request.\n- The verification command or evidence path succeeds: `implementation plan, reviewed diff, branch commits, explicit PR-open decision, and remaining-risk notes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `implementation plan, reviewed diff, branch commits, explicit PR-open decision, and remaining-risk notes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-plan-before-pr.html"
  },
  {
    "id": "github-copilot-repository-instructions",
    "slug": "github-copilot-repository-instructions",
    "category": "docs",
    "title": "Repository Agent Instructions",
    "intent": "Add repository-level agent instructions that document project structure, build/test/validate commands, coding standards, and documentation expectations.",
    "verify": ".github/copilot-instructions.md or AGENTS.md present, commands verified, repository structure covered, standards documented",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/cloud-agent/get-the-best-results",
    "source_name": "GitHub Copilot cloud agent best practices",
    "source_type": "official-agent-task",
    "evidence": "guide Copilot on how to understand your project and how to build, test and validate its changes",
    "evidence_summary": "guide Copilot on how to understand your project and how to build, test and validate its changes; source: GitHub Copilot cloud agent best practices; type: official-agent-task; verification: .github/copilot-instructions.md or AGENTS.md present, commands verified, repository structure covered, standards documented",
    "prompt": "/goal\nGOAL:\nComplete Repository Agent Instructions for a developer-facing documentation site or repository: Add repository-level agent instructions that document project structure, build/test/validate commands, coding standards, and documentation expectations.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `.github/copilot-instructions.md or AGENTS.md present, commands verified, repository structure covered, standards documented`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Add repository-level agent instructions that document project structure, build/test/validate commands, coding standards, and documentation expectations.\n- The verification command or evidence path succeeds: `.github/copilot-instructions.md or AGENTS.md present, commands verified, repository structure covered, standards documented`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `.github/copilot-instructions.md or AGENTS.md present, commands verified, repository structure covered, standards documented` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-repository-instructions.html"
  },
  {
    "id": "github-copilot-playwright-instructions",
    "slug": "github-copilot-playwright-instructions",
    "category": "testing",
    "title": "Playwright Test Instructions",
    "intent": "Create path-specific Playwright instructions that enforce stable locators, isolated tests, explicit assertions, cross-browser coverage, and CI behavior.",
    "verify": ".github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/cloud-agent/get-the-best-results",
    "source_name": "GitHub Copilot cloud agent best practices",
    "source_type": "official-agent-task",
    "evidence": "Use stable locators",
    "evidence_summary": "Use stable locators; source: GitHub Copilot cloud agent best practices; type: official-agent-task; verification: .github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command",
    "prompt": "/goal\nGOAL:\nComplete Playwright Test Instructions for a project with failing or missing verification gates: Create path-specific Playwright instructions that enforce stable locators, isolated tests, explicit assertions, cross-browser coverage, and CI behavior.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Create path-specific Playwright instructions that enforce stable locators, isolated tests, explicit assertions, cross-browser coverage, and CI behavior.\n- The verification command or evidence path succeeds: `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `.github/instructions/playwright-tests.instructions.md with glob front matter, sample e2e test, and passing Playwright command` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-playwright-instructions.html"
  },
  {
    "id": "github-copilot-autopilot-ci-repair",
    "slug": "github-copilot-autopilot-ci-repair",
    "category": "devops-ci",
    "title": "Bounded Autopilot CI Repair",
    "intent": "Run a bounded autonomous CI repair after plan acceptance, with explicit continuation limits, permissions, validation commands, and blocker reporting.",
    "verify": "accepted plan, max continuation limit, CI command outputs, final green run or blocker report",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/concepts/agents/copilot-cli/autopilot",
    "source_name": "GitHub Copilot CLI autopilot docs",
    "source_type": "official-workflow",
    "evidence": "Accept plan and build on autopilot",
    "evidence_summary": "Accept plan and build on autopilot; source: GitHub Copilot CLI autopilot docs; type: official-workflow; verification: accepted plan, max continuation limit, CI command outputs, final green run or blocker report",
    "prompt": "/goal\nGOAL:\nComplete Bounded Autopilot CI Repair for a repository with CI/CD automation: Run a bounded autonomous CI repair after plan acceptance, with explicit continuation limits, permissions, validation commands, and blocker reporting.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect workflow files, build scripts, package manifests, and recent CI logs.\n- Establish a baseline by running or locating evidence for: `accepted plan, max continuation limit, CI command outputs, final green run or blocker report`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken tests, remove required checks, or bypass branch protection.\n- Keep workflow permissions as narrow as the task allows.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a bounded autonomous CI repair after plan acceptance, with explicit continuation limits, permissions, validation commands, and blocker reporting.\n- The verification command or evidence path succeeds: `accepted plan, max continuation limit, CI command outputs, final green run or blocker report`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `accepted plan, max continuation limit, CI command outputs, final green run or blocker report` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-autopilot-ci-repair.html"
  },
  {
    "id": "github-copilot-fleet-parallel-test-suite",
    "slug": "github-copilot-fleet-parallel-test-suite",
    "category": "orchestration",
    "title": "Fleet Parallel Test Suite",
    "intent": "Break a large test expansion into independent subtasks that subagents can execute in parallel while the orchestrator manages dependencies and final integration.",
    "verify": "task split, subagent ownership, dependency notes, merged test output, and conflict audit",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/concepts/agents/copilot-cli/fleet",
    "source_name": "GitHub Copilot CLI fleet docs",
    "source_type": "official-workflow",
    "evidence": "creating a suite of tests for a new feature, are well suited to parallelization",
    "evidence_summary": "creating a suite of tests for a new feature, are well suited to parallelization; source: GitHub Copilot CLI fleet docs; type: official-workflow; verification: task split, subagent ownership, dependency notes, merged test output, and conflict audit",
    "prompt": "/goal\nGOAL:\nComplete Fleet Parallel Test Suite for an agent orchestration task: Break a large test expansion into independent subtasks that subagents can execute in parallel while the orchestrator manages dependencies and final integration.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect plans, worktrees, subtask ownership, PRs, and coordination notes.\n- Establish a baseline by running or locating evidence for: `task split, subagent ownership, dependency notes, merged test output, and conflict audit`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Keep subtask ownership explicit and avoid overlapping write scopes.\n- Do not merge or deploy automatically unless the goal explicitly allows it.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Break a large test expansion into independent subtasks that subagents can execute in parallel while the orchestrator manages dependencies and final integration.\n- The verification command or evidence path succeeds: `task split, subagent ownership, dependency notes, merged test output, and conflict audit`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `task split, subagent ownership, dependency notes, merged test output, and conflict audit` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-fleet-parallel-test-suite.html"
  },
  {
    "id": "github-copilot-research-architecture-report",
    "slug": "github-copilot-research-architecture-report",
    "category": "research",
    "title": "Cited Architecture Research Report",
    "intent": "Produce a saved, cited Markdown architecture report after inspecting the local codebase, relevant repositories, and web sources.",
    "verify": "Markdown report path or gist URL, citations, assumptions, confidence assessment, and architecture summary",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/concepts/agents/copilot-cli/research",
    "source_name": "GitHub Copilot CLI research docs",
    "source_type": "official-agent-task",
    "evidence": "/research What is the architecture of this codebase?",
    "evidence_summary": "/research What is the architecture of this codebase?; source: GitHub Copilot CLI research docs; type: official-agent-task; verification: Markdown report path or gist URL, citations, assumptions, confidence assessment, and architecture summary",
    "prompt": "/goal\nGOAL:\nComplete Cited Architecture Research Report for a research task: Produce a saved, cited Markdown architecture report after inspecting the local codebase, relevant repositories, and web sources.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `Markdown report path or gist URL, citations, assumptions, confidence assessment, and architecture summary`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Produce a saved, cited Markdown architecture report after inspecting the local codebase, relevant repositories, and web sources.\n- The verification command or evidence path succeeds: `Markdown report path or gist URL, citations, assumptions, confidence assessment, and architecture summary`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `Markdown report path or gist URL, citations, assumptions, confidence assessment, and architecture summary` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-research-architecture-report.html"
  },
  {
    "id": "github-copilot-cli-agentic-review",
    "slug": "github-copilot-cli-agentic-review",
    "category": "qa",
    "title": "Terminal Agentic Code Review",
    "intent": "Review a diff from the terminal with a scoped prompt, path, or file pattern, inspect suggested commands, and apply or reject findings before commit.",
    "verify": "/review output, inspected diff evidence, applied fixes or explicit rejects, and final clean diff summary",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli/agentic-code-review",
    "source_name": "GitHub Copilot CLI code review docs",
    "source_type": "official-agent-task",
    "evidence": "/review slash command to have Copilot analyze code changes",
    "evidence_summary": "/review slash command to have Copilot analyze code changes; source: GitHub Copilot CLI code review docs; type: official-agent-task; verification: /review output, inspected diff evidence, applied fixes or explicit rejects, and final clean diff summary",
    "prompt": "/goal\nGOAL:\nComplete Terminal Agentic Code Review for a product with automated and manual QA coverage: Review a diff from the terminal with a scoped prompt, path, or file pattern, inspect suggested commands, and apply or reject findings before commit.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, fixtures, bug templates, and release checklists.\n- Establish a baseline by running or locating evidence for: `/review output, inspected diff evidence, applied fixes or explicit rejects, and final clean diff summary`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete or weaken failing tests to make the suite pass.\n- Reproduce failures before changing production code.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Review a diff from the terminal with a scoped prompt, path, or file pattern, inspect suggested commands, and apply or reject findings before commit.\n- The verification command or evidence path succeeds: `/review output, inspected diff evidence, applied fixes or explicit rejects, and final clean diff summary`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `/review output, inspected diff evidence, applied fixes or explicit rejects, and final clean diff summary` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-cli-agentic-review.html"
  },
  {
    "id": "github-copilot-cross-cutting-logging",
    "slug": "github-copilot-cross-cutting-logging",
    "category": "refactor",
    "title": "Centralize Cross-Cutting Logging",
    "intent": "Centralize scattered logging, validation, security, or error-handling behavior without changing the core business behavior of the services.",
    "verify": "central middleware/decorator/config module, duplicate removal, focused regression tests, and unchanged public behavior",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/copilot-cookbook/refactor-code/handle-cross-cutting",
    "source_name": "GitHub Copilot Cookbook",
    "source_type": "official-agent-task",
    "evidence": "logging, security, data validation, and error handling",
    "evidence_summary": "logging, security, data validation, and error handling; source: GitHub Copilot Cookbook; type: official-agent-task; verification: central middleware/decorator/config module, duplicate removal, focused regression tests, and unchanged public behavior",
    "prompt": "/goal\nGOAL:\nComplete Centralize Cross-Cutting Logging for a refactoring task: Centralize scattered logging, validation, security, or error-handling behavior without changing the core business behavior of the services.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect the target module, call sites, public API, tests, and compatibility notes.\n- Establish a baseline by running or locating evidence for: `central middleware/decorator/config module, duplicate removal, focused regression tests, and unchanged public behavior`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not change public APIs, data formats, or user-visible behavior unless the goal requires it.\n- Keep behavior characterization tests before large internal changes.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Centralize scattered logging, validation, security, or error-handling behavior without changing the core business behavior of the services.\n- The verification command or evidence path succeeds: `central middleware/decorator/config module, duplicate removal, focused regression tests, and unchanged public behavior`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `central middleware/decorator/config module, duplicate removal, focused regression tests, and unchanged public behavior` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-cross-cutting-logging.html"
  },
  {
    "id": "github-copilot-deadlock-minimization",
    "slug": "github-copilot-deadlock-minimization",
    "category": "backend-data",
    "title": "Deadlock-Minimizing Transaction Rewrite",
    "intent": "Rewrite transaction ordering and locking to reduce deadlock risk without adverse performance or data-integrity regressions.",
    "verify": "consistent lock order, shorter transaction evidence, database tests, and before/after query or lock notes",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/copilot-cookbook/refactor-code/fix-database-deadlocks",
    "source_name": "GitHub Copilot Cookbook",
    "source_type": "official-agent-task",
    "evidence": "reduce the chance of deadlock to a minimum while not adversely affecting performance",
    "evidence_summary": "reduce the chance of deadlock to a minimum while not adversely affecting performance; source: GitHub Copilot Cookbook; type: official-agent-task; verification: consistent lock order, shorter transaction evidence, database tests, and before/after query or lock notes",
    "prompt": "/goal\nGOAL:\nComplete Deadlock-Minimizing Transaction Rewrite for a data-backed backend service: Rewrite transaction ordering and locking to reduce deadlock risk without adverse performance or data-integrity regressions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect schema files, migrations, models, repositories, and data tests.\n- Establish a baseline by running or locating evidence for: `consistent lock order, shorter transaction evidence, database tests, and before/after query or lock notes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence.\n- Do not hide database errors behind warnings or silent fallbacks.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Rewrite transaction ordering and locking to reduce deadlock risk without adverse performance or data-integrity regressions.\n- The verification command or evidence path succeeds: `consistent lock order, shorter transaction evidence, database tests, and before/after query or lock notes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `consistent lock order, shorter transaction evidence, database tests, and before/after query or lock notes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-deadlock-minimization.html"
  },
  {
    "id": "github-copilot-xss-innerhtml-fix",
    "slug": "github-copilot-xss-innerhtml-fix",
    "category": "security-appsec",
    "title": "Unsafe innerHTML XSS Fix",
    "intent": "Find and fix XSS caused by unsafe innerHTML rendering while preserving the user-visible text and adding a regression guard.",
    "verify": "unsafe sink replaced, security or DOM test added, no sanitizer bypass, and UI output preserved",
    "difficulty": "advanced",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/copilot-cookbook/analyze-security/find-vulnerabilities",
    "source_name": "GitHub Copilot Cookbook",
    "source_type": "official-agent-task",
    "evidence": "innerHTML = `Showing results for \"${name}\"`",
    "evidence_summary": "innerHTML = `Showing results for \"${name}\"`; source: GitHub Copilot Cookbook; type: official-agent-task; verification: unsafe sink replaced, security or DOM test added, no sanitizer bypass, and UI output preserved",
    "prompt": "/goal\nGOAL:\nComplete Unsafe innerHTML XSS Fix for an application with security-sensitive code paths: Find and fix XSS caused by unsafe innerHTML rendering while preserving the user-visible text and adding a regression guard.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect auth, input handling, rendering, upload, and boundary tests.\n- Establish a baseline by running or locating evidence for: `unsafe sink replaced, security or DOM test added, no sanitizer bypass, and UI output preserved`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not bypass authentication, authorization, validation, or audit checks.\n- Do not use eval, unsafe HTML injection, shell string concatenation, or string-built SQL.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Find and fix XSS caused by unsafe innerHTML rendering while preserving the user-visible text and adding a regression guard.\n- The verification command or evidence path succeeds: `unsafe sink replaced, security or DOM test added, no sanitizer bypass, and UI output preserved`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `unsafe sink replaced, security or DOM test added, no sanitizer bypass, and UI output preserved` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-xss-innerhtml-fix.html"
  },
  {
    "id": "github-copilot-doc-code-sync",
    "slug": "github-copilot-doc-code-sync",
    "category": "docs",
    "title": "Documentation Matches Code",
    "intent": "Update stale API or function documentation so parameters, behavior, examples, thrown errors, and links match the current implementation.",
    "verify": "documentation diff matches code signature, examples compile or type-check, docs lint passes",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/tutorials/copilot-cookbook/document-code/sync-documentation",
    "source_name": "GitHub Copilot Cookbook",
    "source_type": "official-agent-task",
    "evidence": "Update the existing documentation for the getByCategoryName function to reflect the current implementation",
    "evidence_summary": "Update the existing documentation for the getByCategoryName function to reflect the current implementation; source: GitHub Copilot Cookbook; type: official-agent-task; verification: documentation diff matches code signature, examples compile or type-check, docs lint passes",
    "prompt": "/goal\nGOAL:\nComplete Documentation Matches Code for a developer-facing documentation site or repository: Update stale API or function documentation so parameters, behavior, examples, thrown errors, and links match the current implementation.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect README, docs, examples, runbooks, and lint configuration.\n- Establish a baseline by running or locating evidence for: `documentation diff matches code signature, examples compile or type-check, docs lint passes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not invent APIs, flags, commands, or product behavior.\n- Mark unverified commands clearly instead of presenting guesses as facts.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Update stale API or function documentation so parameters, behavior, examples, thrown errors, and links match the current implementation.\n- The verification command or evidence path succeeds: `documentation diff matches code signature, examples compile or type-check, docs lint passes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `documentation diff matches code signature, examples compile or type-check, docs lint passes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-doc-code-sync.html"
  },
  {
    "id": "tecton-codex-voice-e2e-contract",
    "slug": "tecton-codex-voice-e2e-contract",
    "category": "testing",
    "title": "Voice E2E Goal Contract",
    "intent": "Run a long-horizon Codex goal against a TypeScript voice system using a reading list, working rules, concrete done-when criteria, and anti-pattern fences.",
    "verify": "four target end-to-end voice scenarios pass, transcript review shows no prompt loops, and unavailable metrics are documented honestly",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://www.tectontide.com/en/blog/codex-goal-six-hour-run/",
    "source_name": "Tecton & Tide Codex goal run",
    "source_type": "third-party-review",
    "evidence": "All four target end-to-end voice scenarios passed verification",
    "evidence_summary": "All four target end-to-end voice scenarios passed verification; source: Tecton & Tide Codex goal run; type: third-party-review; verification: four target end-to-end voice scenarios pass, transcript review shows no prompt loops, and unavailable metrics are documented honestly",
    "prompt": "/goal\nGOAL:\nComplete Voice E2E Goal Contract for a project with failing or missing verification gates: Run a long-horizon Codex goal against a TypeScript voice system using a reading list, working rules, concrete done-when criteria, and anti-pattern fences.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect test suites, lint config, CI logs, coverage reports, and failing output.\n- Establish a baseline by running or locating evidence for: `four target end-to-end voice scenarios pass, transcript review shows no prompt loops, and unavailable metrics are documented honestly`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not weaken lint, typecheck, or test rules to create a green result.\n- Fix production or fixture causes before changing expectations.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Run a long-horizon Codex goal against a TypeScript voice system using a reading list, working rules, concrete done-when criteria, and anti-pattern fences.\n- The verification command or evidence path succeeds: `four target end-to-end voice scenarios pass, transcript review shows no prompt loops, and unavailable metrics are documented honestly`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `four target end-to-end voice scenarios pass, transcript review shows no prompt loops, and unavailable metrics are documented honestly` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/tecton-codex-voice-e2e-contract.html"
  },
  {
    "id": "halmob-checkout-p95-goal",
    "slug": "halmob-checkout-p95-goal",
    "category": "performance",
    "title": "Checkout P95 Latency Goal",
    "intent": "Reduce checkout p95 latency below a numeric target while keeping the correctness suite green and logging each experiment.",
    "verify": "checkout benchmark p95 below 120 ms, correctness suite green, iteration log, and blocker report if the benchmark cannot run",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://halmob.com/blog/openai-codex-goals-persistent-objectives-guide",
    "source_name": "Halmob Codex goals guide",
    "source_type": "third-party-tutorial",
    "evidence": "Reduce p95 checkout latency below 120 ms",
    "evidence_summary": "Reduce p95 checkout latency below 120 ms; source: Halmob Codex goals guide; type: third-party-tutorial; verification: checkout benchmark p95 below 120 ms, correctness suite green, iteration log, and blocker report if the benchmark cannot run",
    "prompt": "/goal\nGOAL:\nComplete Checkout P95 Latency Goal for a web application with measurable performance goals: Reduce checkout p95 latency below a numeric target while keeping the correctness suite green and logging each experiment.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect Lighthouse reports, bundles, traces, and critical routes.\n- Establish a baseline by running or locating evidence for: `checkout benchmark p95 below 120 ms, correctness suite green, iteration log, and blocker report if the benchmark cannot run`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not trade correctness, accessibility, or security for faster synthetic scores.\n- Compare before/after metrics on the same route and environment.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reduce checkout p95 latency below a numeric target while keeping the correctness suite green and logging each experiment.\n- The verification command or evidence path succeeds: `checkout benchmark p95 below 120 ms, correctness suite green, iteration log, and blocker report if the benchmark cannot run`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `checkout benchmark p95 below 120 ms, correctness suite green, iteration log, and blocker report if the benchmark cannot run` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/halmob-checkout-p95-goal.html"
  },
  {
    "id": "halmob-research-reproduction-goal",
    "slug": "halmob-research-reproduction-goal",
    "category": "research",
    "title": "Evidence-Backed Research Reproduction",
    "intent": "Reproduce a paper or research result as far as local materials allow while separating confirmed findings, approximate reconstructions, blocked claims, and remaining uncertainty.",
    "verify": "report with confirmed findings, approximate reconstructions, blocked claims, remaining uncertainty, and inspected outputs",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://halmob.com/blog/openai-codex-goals-persistent-objectives-guide",
    "source_name": "Halmob Codex goals guide",
    "source_type": "third-party-tutorial",
    "evidence": "Produce the strongest evidence-backed reproduction of the paper",
    "evidence_summary": "Produce the strongest evidence-backed reproduction of the paper; source: Halmob Codex goals guide; type: third-party-tutorial; verification: report with confirmed findings, approximate reconstructions, blocked claims, remaining uncertainty, and inspected outputs",
    "prompt": "/goal\nGOAL:\nComplete Evidence-Backed Research Reproduction for a research task: Reproduce a paper or research result as far as local materials allow while separating confirmed findings, approximate reconstructions, blocked claims, and remaining uncertainty.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect source lists, citation notes, evidence files, and acceptance criteria.\n- Establish a baseline by running or locating evidence for: `report with confirmed findings, approximate reconstructions, blocked claims, remaining uncertainty, and inspected outputs`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not present unsourced claims as facts.\n- Keep direct quotes short and attach a public URL for every external claim.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reproduce a paper or research result as far as local materials allow while separating confirmed findings, approximate reconstructions, blocked claims, and remaining uncertainty.\n- The verification command or evidence path succeeds: `report with confirmed findings, approximate reconstructions, blocked claims, remaining uncertainty, and inspected outputs`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `report with confirmed findings, approximate reconstructions, blocked claims, remaining uncertainty, and inspected outputs` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/halmob-research-reproduction-goal.html"
  },
  {
    "id": "codex-goalcraft-six-field-contract",
    "slug": "codex-goalcraft-six-field-contract",
    "category": "workflow",
    "title": "Goalcraft Six-Field Contract Spine",
    "intent": "Write any /goal as a compact, evidence-first, thread-scoped completion contract with explicit outcome, verification surface, constraints, boundaries, iteration policy, and blocked stop conditions instead of vague effort descriptions.",
    "verify": "activated goal text passes length and structure validation (under 4000 chars, all 6 fields present); subsequent agent run produces claim-by-claim evidence audit instead of proxy claims",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://raw.githubusercontent.com/grp06/goalcraft/main/SKILL.md",
    "source_name": "goalcraft SKILL.md",
    "source_type": "tool-readme",
    "evidence": "six-field spine: Outcome + Verification surface + Constraints + Boundaries + Iteration policy + Blocked stop condition",
    "evidence_summary": "six-field spine: Outcome + Verification surface + Constraints + Boundaries + Iteration policy + Blocked stop condition; source: goalcraft SKILL.md; type: tool-readme; verification: activated goal text passes length and structure validation (under 4000 chars, all 6 fields present); subsequent agent run produces claim-by-claim evidence audit instead of proxy claims",
    "prompt": "/goal\nGOAL:\nComplete Goalcraft Six-Field Contract Spine for a coding-agent workflow repository: Write any /goal as a compact, evidence-first, thread-scoped completion contract with explicit outcome, verification surface, constraints, boundaries, iteration policy, and blocked stop conditions instead of vague effort descriptions.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `activated goal text passes length and structure validation (under 4000 chars, all 6 fields present); subsequent agent run produces claim-by-claim evidence audit instead of proxy claims`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Write any /goal as a compact, evidence-first, thread-scoped completion contract with explicit outcome, verification surface, constraints, boundaries, iteration policy, and blocked stop conditions instead of vague effort descriptions.\n- The verification command or evidence path succeeds: `activated goal text passes length and structure validation (under 4000 chars, all 6 fields present); subsequent agent run produces claim-by-claim evidence audit instead of proxy claims`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `activated goal text passes length and structure validation (under 4000 chars, all 6 fields present); subsequent agent run produces claim-by-claim evidence audit instead of proxy claims` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/codex-goalcraft-six-field-contract.html"
  },
  {
    "id": "goal-md-fitness-dual-score-loop",
    "slug": "goal-md-fitness-dual-score-loop",
    "category": "prompt-optimization",
    "title": "Fitness Function Dual-Score Improvement Loop",
    "intent": "For goals without natural scalar metric (docs quality, code health, consistency), construct an explicit runnable fitness function plus dual-score (outcome + instrument quality guard) and drive an improvement loop with iterations.jsonl ledger until converge criteria.",
    "verify": "./scripts/score.sh --json outputs numeric scores; iterations.jsonl shows progress without instrument gaming; final report matches When to Stop template",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://raw.githubusercontent.com/jmilinovich/goal-md/main/template/GOAL.md",
    "source_name": "goal-md template",
    "source_type": "tool-readme",
    "evidence": "dual-score split + measure/diagnose/act/verify/revert loop + Action Catalog + machine-checkable stopping conditions",
    "evidence_summary": "dual-score split + measure/diagnose/act/verify/revert loop + Action Catalog + machine-checkable stopping conditions; source: goal-md template; type: tool-readme; verification: ./scripts/score.sh --json outputs numeric scores; iterations.jsonl shows progress without instrument gaming; final report matches When to Stop template",
    "prompt": "/goal\nGOAL:\nComplete Fitness Function Dual-Score Improvement Loop for an eval-backed prompt project: For goals without natural scalar metric (docs quality, code health, consistency), construct an explicit runnable fitness function plus dual-score (outcome + instrument quality guard) and drive an improvement loop with iterations.jsonl ledger until converge criteria.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect prompt files, eval cases, scoring reports, regressions, and failure examples.\n- Establish a baseline by running or locating evidence for: `./scripts/score.sh --json outputs numeric scores; iterations.jsonl shows progress without instrument gaming; final report matches When to Stop template`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not delete, weaken, or cherry-pick eval cases to improve the score.\n- Report representative failures as well as the final score.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: For goals without natural scalar metric (docs quality, code health, consistency), construct an explicit runnable fitness function plus dual-score (outcome + instrument quality guard) and drive an improvement loop with iterations.jsonl ledger until converge criteria.\n- The verification command or evidence path succeeds: `./scripts/score.sh --json outputs numeric scores; iterations.jsonl shows progress without instrument gaming; final report matches When to Stop template`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `./scripts/score.sh --json outputs numeric scores; iterations.jsonl shows progress without instrument gaming; final report matches When to Stop template` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-md-fitness-dual-score-loop.html"
  },
  {
    "id": "goal-ledger-html-resume-incomplete-hatch",
    "slug": "goal-ledger-html-resume-incomplete-hatch",
    "category": "goal-maintenance",
    "title": "Single-File HTML Goal Ledger with Resume Block and Structured Incomplete Escape",
    "intent": "Maintain one canonical browser-viewable implementation-notes.html containing Resume Here block, inline progressEvents timeline, and explicit [incomplete]/[blocked] states with full reason/proof/impact so long-running /goal can safely pause and resume across compaction or handoff without drift.",
    "verify": ".agent/runs/<goal-id>/implementation-notes.html exists, opens in browser, is appended at every checkpoint, and any incomplete item carries structured explanation instead of silent drop",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://raw.githubusercontent.com/kingbootoshi/goal-ledger/main/plugins/goal-ledger/skills/goal/SKILL.md",
    "source_name": "kingbootoshi/goal-ledger SKILL.md",
    "source_type": "tool-readme",
    "evidence": "Resume Here + progressEvents array + 6 states including [incomplete] with mandatory explanation fields",
    "evidence_summary": "Resume Here + progressEvents array + 6 states including [incomplete] with mandatory explanation fields; source: kingbootoshi/goal-ledger SKILL.md; type: tool-readme; verification: .agent/runs/<goal-id>/implementation-notes.html exists, opens in browser, is appended at every checkpoint, and any incomplete item carries structured explanation instead of silent drop",
    "prompt": "/goal\nGOAL:\nComplete Single-File HTML Goal Ledger with Resume Block and Structured Incomplete Escape for a goal-management workflow: Maintain one canonical browser-viewable implementation-notes.html containing Resume Here block, inline progressEvents timeline, and explicit [incomplete]/[blocked] states with full reason/proof/impact so long-running /goal can safely pause and resume across compaction or handoff without drift.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect active goals, done conditions, audit logs, and continuation state.\n- Establish a baseline by running or locating evidence for: `.agent/runs/<goal-id>/implementation-notes.html exists, opens in browser, is appended at every checkpoint, and any incomplete item carries structured explanation instead of silent drop`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not mark a goal complete without auditing the current done condition.\n- Keep goal edits and completion reasons visible in the final output.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Maintain one canonical browser-viewable implementation-notes.html containing Resume Here block, inline progressEvents timeline, and explicit [incomplete]/[blocked] states with full reason/proof/impact so long-running /goal can safely pause and resume across compaction or handoff without drift.\n- The verification command or evidence path succeeds: `.agent/runs/<goal-id>/implementation-notes.html exists, opens in browser, is appended at every checkpoint, and any incomplete item carries structured explanation instead of silent drop`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `.agent/runs/<goal-id>/implementation-notes.html exists, opens in browser, is appended at every checkpoint, and any incomplete item carries structured explanation instead of silent drop` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/goal-ledger-html-resume-incomplete-hatch.html"
  },
  {
    "id": "chinese-v2ex-grillme-strong-goal-contract",
    "slug": "chinese-v2ex-grillme-strong-goal-contract",
    "category": "workflow",
    "title": "Strong Verifiable Goal Contract After Alignment Interview",
    "intent": "After a structured alignment interview, produce a binding /goal contract with explicit success evidence, hard constraints, file boundaries, iteration strategy, and blocking/escape handling so a Ralph-loop or native /goal agent can run autonomously until evidence-based completion.",
    "verify": "final agent output includes scoped diff + passing verification commands + iteration/token log; DONE WHEN audited against original contract without subjective claims; escape triggered on budget or blocker",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://v2ex.com/t/1214285",
    "source_name": "V2EX Chinese engineering community (JustW post)",
    "source_type": "public-forum",
    "evidence": "grill-me + goal 6-element strong contract pattern with Ralph loop execution",
    "evidence_summary": "grill-me + goal 6-element strong contract pattern with Ralph loop execution; source: V2EX Chinese engineering community (JustW post); type: public-forum; verification: final agent output includes scoped diff + passing verification commands + iteration/token log; DONE WHEN audited against original contract without subjective claims; escape triggered on budget or blocker",
    "prompt": "/goal\nGOAL:\nComplete Strong Verifiable Goal Contract After Alignment Interview for a coding-agent workflow repository: After a structured alignment interview, produce a binding /goal contract with explicit success evidence, hard constraints, file boundaries, iteration strategy, and blocking/escape handling so a Ralph-loop or native /goal agent can run autonomously until evidence-based completion.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect goal text, progress logs, branch state, and verification artifacts.\n- Establish a baseline by running or locating evidence for: `final agent output includes scoped diff + passing verification commands + iteration/token log; DONE WHEN audited against original contract without subjective claims; escape triggered on budget or blocker`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not claim a goal is complete without a current audit of the stated contract.\n- Pause if the goal text, branch state, or permissions are inconsistent.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: After a structured alignment interview, produce a binding /goal contract with explicit success evidence, hard constraints, file boundaries, iteration strategy, and blocking/escape handling so a Ralph-loop or native /goal agent can run autonomously until evidence-based completion.\n- The verification command or evidence path succeeds: `final agent output includes scoped diff + passing verification commands + iteration/token log; DONE WHEN audited against original contract without subjective claims; escape triggered on budget or blocker`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `final agent output includes scoped diff + passing verification commands + iteration/token log; DONE WHEN audited against original contract without subjective claims; escape triggered on budget or blocker` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/chinese-v2ex-grillme-strong-goal-contract.html"
  },
  {
    "id": "github-copilot-usage-metrics-reconciliation",
    "slug": "github-copilot-usage-metrics-reconciliation",
    "category": "data-analytics",
    "title": "Copilot Usage Metrics Reconciliation",
    "intent": "Reconcile Copilot dashboard, API, and export metrics before reporting agent adoption or pull-request impact trends.",
    "verify": "metrics reconciliation report with dashboard/API/export fields, documented exclusions, and team-level join notes",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://docs.github.com/en/copilot/reference/copilot-usage-metrics/reconciling-usage-metrics",
    "source_name": "GitHub Copilot usage metrics reconciliation docs",
    "source_type": "official-workflow",
    "evidence": "dashboard, APIs, and export files all use the same underlying telemetry data, but they aggregate and present it differently",
    "evidence_summary": "dashboard, APIs, and export files all use the same underlying telemetry data, but they aggregate and present it differently; source: GitHub Copilot usage metrics reconciliation docs; type: official-workflow; verification: metrics reconciliation report with dashboard/API/export fields, documented exclusions, and team-level join notes",
    "prompt": "/goal\nGOAL:\nComplete Copilot Usage Metrics Reconciliation for an analytics or BI project: Reconcile Copilot dashboard, API, and export metrics before reporting agent adoption or pull-request impact trends.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect metric SQL, event schemas, dashboard definitions, and validation queries.\n- Establish a baseline by running or locating evidence for: `metrics reconciliation report with dashboard/API/export fields, documented exclusions, and team-level join notes`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Reconcile Copilot dashboard, API, and export metrics before reporting agent adoption or pull-request impact trends.\n- The verification command or evidence path succeeds: `metrics reconciliation report with dashboard/API/export fields, documented exclusions, and team-level join notes`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `metrics reconciliation report with dashboard/API/export fields, documented exclusions, and team-level join notes` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/github-copilot-usage-metrics-reconciliation.html"
  },
  {
    "id": "layout-design-system-context-export",
    "slug": "layout-design-system-context-export",
    "category": "design",
    "title": "Design System Context Export",
    "intent": "Extract design tokens, components, and visual patterns into agent-readable context so generated UI follows the product design system.",
    "verify": "layout.md and token export reviewed, component variant preview checked, and design-system health score or screenshot evidence captured",
    "difficulty": "intermediate",
    "origin": "source-backed",
    "source_url": "https://layout.design/docs",
    "source_name": "Layout design system docs",
    "source_type": "third-party-project",
    "evidence": "Pull design tokens, components, fonts, and screenshots from Figma files or live websites",
    "evidence_summary": "Pull design tokens, components, fonts, and screenshots from Figma files or live websites; source: Layout design system docs; type: third-party-project; verification: layout.md and token export reviewed, component variant preview checked, and design-system health score or screenshot evidence captured",
    "prompt": "/goal\nGOAL:\nComplete Design System Context Export for a product UI codebase: Extract design tokens, components, and visual patterns into agent-readable context so generated UI follows the product design system.\n\nCONTEXT:\n- Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo.\n- Inspect design tokens, component variants, layouts, visual states, and screenshots.\n- Establish a baseline by running or locating evidence for: `layout.md and token export reviewed, component variant preview checked, and design-system health score or screenshot evidence captured`.\n\nCONSTRAINTS:\n- Keep the scope limited to this goal; do not expand into unrelated cleanup.\n- Do not weaken tests, delete assertions, or mask errors to make verification pass.\n- Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns.\n- Do not replace the app with a landing-page style redesign.\n- Preserve domain workflows and use existing design tokens where they exist.\n\nDONE WHEN:\n- The implementation or documentation directly satisfies: Extract design tokens, components, and visual patterns into agent-readable context so generated UI follows the product design system.\n- The verification command or evidence path succeeds: `layout.md and token export reviewed, component variant preview checked, and design-system health score or screenshot evidence captured`.\n- The final diff is scoped to the relevant files and has no unrelated formatting churn.\n\nVERIFY:\n- Run `layout.md and token export reviewed, component variant preview checked, and design-system health score or screenshot evidence captured` or the closest repo-local equivalent if the exact command is not available.\n- Capture before/after evidence for the behavior, metric, report, or artifact involved.\n- If verification cannot run locally, stop and report the missing dependency instead of guessing success.\n\nOUTPUT:\n- Summarize changed files, key decisions, verification output, and remaining risks.\n- Include any follow-up that is required for production rollout or human review.\n\nSTOP RULES:\n- Pause if secrets, production access, stakeholder decisions, or destructive data operations are required.\n- Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis.\n- Do not mark the goal complete until the current repository state has been audited against DONE WHEN.",
    "static_path": "goals/layout-design-system-context-export.html"
  }
]