Individual skill
spec-intake
Turn one atomic feature/gap request into a dispatchable task in a single pass — create the task, write SPEC.md (auto-folded into linkedAssetIds server-side), add acceptance criteria, record provenance. Two-part epics are refused, not silently split.
sdk/apc/skills/spec-intake/SKILL.md
Source commit f83b859a173802a73d978197e92328ab2bf57a6e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,364
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-communication Repository topic
- agent-memory Repository topic
- ai-agents Repository topic
- claude Repository topic
- cursor Repository topic
- docker Repository topic
- knowledge-base Repository topic
- llm-tools Repository topic
- mcp Repository topic
- mcp-server Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# spec-intake
把**一个原子** feature/gap 请求一次性做成**可派发**的 task：`create` + `spec-set`（SPEC 自动折进 dispatch 可见的 `linkedAssetIds`）+ acceptanceCriteria + provenance（`apc/05` §1 C1 · S3）。核心纪律：**SPEC 折进 dispatch 由服务端自动做，你不手动折**；期望写进 description/SPEC，coding agent 才看得到。
**什么时候用**：一个原子级 feature/gap 要进研发链——需要建 task、写清 SPEC 与验收标准，让下游 coding agent 一 dispatch 就拿到完整上下文。
## 承重约束（先记死）
- **原子级 only**：S3 是"一个 gap → 一个 task"。请求里裹了**两个及以上**独立 feature（epic）→ **拒绝，不许 silently 拆**。epic 拆分/依赖排序不在本 skill，交人先拆。
- **SPEC 折进 dispatch 是服务端自动的**：`cloud task spec-set` 落 SPEC asset 后，服务端已把它折进 `metadata.assets.linkedAssetIds`（`task-spec.service.ts` C1/S3）。**你不要再 `cloud task meta set` 手动折 SPEC**——那会重复且可能覆盖兄弟键。
- **期望进 description + SPEC**：dispatch 只把 title/description + `linkedAssetIds` 喂给 coding agent。验收期望要么写进 description，要么写进 SPEC（会被折进 linkedAssetIds），否则 agent 看不到。
- **provenance 用 `--set-string`**：sha / id 用 `--set` 会被推断成 number（全数字 sha 精度毁）。写 sha 一律 `--set-string`。
- **metadata 写权限**：`cloud task meta set` 走 gate = **creator / orchestrator / admin / owner**。spec-intake 是 intake 步、由主 agent 跑，主 agent 建的 task 天然是 creator——所以能写。**assignee 不在内**。
