jmagly

Aiwg Web3 — Development skill for Claude Code

Development community

Opt-in AIWG Web3 lifecycle framework and generalization roadmap.

How to install Aiwg Web3

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jmagly/aiwg-web3 and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Aiwg Web3 does

Opt-in AIWG Web3 lifecycle framework and generalization roadmap.

Alternatives in Development

Claude Skills Roadmap — Claude Skills Roadmap skill 8.3k ★
Outcome Roadmap — Transform output roadmaps into outcome-focused strategic plans 7.8k ★
Ars Revision Coach — ARS academic-paper revision-coach mode — Revision Roadmap + Response Letter Skeleton 4.5k ★

README

AIWG Web3

An independently versioned, opt-in AIWG framework for the Web3 application and operations lifecycle.

**Status: development framework.** The lifecycle, intake skill, NFT release steward and release skills, package wrapper, tests, and implementation backlog exist. Chain/provider execution adapters and the other generalized specialist modules remain tracked work. Packaging success does not establish production readiness.

Canonical engineering tracker: https://git.integrolabs.net/roctinam/aiwg-web3/issues Distribution repository (currently private): https://github.com/jmagly/aiwg-web3

Use on demand

Use AIWG 2026.9.12 (the version tested during scaffold creation) and Git access to the chosen repository. Select a reviewed immutable commit; no release tag is claimed yet.

aiwg install https://github.com/jmagly/aiwg-web3.git \
  --ref  --package web3-distribution \
  --project-local --deploy --provider claude

For Codex, substitute `--provider codex`. The Gitea remote is `https://git.integrolabs.net/roctinam/aiwg-web3.git`; use an identical verified commit. Private repositories require authenticated Git access. Installation without a publisher signature provides integrity-only status; signed releases remain a tracked deliverable.

Develop and package

python3 scripts/validate.py
python3 tests/test_nft_release.py
aiwg package-plugin web3-distribution --dry-run
aiwg package-plugin web3-distribution --provider all --output dist/plugins

Canonical framework content lives in `.aiwg/plugins/web3-distribution/payload/`. The wrapper owns delivery; its payload is `type: framework`. There is one content source, with no fork of AIWG core or copied provider deployment trees.

See [design](docs/design.md), [roadmap](docs/roadmap.md), [source audit](docs/source-audit.md), [distribution](docs/distribution.md), and [references](docs/references.md).

The NFT release module begins with `nft-release-plan`, then routes through con