بنقرة واحدة
resume-engagement
Resume from engagement_state.json. Use when continue client, pick up books, or where we left off.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Resume from engagement_state.json. Use when continue client, pick up books, or where we left off.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Default for throw-work: dump a folder, "do the accounting", "sort my books", year end, prepare financial statements / MPERS pack without naming a stage. One intake then books; resumes from engagement_state.json. Depth-scoped done.
Human pack (HTML board) plus statements when depth needs them. Use when presenting books, opening the pack, or drafting FS/notes from adjusted TB.
Prove the job for this engagement depth (books scorecard or full QC).
Optional router if lost — which slash to use. Prefer saying do the accounting.
Scaffold clients/<slug> folder layout. Use when new client folder or workspace layout. Also the shelf step: organize scattered docs by entity and period before extract (see shared/shelf-first.md).
Firm profile cold-start (not a client dump). Use when set up the firm or first install.
| name | resume-engagement |
| description | Resume from engagement_state.json. Use when continue client, pick up books, or where we left off. |
Make multi-session work safe. Disk is truth.
engagement_state.json:shared/agent-runtime.md + shared/operator-lens.md + references/stage_artifacts.mdoperator missing → resolve once and write it (do not re-ask if inferable)state.artifacts still existpython3 scripts/validate_engagement_artifacts.py <client_dir> if workpapers present## Resume — [legal_name] · [operator] · [engagement_type] · period [fy / on-disk]
- Stage: [current_stage] ([status])
- Completed: [stages_completed]
- Blockers: [blockers or none]
- Open queries: [n]
- Next: [concrete next skill/action]
status == blocked → work the blocker firststatus == waiting_on_user and open_queries non-empty →
re-issue unanswered asks via structured user-question tool
(shared/user-questions.md) — do not only re-print queries.mdcurrent_stage by loading that stage’s SKILL.mdSay so clearly. Offer:
engagement-setup for a new clientfull-engagement-pipeline if they dumped filesDone when: state loaded, one-line status shown, next stage skill identified (or blockers listed).