Agently Playbook

Use this skill first when the request still starts from business goals, refactor goals, product behavior, or broad model-app language.

The user does not need to say Agently, TriggerFlow, or any other framework term. Generic asks such as "build an assistant", "help me design an internal tool", or "create a validator for common problems" should still start here when the owner layer is unresolved.

Requests that also mention a UI, a web page, a desktop shell, or a local model service such as Ollama should still start here when the request is fundamentally about shaping a model-powered tool rather than only wiring one narrow capability.

Workflow

1. Reduce the request into scenario and atomic goals.
2. If the request is a project initialization or structure refactor, choose the owner layers and repo skeleton first.
3. Choose the narrowest native Agently capability path.
4. Name the concrete operations or primitives that should be used.
5. Name the validation rule that proves the design stayed native-first.

Capability Routing

• model provider setup, settings-file-based model separation, or ${ENV.xxx}-backed settings loading -> agently-model-setup
• request-side prompt design, prompt placeholder injection, or config-file prompt bridge -> agently-prompt-management
• output schema and reliability -> agently-output-control
• response reuse, metadata, or streaming consumption -> agently-model-response
• session continuity or restore -> agently-session-memory
• tools, MCP, FastAPIHelper, auto_func, or KeyWaiter -> agently-agent-extensions
• embeddings, KB, or retrieval-to-answer -> agently-knowledge-base
• branching, concurrency, waiting/resume, mixed sync/async orchestration, event-driven fan-out, process-clarity refactors, runtime stream, or explicit multi-stage quality loops -> agently-triggerflow
• migration choice between LangChain and LangGraph -> agently-migration-playbook

Anti-Patterns

• do not skip this playbook when the owner layer is unresolved
• do not invent custom output parsers, retry loops, or orchestration first
• do not split project initialization into a fake standalone framework surface before the owner layers are chosen
• do not treat multi-agent, judge, or review flows as separate framework surfaces before checking native Agently capabilities

Read Next

• references/capability-map.md
• references/project-framework.md