Specs to install. Work to share.
A spec says what software should do. A spec package holds one, with the skills and playbooks built from it, so AI agents can install and follow it. A group holds a project's records — its specs, decisions and agent sessions — and shares them with the people you work with. Both live here.
Install from the Spex app: open Playbooks, search, Add. Publish from the app, or with the API (guide for agents).
Packages
Browse and install specs, skills and playbooks — no account needed. Publish your own from the Spex app with a GitHub or GitLab sign-in and a claimed org.
Groups
Keep your projects’ records — specs, decisions and agent sessions — with the people you work with. Spex keeps them in your groups; this site lets you browse them.
Recently published
| Package | Version | Description |
|---|---|---|
| claude-workshop-261011/release-notes | 0.1.0 | Writes client-facing release notes for a milestone build, reviews them against the commits, and commits RELEASE-NOTES.md once the account lead approves |
| claude-workshop-261011/release | 0.1.0 | Deploy gate — assemble a release evidence bundle for a change, have the board delegate review it, and ask the owner to approve its release |
| claude-workshop-261011/compliance | 0.1.0 | 部署前合规检查：合规专员按固定清单检查指定 commit 并提交记录，整改人修正不通过项，最多两轮 |
| claude-workshop-261011/promote | 0.1.0 | Decide a change's promotion to staging or production from its eval report, gated by review and the owner's approval |
| claude-workshop-261011/release-review | 0.1.0 | 发布评审：整理候选版本的发布评审记录，按发布准入条件最多评审两轮，由负责人批准或暂缓发布 |
| claude-workshop-261011/incident | 0.1.0 | Turn an on-call incident report into a Lead-reviewed incident record and an intent record for the fix |
| claude-workshop-261011/rollout | 0.1.1 | Canary rollout plan for one change — ReleaseEngineer plans and dry-runs, SRE reviews, owner approves |
| claude-workshop-261011/verify | 0.1.1 | V 模型验证规程——Tester 为每个规约条目补齐可执行测试并提交追溯矩阵和测试报告，Auditor 审核至多两轮 |
| claude-workshop-261011/trip-split | 0.1.0 | Trip expense splitting — the spec of the tripsplit-core library, for teams recasting it in another language |
| claude-workshop-261011/rollout | 0.1.0 | Canary rollout plan for one change — ReleaseEngineer plans and dry-runs, SRE reviews, owner approves |
| claude-workshop-261011/sprint-plan | 0.1.0 | 迭代计划：产品分析师把产品经理的史诗拆分为三到七条意图记录，经技术负责人审查后一次提交 |
| claude-workshop-261011/evaluate | 0.1.0 | Evaluate a change against agreed metric thresholds and the main baseline, commit the eval suite and report, and review them |
| claude-workshop-261011/requirements | 0.1.0 | 需求阶段规程：需求分析师按 GEARS 编写需求条目与意图记录，评审专家正式评审至多两轮，结束后连同评审记录一次提交 |
| claude-workshop-261011/verify | 0.1.0 | V 模型验证规程——Tester 为每个规约条目补齐可执行测试并提交追溯矩阵和测试报告，Auditor 审核至多两轮 |
| claude-workshop-261011/shape | 0.1.0 | Shape a founder request into one reviewed intent record and its spec items, committed together |
| claude-workshop-261011/contrib | 0.1.0 | Implement an issue on its own branch, review it in up to two rounds, and open a pull request |
| claude-workshop-261011/design | 0.1.0 | Turn an agreed feature brief into a client-reviewed decision record and GEARS spec items, committed only on the account lead's sign-off |
| claude-workshop-261011/propose | 0.1.0 | Turn a change request into a risk-classified intent record reviewed by a Risk Officer for the CAB |
| claude-workshop-261011/prototype | 0.1.0 | 把策划的玩法想法做成可试玩的最小原型并提交，不做代码审查 |
| slbeta1/hello-notes | 0.1.0 | A tiny spec package for the acceptance walk. |