Sync Pstack
Set up the pstack plugin in a project through an interview, and keep every pstack...
Install
npx skills add udecode/dotai --skill sync-pstack -g -a claude-code -y- Repository
- udecode/dotai1.2k
- Category
- AI and agents
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Set up the pstack plugin in a project through an interview, and keep every pstack project on one pinned tag and one shared AGENTS.md overrides block. Use to set up or install pstack in a repo, sync, bump or update pstack everywhere, list which projects use pstack or have drifted, compare setups, audit a project's skills for drift from pstack (which to cut, fold or keep), change which work runs a panel, architect or an arena without asking (\"from now on X runs architect\"), or move a workflow lesson, including a plan page shape change, into every project. Not for choosing pstack's per-role models, which setup-pstack owns.
Sync pstack
One skill sets pstack up in a project and keeps every set-up project in step with upstream pstack and with one shared set of overrides. Project-only rules never sync.
Setup brings the shared layer: the plugin pin, the overrides block, its helpers, typed entry points kept for retired controllers, a routing table and a proof skill. It does not bring a project's own knowledge, such as its source authority, domain laws or review scenes; those stay the project's work, and the domain skills come through setup untouched.
Layers
| Layer | Lives in | Changed by |
|---|---|---|
| Upstream | The pstack@pstack-claude plugin at a pinned tag, in each project's .claude/settings.json, the user's ~/.claude/settings.json and the user's Codex marketplace | sync --tag and user-pin. pstack itself is never edited. |
| Shared | assets/block.md, rendered between the pstack:begin and pstack:end markers of each project's AGENTS.md, plus the helpers in assets/pstack/, copied to .agents/pstack/, and the rule files in assets/pstack/rules/, rendered like the block into .agents/pstack/rules/ | An edit to this skill's source in the dotai checkout, then a sync |
| Project | .agents/pstack.json, which holds the interview's answers, the project playbooks in .agents/playbooks/, which the block lists, and every rule outside the block, which wins over it | The project, by hand or through setup |
Run the script
Run node <skill>/scripts/sync-pstack.mjs <command> from any directory.
