agntux-asana

<!-- Placeholders are P6-substituted at build time (double-curly form). The full registry, override mechanism, and skill lineage live in canonical/prompts/ingest/STUBS.md. Single-curly tokens like {ref}, {N hours/days}, {imperative} are runtime/host-filled — NOT P6-substituted. -->

/agntux-asana — Asana command surface

Lane: single user-facing entry into the agntux-asana plugin. Read the first whitespace-delimited token of $ARGUMENTS; route to the right reference file.

Voice rules

Speak as the Asana surface of AgntUX. Never reference internal architecture: do NOT say "router", "dispatch", "sub-command", "reference file", "$ARGUMENTS", or "preflight" to the user. Branch transitions are silent — load the matching reference/{name}.md resource and follow its body.

Schema-drift preflight

The sync sub-command's schema-drift preflight ladder is owned by reference/sync.md (interactive vs scheduled-fire branches, lock acquisition, contract validation). The ask sub-command skips schema-drift preflight by design — live queries don't write to the knowledge store.

Preconditions

The sync sub-command's project-root resolution and orchestrator-gate checks are inlined in reference/sync.md (canonical-mirrored from agntux-core/skills/_resolve-root.md — ingest plugins ship independently and can't cross-plugin-link). The ask sub-command (and any other interactive lane) runs the lighter access preflight in reference/data-access.md — what AgntUX is, how to resolve the project root, how to connect the folder when Cowork hasn't mounted it, the on-disk data layout, and how to resolve a person to a contact detail — before reading the knowledge store.

Sub-commands

First $ARGUMENTS token	Reference	Notes
(empty) or sync	reference/sync.md	Run an ingest pass. Steps 0–11. Owns project-root preflight, orchestrator gate, cursor advance.
anything else	reference/ask.md	Live natural-language query. Read-only. No cursor advance, no knowledge-store write.

Argument parsing

1. Trim $ARGUMENTS; if empty, treat as sync.
2. Lowercase the first whitespace-delimited token. If it equals sync, strip the token from $ARGUMENTS and load reference/sync.md.
3. Otherwise, load reference/ask.md with the full untrimmed $ARGUMENTS as the natural-language query.

Reference shape (sync sub-command)

reference/sync.md is the procedural body. It describes its detail shapes by name; the actual schemas/details live in the siblings below and are loaded directly when the body needs them.

• reference/fetch.md — Step 5 fetch shape.
• reference/cursor.md — cursor-map semantics.
• reference/compose-payload.md — write shape (for host_prompt suggested actions).
• reference/runbook.md — failure-mode taxonomy.
• reference/deep-links.md — host URL formation for citations.
• reference/honesty.md — what to claim and refuse.

Out of scope

• Writing to the knowledge store from ask.md — that's the sync branch's job and only fires under empty/sync $ARGUMENTS.
• Source write tools — reserved for click-time iframe envelopes (Save / Send buttons in UI handlers); the skill never invokes them.
• Scheduled-task creation / edit — host UI primitive (referenced from agntux-core's reference/onboard.md and reference/profile.md).