/aiwg-utils-quickref

name: aiwg-utils-quickref
namespace: aiwg
platforms: [all]
kernel: true
description: AUTO-INVOKE for ANY AIWG capability question, framework/addon/extension query, steward routing, MCP profile, or when unsure where to start. ALWAYS consult before filesystem search on .claude/.factory/.codex/.warp/etc. AIWG core utilities quick reference — always-on framing, steward, index, meta operations.
triggers:
  - "i do not know what AIWG has"
  - "translate my goal into AIWG search terms"
  - "run two or three aiwg discover searches"
  - "capability discovery"

AIWG Core Utilities — Quick Reference

This is your always-loaded core directory for AIWG. It does **not** list every utility skill. Instead, it teaches the cross-cutting domains and gives you **curated search phrases** that map to `aiwg discover` lookups, plus a list of which framework-specific quickrefs are loaded.

How to use this quickref

`aiwg show <type> <name>` returns a metadata card. Inspect its outline, then fetch a needed `--section "Heading"` or use `--body` for the full instructions. Fetch required rules with `--rules --with-rule-bodies` before governed work.

Routing authority: `aiwg show rule skill-discovery --body` (kernel). Skill/CLI precedence: `aiwg show rule cli-secondary --body`. The capability phrases below are lookup aids.

Framework quickrefs (loaded if framework is installed)

If a user asks about a specific framework's surface, the corresponding quickref is your first stop. These are kernel-resident, so they're already in your context:

• `sdlc-quickref` — software-development-lifecycle workflows
• `forensics-quickref` — incident response and digital forensics
• `research-quickref` — research corpus and citation workflows
• `media-curator-quickref` — media archive management
• `marketing-quickref` — marketing operations and campaigns
• `ops-quickref` — operational infrastructure and runbooks
• `security-engineering-quickref` — applied security and crypto decisions
• `knowledge-base-quickref` — wiki and documentation workflows

If a quickref isn't loaded, the framework isn't installed in this project. Use `aiwg list` to confirm.

Addons & extensions (separate kernel quickref)

For everything **outside the framework set** — the ~214 skills across 29 addons (loops, voice, memory, color, testing, NLP, etc.) and 7 ops extensions (sys/net/sec/dev/it/stream/api-adapter) — load `aiwg-language-map`. It's also kernel-resident and acts as the orientation layer for the addon/extension surface, with curated discover phrases per capability domain.

aiwg-language-map  → addon capability domains + extension domains + cheat sheet

Self-maintenance kernel (always loaded)

These ops **skills** are kernel-resident — already in your context regardless of `aiwg discover`. They are your primary surface for self-maintenance. Each skill carries the priming the bare CLI cannot — pre-flight checks, dry-run preview, preservation logic, recovery patterns.

> **Skills first, CLI second.** Each row below shows what the skill is for and the CLI command it calls under the hood. Invoke the skill — let it call the CLI. Direct CLI invocation skips the priming and is acceptable only on the discovery surface (Rule 2 of `cli-secondary`). See [`cli-secondary` rule](../../rules/cli-secondary.md) for the full policy.

| Skill (preferred) | Purpose | CLI it wraps | |---|---|---| | `steward` | Provider capability awareness + command routing | (no single CLI — orchestrates several) | | `aiwg-doctor` | Installation health check + remediation | `aiwg doctor` | | `aiwg-refresh` | Update CLI + redeploy frameworks with dry-run preview | `aiwg refresh` (alias: `aiwg sync`) | | `aiwg-regenerate` | Regenerate AIWG.md + AGENTS.md preserving team directives | `aiwg regenerate` | | `aiwg-status` | Workspace status dashboard | `aiwg status` | | `aiwg-help` | List CLI commands, args, examples | `aiwg help` | | `aiwg-issue` | Filing AIWG project issues (template, env, duplicate detection) | (no single CLI) | | `aiwg-pr` / `aiwg-delivery-pr` | AIWG-specific delivery PRs only (delivery-policy, no-attribution, CI gate); not generic repository PR work | (no single CLI) | | `use` | Deploy a framework or addon with validation gates | `aiwg use <name>` |

Pair with the `aiwg-steward` agent (always-deployed) for orchestrated repair: health check → refresh → re-doctor.

**Discovery commands stay direct** — `aiwg discover`, `aiwg show`, `aiwg list`, `aiwg version`, `aiwg runtime-info`, status/info subcommands. They have no paired "priming skill" because they ARE the priming entry points.

Session handoff

"handoff", "hand off to a new session", or "prepare a handoff" → `checkpoint` skill (`aiwg show skill checkpoint --body`), `--handoff` flow: `aiwg checkpoint create --handoff --name <n> --scope <scope> --todo <task> --constraint <rule> --artifact <path>`. Resume with `aiwg checkpoint recover <n>`.

Status intent disambiguation

Route these phrases carefully:

| User intent | Use | |---|---| | Workspace inventory, installed frameworks, deployed provider files | `aiwg-status` / `aiwg status` | | Cross-framework project progress, "project-status", "where are we?", "what is next?" | `aiwg discover "project status"` → `aiwg show skill project-status --body --first` | | SDLC-specific project health or lifecycle gate status | `aiwg discover "SDLC project health check"` and prefer `project-health-check` or `orchestrate-project` when those rank above generic workspace inventory |

Do not answer `project-status` by running only `aiwg status`; that command reports workspace install/deployment inventory, not project progress.

When a user wants to **file an AIWG product issue or open an AIWG delivery PR**, route them through `aiwg-issue` / `aiwg-pr` (or the explicit alias `aiwg-delivery-pr`) first. These are AIWG-specific kernel skills and reference `steward-prep-delivery` where applicable.

For generic repository PR work, use ordinary repository PR tooli