一键导入
session-end
End session and create all handoff documentation
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
End session and create all handoff documentation
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Strategic system analysis for health assessment, pattern recognition, component deep dives, risk assessment, and architecture review. Use for proactive system understanding beyond reactive incident response.
Transform a design into an implementation spec. Creates a blueprint document and an implementation prompt for /plan mode. Use after /design or /research.
Cancel the active Wrought implementation/RCA loop
Interactive design analysis for architecture decisions. Combines codebase analysis, documentation review, and external research to provide evidence-based recommendations. Use for tradeoff analysis, pattern evaluation, migration planning, or design validation.
Log a proactive discovery that needs attention. Creates a factual record of WHAT was found with classification and a Findings Tracker. Use for analysis discoveries, review findings, or inspection results.
Deep multi-agent code review with algorithmic complexity analysis, data structure review, paradigm enforcement, and efficiency analysis. Complements /simplify with deeper dimensions.
| name | session-end |
| description | End session and create all handoff documentation |
| disable-model-invocation | false |
| wrought | {"version":"1.0","platforms":{"claude-code":{"disable-model-invocation":false}}} |
Session is ending. Please complete all session end tasks:
Save active plan file (if exists):
~/.claude/plans/ for recent plan files (modified today)~/docs/plans/PLAN_{datetime}_{original_name}.mdCreate new handoff document:
date '+%Y-%m-%d_%H%M'NEXT_SESSION_PROMPT_{datetime}.mdCreate session summary:
SESSION_SUMMARY_{datetime}.mdUpdate CLAUDE.md:
@NEXT_SESSION_PROMPT_*.mdArchive old handoff:
NEXT_SESSION_PROMPT_*.md to docs/archive/sessions/Update Findings Trackers (if applicable):
docs/findings/{datetime}_{name}_FINDINGS_TRACKER.mddocs/findings/*_FINDINGS_TRACKER.md files for trackers related to this session's work- [x] **F1.1**: ...)Status field (Open → In Progress → Resolved → Verified)Stage field to reflect the current pipeline positionResolved in session / Verified in session fields with the session numberLast Updated timestamp at the top of the fileStage reconciliation — Check if artifacts exist that the tracker doesn't yet reflect:
docs/investigations/ matching finding → Stage should be ≥ Investigatingdocs/RCAs/ matching finding → Stage should be ≥ RCA Completedocs/design/ matching finding → Stage should be ≥ Designingdocs/blueprints/ matching finding → Stage should be ≥ Blueprint Readydocs/plans/ matching finding → Stage should be ≥ PlannedResolved
If a stage was missed (artifact exists but no lifecycle row), backfill the lifecycle row with approximate timestamp.GitHub Projects sync (NON-FATAL) — For each finding whose stage changed this session, read docs/reference/github_projects_sync_protocol.md and follow Protocol B to update the board. Key mappings:
9afc76db), Status = In Progress (47fc9ee4)c9de0e86), Status = Done (98236657)a20e6ccd), Status = Done (98236657)
If **Project Item ID**: is missing or — in the tracker, skip sync with a note.Output format — Show Stage alongside Status:
Findings Trackers:
{tracker_name}:
F1: {title} — Status: In Progress | Stage: RCA Complete
F2: {title} — Status: Open | Stage: Open
IMPORTANT:
After completing all tasks, provide a summary showing: