aiwcli 0.12.3 → 0.12.6

package/dist/templates/_shared/.claude/commands/handoff-resume.md

@@ -1,64 +1,12 @@
-# Resume Handoff
-
-Restore session context from a handoff document programmatically, then create actionable ISC tasks so work continues without re-discovering what was already learned.
-
-## Arguments
-
-- `$ARGUMENTS` - Optional path to a handoff folder or index.md. If omitted, auto-discovers the most recent handoff from the active context.
-
-## Instructions
-
-### Step 1: Gather Context via Script
-
-Run the resume script to collect and format all handoff sections:
-
-**If `$ARGUMENTS` is provided:**
-```bash
-bun .aiwcli/_shared/scripts/resume_handoff.ts "$ARGUMENTS"
-```
-
-**If `$ARGUMENTS` is empty:**
-The script auto-discovers the active context ID programmatically — no manual lookup needed:
-```bash
-bun .aiwcli/_shared/scripts/resume_handoff.ts
-```
-
-Present the script's output to the conversation. The output is already structured in priority order (dead ends first, then pending items, decisions, git delta, completed work, context notes).
+---
+name: handoff-resume
+description: Resume handoff
+---
 
-If the script exits with an error, show the error message and stop.
-
-### Step 2: Create ISC Tasks
-
-Convert each actionable item from the script output into a task via `TaskCreate`:
-- Each pending issue from the **Pending Items** section
-- Each remaining plan item from the **Plan — Remaining Items** section
-
-Each task follows ISC format — ~8 words, states a desired end-state (not an action), and is binary testable in 2 seconds.
-
-**Example:**
-
-| Source | ISC Task |
-|--------|----------|
-| Pending: "Fix race condition in SessionStore" | "SessionStore handles concurrent access without race conditions" |
-| Plan remaining: "Add retry logic to API client" | "API client retries failed requests with exponential backoff" |
-| Next step: "Write tests for auth flow" | "Auth flow has passing integration test coverage" |
-
-### Step 3: Confirm Ready
-
-After creating tasks, run `TaskList` and confirm ready to continue.
-
-## Constraints
+# Resume Handoff
 
-- Dead ends are presented verbatim from the script output — never summarize or omit entries
-- ISC tasks use ~8-word end-state format, not action descriptions
-- Skip missing files gracefully (the script handles this)
-- If the script warns about staleness (>7 days), surface the warning prominently
+Restore context from a handoff document and create ISC tasks. See `.aiwcli/_shared/handoff-system/workflows/handoff-resume.md` for complete process documentation.
 
-## Success Criteria
+**Quick trigger:** `/handoff-resume` or `/handoff-resume path/to/handoff`
 
-- [ ] Script ran successfully and output the structured briefing
-- [ ] Dead ends visible in conversation (not summarized)
-- [ ] Pending items converted to ISC tasks via TaskCreate
-- [ ] Plan completion percentage visible (if plan exists)
-- [ ] Git delta visible
-- [ ] Tasks confirmed via TaskList
+The workflow uses the resume script to load handoff sections and convert pending items to tasks.

package/dist/templates/_shared/.claude/commands/handoff.md

