create_dr_plan_import
ChatGPTUse this only after the assistant has already shown the proposed plan in a prior assistant turn, asked "Want me to turn this into a D/R plan?", and the user answers yes, yep, do it, looks good, send it, send to D/R, or similar. Include every core and optional habit shown to the user in plan.habits, with optional add-ons marked optional: true. Put concise, board-ready habit instructions in habit.detail; keep long coaching context in chat, not D/R. Do not call it during initial brainstorming, discovery, after a vague first message, after a vague answer, or in the same turn that first shows the proposed plan. It creates a pending draft and Review Plan URL only; the D/R user must approve before board records are created. After success, respond only with the Review Plan link, plan counts, and approval reminder.
create_dr_plan_import
ChatGPTUse this only after the assistant has already shown the proposed plan in a prior assistant turn, asked "Want me to turn this into a D/R plan?", and the user answers yes, yep, do it, looks good, send it, send to D/R, or similar. Include every core and optional habit shown to the user in plan.habits, with optional add-ons marked optional: true. Put concise, board-ready habit instructions in habit.detail; keep long coaching context in chat, not D/R. Do not call it during initial brainstorming, discovery, after a vague first message, after a vague answer, or in the same turn that first shows the proposed plan. It creates a pending draft and Review Plan URL only; the D/R user must approve before board records are created. After success, respond only with the Review Plan link, plan counts, and approval reminder.
draft_dr_plan
ChatGPTUse this to normalize and validate a proposed PlanImportPayload without creating drafts or board records. Use only after discovery and conversational planning, not after a vague first message or vague answer. If the user wants one commitment or routine, draft a habit-only payload with no goals or milestones. Use habit.name and category.name exactly. Put concise, board-ready instructions in habit.detail, ideally under 160 characters.
draft_dr_plan
ChatGPTUse this to normalize and validate a proposed PlanImportPayload without creating drafts or board records. Use only after discovery and conversational planning, not after a vague first message or vague answer. If the user wants one commitment or routine, draft a habit-only payload with no goals or milestones. Use habit.name and category.name exactly. Put concise, board-ready instructions in habit.detail, ideally under 160 characters.
get_dr_plan_schema
ChatGPTUse this before drafting. It returns the exact D/R PlanImportPayload shape plus D/R planning rules. For broad first messages, ask a clarifying question only; do not show plan bullets yet. For simple single-behavior asks, ask whether the user wants one D/R habit/commitment or a fuller plan. If the user answer is vague, ask a follow-up and do not infer values from examples. After the user answers, show the proposed plan and ask "Want me to turn this into a D/R plan?" Do not create the draft in the same turn that first shows the plan.
get_dr_plan_schema
ChatGPTUse this before drafting. It returns the exact D/R PlanImportPayload shape plus D/R planning rules. For broad first messages, ask a clarifying question only; do not show plan bullets yet. For simple single-behavior asks, ask whether the user wants one D/R habit/commitment or a fuller plan. If the user answer is vague, ask a follow-up and do not infer values from examples. After the user answers, show the proposed plan and ask "Want me to turn this into a D/R plan?" Do not create the draft in the same turn that first shows the plan.
list_dr_persona_plans
ChatGPTUse this when a user wants inspiration/persona board examples that can become pending D/R imports for review.
list_dr_persona_plans
ChatGPTUse this when a user wants inspiration/persona board examples that can become pending D/R imports for review.
