okhp3-askjamie-gpt-readiness

Topics in the source

• okhp3-askjamie-gpt-readiness
• AskJamie readiness lens
• Scope
• Operating contract
• Required output
• Quality gates
• Handoff
• About

OverKill Hill P³ · overkillhill.com · 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. Assess the concept against https://askjamie.bot as its public positioning reference. In addition to the eight generic readiness domains, require evidence for the messy context being clarified, the decision or walkthrough being supported, the audience's pressure and knowledge level, the visible branch logic, the evidence/uncertainty policy, and the boundary between interpretation, recommendation, and authorized action. A concept is not ready merely because it has a warm persona; the user must be able to see how it reaches a clearer next step. | 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 | 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 conf

This is an excerpt. Refer to the complete source and its current requirements.