okhp3-custom-gpt-readinesslisted

# okhp3-custom-gpt-readiness **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) Turn scattered GPT ideas and partial artifacts into a buildable, testable brief. This is an intake and gap-analysis skill, not the builder itself. ## Scope | In scope | Out of scope | |---|---| | Concept triage, evidence inventory, requirement elicitation, readiness scoring, and builder handoff | Writing production integrations, managing credentials, publishing a GPT, or claiming volatile platform limits | ## Operating contract 1. **Inventory before asking.** Inspect the supplied conversation, notes, files, prior prompts, prompt-chain stages, and existing GPT export. Record each artifact as `present`, `partial`, `missing`, or `conflicting`; never ask for information already present. 2. **Classify every claim.** Quote or point to the source artifact for every `present` claim. Label it `verified_platform_fact`, `source_derived_practice`, `theory`, `preference`, `inferred`, or `unknown`. A source assertion does not become a platform fact by being repeated. 3. **Assess the eight readiness domains:** job and audience, outcomes, boundaries, conversation contract, instruction behavior, knowledge/data, tools and permissions, and evaluation/governance. 4. **Identify blockers.** A missing primary job, audience, safety boundary, allowed data source, or acceptance test is a build blocker. Do not declare a concept ready while a blocker remai