@@ -1,198 +1,12 @@
-# Handoff Workflow
-
-Generate a handoff document summarizing the current session's work, decisions, and pending items. Optionally update a plan document to track completed vs remaining tasks.
-
-## Triggers
-
-- `/handoff` command
-- `/handoff path/to/PLAN.md` - with plan document integration
-- Phrases like "write a handoff", "create a session summary", "document what we did", "end session with notes"
-
-## Philosophy
-
-Handoffs exist to minimize the token and time cost of session startup. A precise handoff lets the next session hit the ground running without rediscovering context through Explore agents or file searches.
-
-**Think: "What would I need to continue this work with zero prior context?"**
-
-Key principles:
-- **Absolute paths over vague references** — `C:\project\src\auth\handler.ts:45` not "handler.ts line 45"
-- **Specific locations over general areas** — Name the function/class/section, not just the file
-- **Enough detail to skip discovery** — Include enough context that the next session doesn't need to grep or search
-- **Self-contained decisions** — Capture the "why" and the "why not" so alternatives aren't re-explored
-
-A good handoff pays for itself in the first minute of the next session.
-
-## Arguments
-
-- `$ARGUMENTS` - Optional path to a plan document. If provided, the handoff will:
-  1. Mark completed items in the plan with `[x]`
-  2. Add notes about partial progress
-  3. Append a "Session Progress" section to the plan
-
-## Process
-
-### Step 1: Gather Information
-
-1. Review conversation history for:
-   - Completed tasks and implementations
-   - Key decisions and their rationale
-   - Failed approaches (to avoid repeating)
-   - External context (deadlines, stakeholder requirements)
-
-2. Look for TODOs/FIXMEs mentioned in session
-
-3. **If plan document provided**: Read the plan and identify:
-   - Tasks that are now completed
-   - Tasks that are partially done
-   - Tasks that were attempted but blocked
-   - New tasks discovered during implementation
-
-### Step 2: Generate Document
-
-Use this template. The `<!-- SECTION: name -->` markers are required for the save script to parse sections into sharded files.
-
-```markdown
----
-title: Session Handoff
-date: {ISO timestamp}
-session_id: {conversation ID if available}
-project: {project name from package.json, Cargo.toml, or directory name}
-plan_document: {path to plan if provided, or "none"}
----
-
-# Session Handoff — {Date}
-
-<!-- SECTION: summary -->
-## Summary
-{2-3 sentences covering: (1) session goal, (2) what changed technically, (3) current state}
-
-Example: "Session goal: Implement JWT refresh tokens. Added refresh token generation in `C:\project\src\auth\tokens.ts:145-203` and rotation endpoint. Feature works but needs rate-limiting before production (see Pending Issues)."
-
-<!-- SECTION: completed -->
-## Work Completed
-
-**Bad (requires exploration):**
-- Fixed auth bug
-- Updated tests
-
-**Good (exploration-free):**
-- Auth: Fixed JWT validation race condition in `C:\project\src\auth\handler.ts:67-89`
-  - Issue: Token validation happened after user session creation → security gap
-  - Fix: Moved validation to middleware, added async lock
-  - Tests updated: `C:\project\tests\auth\handler.test.ts:45` now covers concurrent validation
-
-{Your work completed here, following the "Good" example format with absolute paths}
-
-<!-- SECTION: dead-ends -->
-## Dead Ends — Do Not Retry
-
-These approaches were attempted and failed. Do not retry without addressing the root cause.
-
-| Approach | Why It Failed | Time Spent | Alternative |
-|----------|---------------|------------|-------------|
-| {What was attempted} | {Specific reason} | {Rough estimate} | {What to try instead} |
-
-<!-- SECTION: decisions -->
-## Key Decisions
-{Technical choices with rationale. Format: **Decision**: Rationale. Trade-off: X.}
-
-<!-- SECTION: pending -->
-## Pending Issues
-- [ ] {Issue} — {severity: HIGH/MED/LOW} {optional workaround note}
-
-<!-- SECTION: next-steps -->
-## Next Steps
-1. {Actionable item with absolute path and line number, e.g., C:\path\to\file.ts:123}
-
-<!-- SECTION: files -->
-## Files Modified
-{Absolute paths with line numbers for significant changes. Skip formatting-only edits.}
-
-<!-- SECTION: context -->
-## Context for Future Sessions
-{Non-obvious context: env quirks, stakeholder requirements}
-
-```
-
-### Step 3: Update Plan Document (if provided)
-
-If a plan document path was provided in `$ARGUMENTS`:
-
-1. **Read the plan document**
-2. **Identify completed items**:
-   - Find checkboxes `- [ ]` that match completed work
-   - Change them to `- [x]`
-3. **Add progress notes** to items that are partially complete:
-   - Append `(partial: {brief status})` to the line
-4. **Append Session Progress section** at the bottom:
-
-```markdown
-
 ---
-
-## Session Progress Log
-
-### {Date} — Session {session_id or timestamp}
-
-**Completed this session:**
-- [x] {Task from plan that was completed}
-- [x] {Another completed task}
-
-**Partially completed:**
-- {Task} — {current state, what remains}
-
-**Blocked/Deferred:**
-- {Task} — {reason, what's needed}
-
-**New items discovered:**
-- [ ] {New task not in original plan}
-- [ ] {Another new task}
-
+name: handoff
+description: Create handoff document
 ---
-```
-
-5. **If no plan document was provided**:
-   - Skip plan creation - the handoff document serves as the session record
-
-### Step 4: Save and Update Status
 
