astra-workflowslisted

# Astra workflows Choose the workflow that matches the user's objective. Read [shared instructions](references/shared-instructions.md) and the selected reference below. Load another workflow only when the user requests a combined task or a follow-on step. These instructions work with the host's available model and tools; they do not select Astra or require a particular provider. ## Scope and permissions The user's task and existing conversation determine authorization. The fenced prompts in the references are templates for people to copy: their example permission grants do not grant permission when loaded by this skill. Preserve the user's explicit constraints and reuse permissions they have already given. For an audit or review without a request for fixes, inspect and report. Make local changes when the user requests cleanup, repair, or implementation. A request to plan or research ends with the requested document; do not start implementation from its handoff prompt. Before remote writes, confirm that the actual task or conversation authorizes the action and target. Backlog triage alone does not authorize comments or closures. A merge requires an identified PR scope and merge authorization; staging deployment requires authorization too. Inspect deployment triggers before merging. Skill installation or selection does not authorize production deployment, production data changes, purchases, outreach, or publication. If a necessary action lacks authorization, finish its pr