القائمة
Session-end handoff writer. Use at end of a session to update HANDOFF.yaml with completed work, new gaps, and current project state.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | hj-handoff |
| description | Session-end handoff writer. Use at end of a session to update HANDOFF.yaml with completed work, new gaps, and current project state. |
Write HANDOFF.yaml with completed work, new gaps discovered, and current project state.
| File | Location | Committed | Purpose |
|---|---|---|---|
HANDOFF.<project>.<base>.yaml | repo root | yes | Tasks, items, log — doob source of truth |
.ctx/HANDOFF.state.yaml | .ctx/ | no | Build/tests/branch snapshot |
.ctx/HANDOFF.md | .ctx/ | no | Generated reference doc |
.ctx/ must be in .gitignore. Never commit anything under it.
git branch --show-current
git log --oneline -5
cargo check 2>&1 | tail -3
cargo nextest run 2>&1 | tail -5
handoff-detect # path if exists; expected path + exit 2 if not
handoff-detect --name # expected filename
Naming: HANDOFF.<project>.<cwd-basename>.yaml
id (no doob_uuid yet)status: done, add completed: <today>status: blocked, append extra entry with type: blockertitle, description, priority, or files on existing itemslog — prepend a new entry (newest first), one line, past tense, with commit hashesupdated — set to todayupdated: <YYYY-MM-DD>
branch: <git branch>
build: clean | failing | unknown
tests: "<N passing>" | "failing: N" | "unknown"
notes: <one-line or null>
doob handoff sync --file <path-to-HANDOFF.yaml>
git add HANDOFF.yaml
git commit -m "docs: update handoff"
Stage only HANDOFF.yaml. Never stage anything under .ctx/.
| Priority | Meaning |
|---|---|
| P0 | Broken, blocked, security, data loss |
| P1 | Known fix, clear scope, safe to execute |
| P2 | Safe to delegate, well-understood |
Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.
Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.
Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".
Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.
Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.
Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.