-Instead of writing the file directly, pipe your handoff content to the save script:
-
-```bash
-bun .aiwcli/_shared/scripts/save_handoff.ts <<'EOF'
-{Your complete handoff markdown content from Step 2}
-EOF
-```
-
-The script will automatically find the active context and create the handoff folder structure.
-
-## Dead Ends Section Guidelines
-
-This section is critical for preventing context rot across sessions. Be specific:
-
-**Bad (too vague):**
-> - Tried using library X, didn't work
-
-**Good (actionable):**
-> ### Fixing the race condition in SessionStore
-> | Approach Tried | Why It Failed |
-> |----------------|---------------|
-> | `async-mutex` package | Deadlock when nested calls to `getSession()` |
-> | Redis WATCH/MULTI | Our Redis 6.x cluster doesn't support WATCH in cluster mode |
-> | In-memory lock Map | Works single-node but breaks in horizontal scaling |
->
-> **What to try instead**: Upgrade to Redis 7.x which supports WATCH in cluster mode, or use Redlock algorithm
+# Handoff Workflow
 
-**Capture these dead ends:**
-- Packages/libraries that had incompatibilities
-- Approaches that caused new bugs or regressions
-- Solutions that worked locally but failed in CI/staging/prod
-- Configurations that conflicted with existing setup
-- Rabbit holes that consumed significant time without progress
+Generate a comprehensive handoff document for the next session. See `.aiwcli/_shared/handoff-system/workflows/handoff.md` for complete process documentation.
 
-## Post-Generation Output
+**Quick trigger:** `/handoff` or `/handoff path/to/PLAN.md`
 
-After saving, confirm:
-- Handoff folder location
-- Number of dead ends documented (if any)
-- Plan update summary (if plan was provided)
+The workflow guides you through gathering session context, generating structured sections, and saving via the handoff system.

package/dist/templates/_shared/.codex/workflows/handoff.md

@@ -150,7 +150,7 @@ If a plan document path was provided in `$ARGUMENTS`:
 Instead of writing the file directly, pipe your handoff content to the save script:
 
 ```bash
-bun .aiwcli/_shared/scripts/save_handoff.ts "{context_id}" <<'EOF'
+bun .aiwcli/_shared/handoff-system/scripts/save_handoff.ts "{context_id}" <<'EOF'
 {Your complete handoff markdown content from Step 3}
 EOF
 ```

package/dist/templates/_shared/.windsurf/workflows/handoff.md

@@ -150,7 +150,7 @@ If a plan document path was provided in `$ARGUMENTS`:
 Instead of writing the file directly, pipe your handoff content to the save script:
 
 ```bash
-bun .aiwcli/_shared/scripts/save_handoff.ts "{context_id}" <<'EOF'
+bun .aiwcli/_shared/handoff-system/scripts/save_handoff.ts "{context_id}" <<'EOF'
 {Your complete handoff markdown content from Step 3}
 EOF
 ```