Ideagents

View saved version →

---
name: challenge-proposal
description: Stress-test an idea, plan or proposal against its goals and constraints with configurable profiles and quick or guided participation. Expose unsupported assumptions, meaningful alternatives and concrete validation steps while keeping the working record and requested diagrams current.
---

# Challenge a proposal

Produce an actionable critique of the proposal the user supplied. Use the host model to examine several perspectives; do not describe the result as independent expert review or consensus. No separate model, external account or local executable is required.

The user's explicit scope, format and requested depth override these defaults. Preserve their objective; critique is not permission to replace it with a different product or widen the task. In quick mode, for a short proposal or a concise request, lead with the recommendation and a compact set of consequential findings. Integrate the perspectives and counterargument into those findings rather than repeating them in separate narrative sections.

## Profiles, participation and working outputs

Read the [stateless backend guide](../develop-idea/assets/backend-guide.md) before using record tools. Use `ideagents_get_profiles` for the current catalog/defaults, `ideagents_revise_record` for useful typed decision changes, and `ideagents_export_session` for requested consistent exports. Before the first record/export call, state that necessary bounded current fields, including any minimum user direction for a selected choice, go to Ideation Lab, Corp.; honor a request to keep content in chat. Never send transcripts, secrets or unnecessary personal data. Keep returned state in chat; no server session is saved. Create with `record: null`, `expected_revision: 0` and no `expected_state_hash`. Every later revise and every export requires `expected_state_hash`, copied unchanged with the exact `record` from the last successful result or supplied capsule; then adopt the returned `record` and `state_hash`. Never invent or recompute this guard from corrupted or retyped input, bypass a failure with a new null record, or claim server history or a signature. If no actual guard is available, ask for the latest checked record or capsule, or offer an honest unchecked chat draft. Tool failures permit honest unchecked text fallback, not a claim of validation.

Use the [shared session protocol](../develop-idea/assets/session-protocol.md), [six-profile catalog](../develop-idea/assets/profiles.md) and [working-record guide](../develop-idea/assets/working-record.md) for session controls and coordinated documents/diagrams. Read the protocol when starting or continuing a guided session or handling a control, settings, output or export request, and the catalog when selecting or changing a profile. If a shared file is unavailable in this host, apply this section directly and do not claim to have read it; the six profile names are App Builder, Policy War Room, Process Architect, Viral Campaign, Startup Pitch and Technical RFC. The current user's instructions override all defaults. Preserve their active settings across these three workflows within the available conversation.

For collaborative guided use, produce one short perspective per assistant turn by default, then actually end the turn so the user can participate. A request for a quick answer or complete deliverable takes priority and receives a coherent result in one response. Pause, resume, skip, profile changes, custom roles and output on/off settings work through ordinary chat instructions. On a correction, update affected decisions and scope before continuing; never simulate the user's answer or treat silence as consent.

Use the host model for reasoning and the stateless tools for checked record changes and deterministic exports at appropriate decision checkpoints. Label proposals versus user-selected decisions; keep stable revisions when revising actual prior outputs. Disabled or deferred outputs b

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: develop-idea
description: Develop a rough idea with configurable profiles, guided user participation, relevant perspectives, explicit trade-offs and an evolving decision record. Use when shaping an idea, choosing or changing an Ideagents profile, or continuing an idea session; adapt to quick requests.
---

# Develop an idea

Turn the user's idea into a useful next decision and a coherent concept brief. Use the current chat's model; the panel is a set of analytical perspectives, not independent experts, independent models or a vote. No separate model API, external account or local execution is required. The connected stateless service checks bounded records and compiles exports; conceptual drafts can remain in chat.

Explicit user instructions take priority over the defaults below. Adapt the depth and format to the request; a request for a quick answer does not require a staged interview or a role-play transcript. In quick mode, for a small idea or a concise request, integrate the useful perspective findings directly into a short brief rather than showing a panel transcript and then repeating it in a report. State each constraint once unless a specific trade-off needs it repeated.

## Profiles, participation and working outputs

Read the [stateless backend guide](assets/backend-guide.md) before using record tools. Use `ideagents_get_profiles` for the current catalog/defaults, `ideagents_revise_record` for useful typed decision changes, and `ideagents_export_session` for requested consistent exports. Before the first record/export call, state that necessary bounded current fields, including any minimum user direction for a selected choice, go to Ideation Lab, Corp.; honor a request to keep content in chat. Never send transcripts, secrets or unnecessary personal data. Keep returned state in chat; no server session is saved. Create with `record: null`, `expected_revision: 0` and no `expected_state_hash`. Every later revise and every export requires `expected_state_hash`, copied unchanged with the exact `record` from the last successful result or supplied capsule; then adopt the returned `record` and `state_hash`. Never invent or recompute this guard from corrupted or retyped input, bypass a failure with a new null record, or claim server history or a signature. If no actual guard is available, ask for the latest checked record or capsule, or offer an honest unchecked chat draft. Tool failures permit honest unchecked text fallback, not a claim of validation.

