Skip to content
Agentic Craft

Templates

End-to-end agentic product workflows built from registry-ready primitives. Templates document the sequence, states, human control points, and recovery behavior that a production interface needs.

Review to delivery

Templates should describe the whole job, not a single widget. This map is the reusable backbone across review, approval, clarification, memory, and monitoring flows.

input

Collect

Gather selected files, policies, prior decisions, and user intent.

agent

Inspect

Show observable work, touched sources, gaps, and confidence.

human

Clarify

Ask only for missing decisions that would otherwise be invented.

human

Approve

Lock the consequence preview before external or costly actions.

output

Deliver

Return cited output, durable memory updates, and recovery paths.

Review Workflow

Use this when the agent reviews source material and produces a result that a person must trust, cite, or approve.

Collect source materialRead user-selected files, previous decisions, and current requirements.4 sourcesComplete
Project brief v3, Launch Policy v2, the support readiness checklist, and the prior review decision were read in full and pinned as citable sources.
Compare claims against evidenceCheck whether conclusions are backed by source excerpts.2 filesActive
Show touched sources, claim coverage, and unresolved gaps. Do not expose speculative hidden reasoning.
Prepare reviewable resultGenerate a summary only after the evidence pass finishes.Pending
The summary will cite every claim back to a pinned source and list unresolved gaps for human review before anything is sent.

Approval Workflow

Use this when the agent is about to change external state, spend budget, notify people, or publish an output.

Clarifying Workflow

Ask for missing product decisions in a structured way, with defaults visible and no conversational guesswork.

Question 1 of 3

Which source set should I prioritize?

The answer changes what the agent reads first.

Source-Backed Artifact

Turn an agent answer into a cited document that users can inspect after the conversation ends.

Requirements Coverage Report

Cited draft prepared from the brief and the support readiness checklist.

Reviewingv1

Sources

2 linked

Owner

Document Drafter

Updated

34s ago

Coverage

21 of the 23 requirements in the brief map to a named owner and review criterion.

Project-Brief-v3.pdf, §2

Open gaps

Needs source

Fallback behavior and cleanup behavior are not covered by any pinned source yet.

Next action

Draft

Confirm owners for both gaps with the project owner before the artifact is shared.

Memory Review

Show proposed memory before it becomes durable product context.

Preferred review format
Proposed

Use concise source-backed summaries for future review tasks.

Source: current session / Scope: this workspace / Expiry: 90 days

Background Run Monitor

Use this template when agent work continues after the user leaves the composer.

AgentStatusTaskProgressConfidenceCostUpdated

Source Collector

Gathers evidence

WorkingWorkingReading recent source material and extracting referenced decisions.
x
64%
88%$0.1812s ago

Requirements Mapper

Checks coverage

BlockedBlockedWaiting on product owner answer for unresolved launch scope.
x
52%
71%$0.1141s ago

Document Drafter

Prepares output

IdleIdleNo drafting until source checks are complete.
x
0%
n/a$0.002m ago

Multi-Agent Handoff

Make ownership transfer explicit so users can see who has the task and what context moved with it.

Source Collector prepared packetSources, open questions, and confidence notes were grouped.Packet v2Complete
Requirements Mapper accepted handoffThe receiving agent is checking whether the packet is enough to proceed.handoffActive
Handoff payloads should show sender, receiver, carried context, omissions, and the next expected action.

Agent Settings

Agentic products need durable controls, not only per-action prompts.

The agent must ask before sending, publishing, or modifying shared records.

Durable memory changes appear in a review queue before being saved.

Registry mapping

Settings templates compose shadcn Field, Switch, Decision Surface, and Reference Item instead of shipping as one rigid settings screen.

Templates are intentionally site-level guidance. The registry exports the smaller primitives underneath them so teams can adapt the workflow to their own product surface.