Talk Once
Turn one substantive conversation into reusable content while keeping the user
in control of truth, voice, and publishing.
Operating rules
- Keep Markdown and JSON files as the source of truth.
- Work with any model or agent harness available to the user.
- Separate the user's claims from sourced facts and agent inference.
- Use a voice profile as style guidance only; never invent beliefs or claims.
- Establish one canonical article before producing derivatives.
- Ask for approval at the brief, article, and distribution boundaries.
- Never publish or post without explicit approval.
- Keep recordings, raw transcripts, credentials, and unpublished personal data
outside public repositories.
Workflow
- Create a content package from the Talk Once template or schema.
- If the package references a voice profile, read it before interviewing.
- Interview for the idea, audience, evidence, personal experience, useful
examples, disagreements, and desired outcome. Ask one focused question at a
time when the interface supports conversation.
- Attach supplied sources. Research only when requested or when factual
verification is necessary. Preserve links and distinguish evidence from
interpretation.
- Produce a brief containing the thesis, audience, promise, outline, claims,
sources, unknowns, and tone notes. Stop for approval.
- Draft one canonical long-form article from the approved brief. Preserve the
speaker's meaning while tightening structure and prose. Stop for approval.
- Produce only the requested derivatives from the approved canonical article.
Adapt format and length without changing the underlying position.
- Present the distribution set for approval. Do not publish automatically.
Interoperability
Prefer stable contracts over harness-specific state:
- Voice providers export a versioned JSON profile. VoiceForge supports
forge profile --output <path>.
- Talk Once packages conform to
content-package.schema.json and may reference
a voice profile by provider, path, and version.
- Harness integrations should orchestrate this workflow without changing the
contracts.
Read references/contracts.md when creating or
validating package files.
Completion
Return the created artifact paths, current package status, outstanding approval,
and any unresolved factual questions. A draft is not published content.
1---2name: talk-once3description: Turn a conversation, voice note, transcript, or guided interview into one source-grounded canonical article and reviewed channel-specific drafts. Use when someone wants to be interviewed about an idea, create long-form content from speech, repurpose one piece across channels, build a content package, or run the Talk Once workflow with an optional VoiceForge profile.4---56# Talk Once78Turn one substantive conversation into reusable content while keeping the user9in control of truth, voice, and publishing.1011## Operating rules1213- Keep Markdown and JSON files as the source of truth.14- Work with any model or agent harness available to the user.15- Separate the user's claims from sourced facts and agent inference.16- Use a voice profile as style guidance only; never invent beliefs or claims.17- Establish one canonical article before producing derivatives.18- Ask for approval at the brief, article, and distribution boundaries.19- Never publish or post without explicit approval.20- Keep recordings, raw transcripts, credentials, and unpublished personal data21 outside public repositories.2223## Workflow24251. Create a content package from the Talk Once template or schema.262. If the package references a voice profile, read it before interviewing.273. Interview for the idea, audience, evidence, personal experience, useful28 examples, disagreements, and desired outcome. Ask one focused question at a29 time when the interface supports conversation.304. Attach supplied sources. Research only when requested or when factual31 verification is necessary. Preserve links and distinguish evidence from32 interpretation.335. Produce a brief containing the thesis, audience, promise, outline, claims,34 sources, unknowns, and tone notes. Stop for approval.356. Draft one canonical long-form article from the approved brief. Preserve the36 speaker's meaning while tightening structure and prose. Stop for approval.377. Produce only the requested derivatives from the approved canonical article.38 Adapt format and length without changing the underlying position.398. Present the distribution set for approval. Do not publish automatically.4041## Interoperability4243Prefer stable contracts over harness-specific state:4445- Voice providers export a versioned JSON profile. VoiceForge supports46 `forge profile --output <path>`.47- Talk Once packages conform to `content-package.schema.json` and may reference48 a voice profile by provider, path, and version.49- Harness integrations should orchestrate this workflow without changing the50 contracts.5152Read [references/contracts.md](references/contracts.md) when creating or53validating package files.5455## Completion5657Return the created artifact paths, current package status, outstanding approval,58and any unresolved factual questions. A draft is not published content.
cyperx84