Agently Skills

---
name: agently
description: Route ambiguous product, document, or Agentic work to the right design or implementation skill. Use for unresolved owner/project shape, mixed specialties or explicit low-frequency TaskDAG or DynamicTask requests. Clear tasks use their specialist directly; conversation expression, progress and handoffs use agently-collaboration alongside any task.
---

# Agently

Start here when the owner or working method is unclear, or several specialties
share one work item. First distinguish human product/document outcomes from
model-service behavior. Route clear product work directly to `agently-product-design`;
no model, Agently runtime or framework migration is required. For model systems,
choose the smallest suitable owner before files or mechanisms; use Agently-native
mappings only when Agently is in scope. Respect another selected stack.

When an Agently developer needs to understand model-node duties, tune execution
effects, check data flow or redundant context, or judge model/Host ownership,
use collaborative review without waiting for the phrase "Prompt review".
Route through `agently-agentic-design` for the highlighted flow and handoffs, and
`agently-request` for related Prompt tables grouped by readability and dependency.
Keep unrelated mechanical work outside this review method.

## Shared coordination

Use [Conversation and Collaboration](../agently-collaboration/SKILL.md) alongside
any task for reader-oriented communication, progress, decisions and handoffs.
It can be selected directly without this router. Specialist Skills retain their
execution and acceptance criteria; reuse one work record across them. If the
companion is unavailable, follow the host's base guidance and existing task
record; routing does not require installation or a new tracking system.

## Workflow

The following owner workflow applies to model-powered systems. For non-model
product or writing tasks, route to the product Skill and continue its method.

1. Reduce the request to goals, inputs, outputs, side effects, evidence, and
   lifecycle needs.
2. Separate model-owned semantic decisions from host-owned validation,
   authorization, identity joins, arithmetic, and effects.
3. Assign each decision, state, and effect to one existing owner.
4. For non-trivial flows, map nodes, value/event edges, invariants, and the
   production need for every requested field and stage.
5. Implement async-first where the caller owns an async boundary; validate
   deterministic contracts separately from model-owned quality.
6. Report a framework gap when no native owner can carry a required invariant.
   Do not hide the gap behind business-specific glue or a pass-through facade.

## Route by Owner

- Product goals, role/behavior coverage, interface/component/layout design,