// Display workspace status dashboard showing installed frameworks, deployments, artifact counts, and health indicators
| name | aiwg-status |
| description | Display workspace status dashboard showing installed frameworks, deployments, artifact counts, and health indicators |
| platforms | ["codex"] |
You display a comprehensive workspace inventory dashboard: registry-installed frameworks and addons with versions, deployed provider artifact directories, project-local bundles, .aiwg/ artifact counts by subdirectory, last sync time, and overall health indicators.
This skill is for workspace inventory / install health. It is not the cross-framework project status aggregator. If the user asks for project-status, "where are we?", "what is next?", or SDLC project progress, route through aiwg discover "project status" and load the project-status skill instructions instead.
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
| Pattern | Example | Action |
|---|---|---|
| Full status | "show workspace status" | Run aiwg status |
| Quick health | "is my workspace healthy?" | Run aiwg status |
| Framework inventory | "what frameworks are installed?" | Run aiwg status |
| Artifact counts | "how many requirements do I have?" | Run aiwg status |
| Deployment check | "what's deployed to copilot?" | Run aiwg status |
| Project progress | "project-status" / "where are we?" | Do not run aiwg status; use aiwg discover "project status" then aiwg show skill project-status --first |
When triggered:
Distinguish from doctor:
status is a read-only summary — it reports current state without running active checks or attempting repairs.doctor runs active health checks and can suggest or apply fixes.doctor. When they ask "what do I have?", prefer status.project-status / project-health-check, not this workspace inventory command.Run the command:
# Full status dashboard
aiwg status
What the dashboard shows:
.aiwg/frameworks/registry.json (name, version, install date).claude/, .github/, .cursor/).aiwg/{extensions,addons,frameworks,plugins}/.aiwg/ artifact counts per subdirectory (requirements/: 4 files, architecture/: 2 files, etc.)Report the result — present the dashboard output inline; highlight any WARN or ERROR indicators.
User: "Show me the workspace status"
Extraction: Full status request
Action:
aiwg status
Response:
AIWG Workspace Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Installed Frameworks (registry)
sdlc-complete v2026.3.15 installed 2026-03-20
aiwg-utils v2026.3.15 installed 2026-03-20
voice-framework v2026.3.15 installed 2026-03-20
Provider Deployments
claude-code .claude/ agents: 58 commands: 42
copilot .github/ agents: 58 prompts: 42
Project-local Bundles
extensions 1 (agent-ops-control)
.aiwg/ Artifacts
intake/ 2 files
requirements/ 7 files
architecture/ 3 files
planning/ 2 files
risks/ 1 file
testing/ 4 files
security/ 1 file
deployment/ 0 files
working/ 5 files (temporary)
reports/ 2 files
Last sync: 2026-03-28 14:32 UTC
Health: OK
User: "How is my workspace?"
Extraction: Health summary request
Action:
aiwg status
Response: Reports status dashboard as above, but with Health: WARN — sdlc-complete may be outdated (last sync 8 days ago). Run \aiwg sync --dry-run` to check.`
User: "How many requirements files do I have?"
Extraction: Artifact count question; status provides this summary
Action:
aiwg status
Response: Points to the .aiwg/ Artifacts section of the output: "You have 7 files in requirements/."
User: "What's installed?"
Extraction: Framework inventory request
Action:
aiwg status
Response: Shows the Installed Frameworks (registry), Provider Deployments, and Project-local Bundles sections. If nothing is installed yet: "No frameworks installed. Run aiwg use sdlc to deploy the SDLC framework."
If the user's intent is ambiguous:
aiwg status), active diagnostics (aiwg doctor), or project progress (project-status)?"status command handlerAIWG project issue filing only — templates, environment capture, duplicate detection, and import flow for AIWG tracker reports; not for general issue audits or address-issues processing
AIWG addons + extensions language map — categories, curated discover phrases, and per-bundle pointers covering everything beyond the framework quickrefs
Regenerate platform context file with preserved team directives
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.
AUTO-INVOKE when user mentions cryptography, AEAD, KDF, chain of trust, signing key, auth factor, MFA, secret hygiene, supply chain trust, physical threat. Security-engineering quick reference — decision domains for crypto primitives, chain-of-trust, auth factors, degraded modes, supply-chain trust, physical-threat modeling.