
create-adsk

Adopt agent skills, Cursor commands, and team profiles — versioned in your repo. Not a skills marketplace.
(create-adsk applies an ADSK profile: skills via the skills CLI plus optional Cursor commands/rules.)
Quick Start
Interactive
npx create-adsk
Follow the prompts. You pick a profile (kit depth), optionally select packs (product-value-loop, engineering-methods), then the CLI installs skills, syncs Cursor commands when the profile includes them, and writes .adsk/config.json.
Profile skills are first-party ADSK (include evals/). Packs install upstream skills as those authors ship them — often without an ADSK-style evals/ folder. Details: docs/using-adsk.md.
core | Spec-driven workflow + Cursor commands |
delivery | Core + solution architecture + DevOps strategy + release automation |
maintainer | Delivery + skill/README/PR authoring + supply-chain gate + stock rules |
skills-only | All first-party skills; no .cursor/ writes |
Source: profiles.json. Contract: docs/product/create-adsk.md.
Non-interactive
npx create-adsk --profile delivery --yes
--profile <id> | Choose a profile without prompting |
--yes / -y | Skip prompts (core if --profile is omitted; packs off unless --packs / --with-optional-packs) |
--packs <ids> | Comma-separated pack IDs (e.g. engineering-methods) |
--with-optional-packs | Include all packs |
See npx create-adsk --help for the full option list.
Commands
npx create-adsk
npx create-adsk update
npx create-adsk status
Other useful flags: --dry-run, --scope project|global, --force-rules, --target <dir>. Pack docs: docs/engineering-methods.md, docs/product-value-loop.md.
Org rules: put company policy in .cursor/rules/org-*/ in the app — update does not overwrite those folders. Avoid --force-rules unless you intend to reset stock rules. Guide: docs/customizing-org-rules.md.
Two tools
npx skills | Skill folders in .agents/skills/ |
npx create-adsk | ADSK profile (skills + Cursor + .adsk/config.json) |
Local kit path (optional)
Developing against a checkout instead of the published package:
npx --yes /path/to/agentic-development-starter-kit/packages/create-adsk
(npx --yes skips the npx install prompt for that path — not the same as create-adsk --yes.)
Develop in this monorepo
./scripts/prepare-create-adsk-snapshot.sh
cd packages/create-adsk && npm install && npm test && npm run build
node dist/cli.js --help
Releases (kit vs npm)
Kit GitHub releases (v*) and this npm package are independent.
| Land code on GitHub | PR → green tier1 → merge to main |
| Kit changelog / GitHub Release | Merge the release-please PR when ready |
New npx create-adsk on npm | Bump package.json version on main, then tag create-adsk-vX.Y.Z |
Full workflow: docs/RELEASE.md. Publishing uses Trusted Publishing via .github/workflows/publish-create-adsk.yml.