Update to BuildBetter.ai

{
  "description": "Review and operate BuildBetter knowledge-gap recommendations, project attachments, durable rechecks, and release-readiness analysis with explicit evidence and mutation approval. Use when the user asks what documentation is missing, wants to approve or decline a gap, attach a gap to product work, re-run documentation checks, or assess release knowledge readiness.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 250
    }
  ],
  "name": "buildbetter-knowledge-gaps",
  "skill_md_contents": "---\nname: buildbetter-knowledge-gaps\ndescription: Review and operate BuildBetter knowledge-gap recommendations, project attachments, durable rechecks, and release-readiness analysis with explicit evidence and mutation approval. Use when the user asks what documentation is missing, wants to approve or decline a gap, attach a gap to product work, re-run documentation checks, or assess release knowledge readiness.\n---\n\n# BuildBetter Knowledge Gaps\n\nFollow [buildbetter-start’s interaction guidance](../buildbetter-start/SKILL.md#interaction): complete supported work through chat; use optional UI only when it reduces effort or clarifies a decision.\n\n## Safety Contract\n\nSearch organization skills with list-skills and get-skill first. list-knowledge-gaps is observational. Review state changes, project attachments, rechecks, source sync, and release analysis create or mutate durable records and require approval for the exact gaps, project, release, or source scope.\n\nUse release-readiness tools only when they appear in the registered MCP inventory. If a named tool is unavailable, report that state instead of guessing or using GraphQL mutation.\n\n## Gap Review\n\n1. Use list-knowledge-gaps with the relevant approval state, source, project, or date scope. State filters and page coverage.\n2. Inspect recommendation, evidence, current state, related artifact, and whether the underlying customer or release evidence is still current.\n3. Classify the next action: needs investigation, approve, decline, attach, recheck, mark done, or no-op.\n4. Before review-knowledge-gap, read back the exact gap ID, current state, intended new state, and rationale. Obtain approval.\n5. Before attach-knowledge-gap-to-project, verify the exact project_v2 ID with get-project, show the attachment, and obtain approval.\n6. For recheck-knowledge-gap, provide a client-generated UUID idempotency key, reuse it only after an unknown outcome, and poll the returned durable receipt with get-job or the operation tool named by the response.\n7. Verify final state with list-knowledge-gaps and project detail where relevant.\n\n## Release Readiness\n\nWhen registered, use sync-release-sources to refresh the explicitly approved source scope, estimate-release-knowledge-gaps for a no-surprise estimate, and analyze-release-knowledge-gaps only after reviewing the estimate and cost or work bounds. Preserve release identifier, source SHAs or versions, operation ID, and exact completion state.\n\n## Output\n\nReport searched scope, gap IDs and states, evidence, proposed actions, approval state, mutation receipts, operation or job IDs, project attachments, release source identifiers, completed analysis, and remaining unknowns. Distinguish recommendation reviewed, approved, attached, recheck queued, recheck completed, and documentation verified.\n"
}