SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsproject-intake

project-intake

Data & analytics

View repository

Updated 10-16 02:31

About this skill

Project Intake

Role

You are the handoffreceiver. Take over a project handed off by another agent/tool/new session:first read HANDOFF.md to restore context, then continue work according to its guidance. Symmetric with project-handoff(the handoff party)—the handoff party writes the delta, the receiver reads the delta.

When to use

  • Taking over a project handed off by another agent/tool (e.g., Cursor taking over a Deep Code project);
  • Starting a new session and needing to quickly restore project context;
  • The user says "continue the previous work", "pick up where we left off", "take over the project", "proceed according to HANDOFF".

Hard constraints (non-negotiable)

  1. Read first, then act—the first step of taking over is to locate and read HANDOFF.md (or the handoff document),starting work without reading is prohibited(it will duplicate exploration and miss the delta).
  2. Prevent dual sources—content already in HANDOFF should bereferenced, not copied; your new documents/notes must not copy HANDOFF content (only record your newly added delta).
  3. Desensitization—must not write/propagate API Keys/passwords/PII; obtain credentials from the user (or reference the storage location, without writing the value).
  4. Confirm before acting—only enter business verification after the environment readiness check passes; before making changes, first check the current state against the HANDOFF snapshot.

Workflow (7 steps)

- [ ] 1. 定位 HANDOFF.md（项目根；不存在则先读 README/docs 重建上下文，并提示交接方先生成）
- [ ] 2. 读 6 节：元信息（谁/为什么/建议动作）/ 快照（进度到哪——§2 最近完成是一行式 `- [hash] 一句话标题`，详情不足时 `git log`；过期周期见 `HANDOFF-ARCHIVE/cycles.md`，已修坑见 `pits.md`）/ 下一步（做什么/验证什么——§3 只应有未完成项）/
        即时操作（命令 + §4 未修/仍会踩的坑）/ 引用索引 / 维护规则（回填 + **确认修复即归档**：坑→`pits.md`，待办→`done.md`）
- [ ] 3. 复述上下文：向用户确认「当前状态 + 下一步」，核对无误再继续
- [ ] 4. 执行接收方建议动作（HANDOFF §1）：git init → .gitignore → 首次提交 / 读 tickets / 向用户索取凭据
- [ ] 5. 环境就绪检查（HANDOFF §3 首项）：构建通过 + 应用可启动（依赖已装则跳过重装）
- [ ] 6. 执行下一步验证点（对照 ticket AC 逐条跑）
- [ ] 7. 回填闭环：ticket 完成 → 勾选 AC + 标注文档引用兑现 → 同步更新 HANDOFF §2 快照 → 新的未修坑追加 §4 → **确认已修（或裁决不修）当次按类型迁 `HANDOFF-ARCHIVE/`（坑→`pits.md`，待办→`done.md`），不留在正文**

Anti-patterns

  • Starting work without reading HANDOFF—duplicate exploration, missed delta, misjudged progress
  • Copying HANDOFF contentinto your notes/new documents—causing dual sources
  • Business verification before the environment is ready—misjudging environment issues as business defects
  • Not backfilling after completion(ticket/snapshot)—HANDOFF becomes outdated, and the next receiver misreads it
  • Confirming a fix but not archiving it——§3 [x] / fixed pitfalls left in the main text, the handoff document only grows and never shrinks; symmetric with project-handoff : pitfalls→HANDOFF-ARCHIVE/pits.md, to-dos→done.md
  • Guessing credentials(searching code/config for Keys)—should ask the user or reference the storage location
  • Not checking the snapshot before changes—making decisions based on outdated state

Completion criteria

  • HANDOFF's 6 sections have been read and the context (status + next steps) restated and confirmed (when the one-line details in §2 are insufficient, check git log / HANDOFF-ARCHIVE/cycles.md; for fixed pitfalls check pits.md）
  • Recommended actions have been executed (git/.gitignore/read tickets/credential source clarified)
  • Environment readiness check passed (build + startup)
  • Verification points completed (against ticket AC)
  • Backfill completed (ticket AC checked + HANDOFF §2 snapshot synchronized + new unfixed pitfalls added to §4 + confirmed fixes have been migrated and archived）
  • HANDOFF content not copied; no sensitive information written

Methodology source (2026-08)

  • project-handoff (symmetric skill): the handoff party's 6-section structure → the receiver restores context according to the isomorphic 6 sections; maintenance rules (backfill/prevent dual sources/desensitization/archive upon confirmed fix) are shared in both directions
  • mattpocock handoff: The handoff document serves as the starting context for the next session—from the recipient's perspective, it is "read the document → continue"
  • NeonForge HANDOFF.md practice (2026-08-02): Deep Code → Cursor handoff—the recipient needs suggested actions (git init/.gitignore/read tickets/Key request) and environment readiness checks (recipient requirements discovered through 4 rounds of AI review)