agently-langchain-langgraph-migration-playbook
Agently LangChain LangGraph Migration Playbook
This skill is the top-level routing entry point for migration work from LangChain or LangGraph into Agently. Use it when the request starts from an existing LangChain or LangGraph codebase, concept, or architecture rather than an Agently API. It helps choose the right migration path and the right Agently skill combination. It does not replace the implementation skills themselves.
Prerequisite: Agently >= 4.0.8.5.
Scope
Use this skill for:
- deciding whether the source design is mainly LangChain-side or LangGraph-side
- deciding whether the migration target should stay one request, become a multi-agent design, or become TriggerFlow orchestration
- choosing the correct migration skill and implementation order
- identifying which parts can map directly and which parts require redesign
Do not use this skill for:
- direct Agently API implementation details
- one isolated LangChain or LangGraph feature with no migration-design question
More from agentera/agently-skills
agently-playbook
Use when the user wants to build, initialize, validate, optimize, or refactor a model-powered assistant, internal tool, automation, evaluator, or workflow from a business scenario or common problem statement, including project-structure refactors or starter skeletons that may separate model setup, prompt config, and orchestration, even if the request also mentions a UI, app shell, or local model service such as Ollama, and it is still unclear whether the solution should stay a single request, add supporting capabilities, or become orchestration. The user does not need to mention Agently explicitly.
40agently-prompt-management
Use when the user is shaping how one model request or request family should be instructed or templated, including prompt slots, input/instruct/info layering, mappings, recursive placeholder injection, prompt config, YAML or config-file-driven prompt behavior, and reusable prompt structure.
40agently-model-setup
Use when the request is already narrowed to wiring a model endpoint, env vars, settings-file-based model config, `${ENV.xxx}` placeholders, `auto_load_env=True`, or connectivity check for a model-powered feature, including local Ollama, dotenv-loaded DeepSeek or other OpenAI-compatible settings, plugin namespace placement, auth, request options, and minimal verification.
40agently-langchain-to-agently
Use when a migration is already known to stay on the LangChain agent side, including agent setup, tools, structured output, retrieval, and short-term memory.
38agently-triggerflow
Use when the user needs workflow orchestration such as branching, concurrency, approvals, waiting and resume, runtime stream, restart-safe execution, mixed sync/async function or module orchestration, event-driven fan-out, process-clarity refactors that make stages explicit, performance-oriented refactors that collapse split requests, or workflow definitions and chunk-level runtime metadata that must stay visible for debugging and visualization. The user does not need to say TriggerFlow explicitly.
38agently-output-control
Use when the user wants stable structured fields, required keys, reliable machine-readable sections, or downstream-consumable output from one model request, including prompt-config-owned output contracts, `.output(...)`, field ordering, `ensure_keys`, and structured streaming.
38