Use the [shared session protocol](assets/session-protocol.md), [six-profile catalog](assets/profiles.md) and [working-record guide](assets/working-record.md) for session controls and coordinated documents/diagrams. Read the protocol when starting or continuing a guided session or handling a control, settings, output or export request, and the catalog when selecting or changing a profile. If a shared file is unavailable in this host, apply this section directly and do not claim to have read it; the six profile names are App Builder, Policy War Room, Process Architect, Viral Campaign, Startup Pitch and Technical RFC. The current user's instructions override all defaults. Preserve their active settings across these three workflows within the available conversation.

For collaborative guided use, produce one short perspective per assistant turn by default, then actually end the turn so the user can participate. A request for a quick answer or complete deliverable takes priority and receives a coherent result in one response. Pause, resume, skip, profile changes, custom roles and output on/off settings work through ordinary chat instructions. On a correction, update affected decisions and scope before continuing; never simulate the user's answer or treat silence as consent.

Use the host model for reasoning and the stateless tools for checked record changes and deterministic exports at appropriate decision checkpoints. Label proposals versus user-selected decisions; keep 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 5 — file references are metadata, not package contents.

View saved version →

---
name: prepare-handoff
description: Turn agreed decisions or an idea-review record into a practical handoff with scope, exclusions, acceptance checks and next actions. Preserve active profile settings, user corrections and document/diagram state; use when exporting a session or handing work to a collaborator.
---

# Prepare a handoff

Compile a faithful brief that another person can act on without reading the entire conversation. Use the user's current decisions and constraints, not a new round of ideation. A completed develop-idea or challenge-proposal skill is not required; use any adequate user-supplied context.

Explicit user instructions override the default structure and level of detail. For a small delivery or a concise request, write a brief the intended recipient can act on quickly. State constraints and changes once, then refer to the affected requirement or check without repeating the whole context. This workflow uses the host model and the connected stateless record service; it requires no external account, separate model API or local execution.

## Profiles, participation and working outputs

Read the [stateless backend guide](../develop-idea/assets/backend-guide.md) before using record tools. Use `ideagents_get_profiles` for the current catalog/defaults, `ideagents_revise_record` for useful typed decision changes, and `ideagents_export_session` for requested consistent exports. Before the first record/export call, state that necessary bounded current fields, including any minimum user direction for a selected choice, go to Ideation Lab, Corp.; honor a request to keep content in chat. Never send transcripts, secrets or unnecessary personal data. Keep returned state in chat; no server session is saved. Create with `record: null`, `expected_revision: 0` and no `expected_state_hash`. Every later revise and every export requires `expected_state_hash`, copied unchanged with the exact `record` from the last successful result or supplied capsule; then adopt the returned `record` and `state_hash`. Never invent or recompute this guard from corrupted or retyped input, bypass a failure with a new null record, or claim server history or a signature. If no actual guard is available, ask for the latest checked record or capsule, or offer an honest unchecked chat draft. Tool failures permit honest unchecked text fallback, not a claim of validation.

Use the [shared session protocol](../develop-idea/assets/session-protocol.md), [six-profile catalog](../develop-idea/assets/profiles.md) and [working-record guide](../develop-idea/assets/working-record.md) for session controls and coordinated documents/diagrams. Read the protocol when starting or continuing a guided session or handling a control, settings, output or export request, and the catalog when selecting or changing a profile. If a shared file is unavailable in this host, apply this section directly and do not claim to have read it; the six profile names are App Builder, Policy War Room, Process Architect, Viral Campaign, Startup Pitch and Technical RFC. The current user's instructions override all defaults. Preserve their active settings across these three workflows within the available conversation.

For collaborative guided use, produce one short perspective per assistant turn by default, then actually end the turn so the user can participate. A request for a quick answer or complete deliverable takes priority and receives a coherent result in one response. Pause, resume, skip, profile changes, custom roles and output on/off settings work through ordinary chat instructions. On a correction, update affected decisions and scope before continuing; never simulate the user's answer or treat silence as consent.

Use the host model for reasoning and the stateless tools for checked record changes and deterministic exports at appropriate decision checkpoints. Label proposals versus user-selected decisions; keep stable revisions when revising actual prior outputs. Disabled or def

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.