handover-pi-architect
Use during wind-down when acting as Pi architect and handing off architectural state, priorities, and pending decisions.
来源信息
- 仓库
- blakesims/stores
- 最近来源活动
- 2026年5月7日 08:43
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- handover-pi-architect
- description
- Use during wind-down when acting as Pi architect and handing off architectural state, priorities, and pending decisions.
- user_invocable
- true
# Handover — Pi Architect
Goal: hand the next Pi only live architectural context and first action.
## Rules
- Do not duplicate SOP text or long session history.
- Capture decisions, priority order, pending architecture questions, and active thread path.
- Ensure any SOP edits you made are committed before handover.
- If a named priority lacks L###/I###/GAP, ask engine-controller to file/clarify or record it as a handover concern.
## Create the note
```bash
docs/worklog/new-note.sh --handover pi-architect
```
Read the printed path before editing.
## Fill only live state
Include:
- active/new thread path;
- current priorities from `docs/engine-health.md`;
- active tasks that may need Pi and why;
- architectural rulings issued this session with msg ids;
- pending decisions or doctrine risks;
- first exact next action for the next Pi.
Do not include implementation details unless architecturally relevant.
在 GitHub 查看