aiwg Prompt模板

Simple Building Blocks

AIWG ships five primitive artifact types. All are plain text:

• Agents — specialized personas (Security Auditor, Test Architect) with a scoped toolset
• Skills — natural-language workflows the platform auto-invokes on trigger phrases
• Commands — explicit slash invocations (/flow-security-review-cycle)
• Rules — enforcement directives the platform loads into every session
• Behaviors — lifecycle hooks that fire on events (pre-write, post-session)

Each is a single .md file with YAML frontmatter. Nothing executes until an AI platform reads it.

Install & Deploy

```bash

Install globally

npm install -g aiwg

Deploy to your project

cd your-project aiwg use sdlc # Full SDLC framework (98 agents, 38 rules, 200+ templates) aiwg use forensics # Digital forensics & incident response (13 agents, 10 skills) aiwg use marketing # Marketing operations (37 agents, 87+ templates) aiwg use media-curator # Media archive management (6 agents, 9 commands) aiwg use research # Research workflow automation (8 agents, 8-stage pipeline) aiwg use rlm # RLM addon (recursive context decomposition) aiwg use all # Everything

Check installation health

aiwg doctor ```

Multi-Platform Deployment

aiwg use sdlc                          # Claude Code (default)
aiwg use sdlc --provider copilot       # GitHub Copilot
aiwg use sdlc --provider cursor        # Cursor
aiwg use sdlc --provider warp          # Warp Terminal
aiwg use sdlc --provider factory       # Factory AI
aiwg use sdlc --provider opencode      # OpenCode
aiwg use sdlc --provider openai        # OpenAI/Codex
aiwg use sdlc --provider windsurf      # Windsurf

Install into Claude Desktop

aiwg mcp install claude

Quick Start

Prerequisites: Node.js >=20.0.0 and an AI platform (Claude Code, GitHub Copilot, Cursor, Warp Terminal, or others). New installs should prefer Node 24. See Prerequisites Guide for details.

Verifying releases (v2026.5.3+): Every AIWG release ships with Sigstore-anchored npm provenance, a signed git tag, a cosign keyless tarball signature, and a signed CycloneDX SBOM. Verification is optional but recommended:

> npm view aiwg@2026.5.3 --json | jq .dist.attestations
> 

Full walkthrough at docs/releases/verifying.md. Adopt the same pattern for your own packages: docs/security/supply-chain-hardening.md.

Analyze writing patterns in a voice sample

/voice-analyze docs/existing-content.md

The Six Core Components

Resume interrupted pipeline

aiwg sdlc-accelerate --resume

Generates intake form, vision document, use cases, architecture baseline, risk register, test strategy, and deployment plan — all with human approval gates between phases.

**Dual-Track Iteration Model:**

Metrics & Quality Tracking:

Full curation pipeline

/curate "Pink Floyd"

Research Complete — Academic Research Pipeline

 ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
 │ DISCOVER │───▶│ ACQUIRE  │───▶│ DOCUMENT │───▶│ ARCHIVE  │
 │          │    │          │    │          │    │          │
 │ Search   │    │ Download │    │ RAG      │    │ OAIS     │
 │ databases│    │ PDF      │    │ summaries│    │ lifecycle│
 │ Rank     │    │ Metadata │    │ Citations│    │ FAIR     │
 │ results  │    │ extract  │    │ GRADE    │    │ W3C PROV │
 └──────────┘    └──────────┘    └──────────┘    └──────────┘

8-stage pipeline: Discovery → Acquisition → Documentation → Citation → Quality Assessment → Synthesis → Gap Analysis → Archival. Persistent REF-XXX identifiers. GRADE scoring (HIGH/MODERATE/LOW/VERY LOW). Unpaywall integration for open access papers.

---

MCP Server — Model Context Protocol Integration

AIWG includes a built-in MCP server for tool-based AI workflow integration:

```bash

Project scope (recommended) vs user scope (global)

aiwg use writes artifacts at one of two scopes. Both are first-class supported (see ADR-NUA-001 in .aiwg/studies/novice-user-adoption/):

• Project scope — default. Run aiwg use sdlc from a project root and the artifacts land in ./.claude/agents/, ./.claude/skills/, etc. One project's agent set never bleeds into another's session. This is the recommended default for most use cases.
• User scope (global install) — aiwg use sdlc --scope user writes to ~/.claude/agents/, ~/.claude/skills/, etc. Same artifact set loads into every session, regardless of project. Fits "AIWG in every conversation" workflows and is the canonical mode for OpenClaw and Hermes (whose primary discovery is user-scope).

The trade-off is real: when the same agent set loads into every session, context from one project can bleed into reasoning about another. Research (REF-720, Lost in Multi-Turn Conversation, MSR/Salesforce 2025) measured a 39% capability drop when this happens. The non-blocking project-isolation warning surfaces the trade-off at deploy time so the scope choice is informed. Neither scope is wrong; pick the one that fits the workflow.

See docs/cli-reference.md (under aiwg use → "Scope models") for the per-provider details and the global-install rough-edge inventory.

Claude Code Plugin (Alternative)

/plugin marketplace add jmagly/ai-writing-guide
/plugin install sdlc@aiwg

Detect AI patterns and suggest authentic alternatives

/ai-pattern-detection docs/generated-content.md ```

---

Installation Troubleshooting