# Rebeccapowell Dotnet Temporal AI Temporal Workflow Apis

> Workflow APIs: Run / Signal / Query / Update / Child Workflows

- Skill: `tomevault-io/rebeccapowell-dotnet-temporal-ai-temporal-workflow-apis` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/rebeccapowell-dotnet-temporal-ai-temporal-workflow-apis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/rebeccapowell-dotnet-temporal-ai-temporal-workflow-apis/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/rebeccapowell-dotnet-temporal-ai-temporal-workflow-apis

---


# Workflow APIs: Run / Signal / Query / Update / Child Workflows

## When to use
Use this when the user is defining or refactoring:
- workflow entrypoint shape
- signal/query/update APIs
- child workflow orchestration
- idempotency & state model

## Required guidance
- Queries must be **read-only**.
- Signals are **fire-and-forget**; make handlers idempotent.
- Updates **mutate with acknowledgement**; describe acceptance/completion semantics.
- Keep workflow state explicit; do not use static mutable state.

## Output required
Provide:
1. Recommended public surface (method signatures + attributes)
2. State model outline (fields + invariants)
3. Idempotency approach for signals/updates
4. Minimal compile-ready example

## Notes
- Prefer stable, explicit task queues.
- If the SDK supports update stages, mention how to wait for admitted/accepted/completed when relevant.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/rebeccapowell) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->

