handoff

Engineering Community

Skill notes

Step 1: Gather Context

Run these commands in parallel to understand the current state: git status — see all tracked/untracked files and staging state git diff — see unstaged changes git log --oneline -10 — recent commits to understand work trajectory git branch --show-current — current branch name

Step 2: Confirm Save Location

List all folders in .specs/ Match the current branch name, modified files, or recent commit messages to spec folder names Use AskUserQuestion to confirm the save location with the user: If a likely match is found, suggest it as the recommended option Always include other spec folders as alternatives

Step 3: Analyze Work State

Work Completed — analyze recent git commits, review completed todos, identify patterns in changes made Work In Progress — active todo items, uncommitted changes, files currently being modified Work Remaining — pending todo items, blockers, dependencies, priorities Context — branch strategy, important decisions, known issues, relevant file paths with line numbers

Step 4: Write the Handoff Document

Save the file as handoff--{YYYY-MM-DD-HH-mm}--{brief-work-summary}.md in the confirmed location. Use date +"%Y-%m-%d-%H-%M" to get the correct local timestamp {brief-work-summary} is a short kebab-case description of the work (e.g., add-cart-api, fix-auth-redirect, refactor-review-section) Use this structure:

Step 5: Report

After saving, display: The full file path where the handoff was saved A brief summary of the current state

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@hta218 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather Context

Run these commands in parallel to understand the current state: `git status` — see all tracked/untracked files and staging state `git diff` — see unstaged changes `git log --oneline -10` — recent commits to understand work trajectory `git branch --show-current` — current branch name

02
Step 2: Confirm Save Location

List all folders in `.specs/` Match the current branch name, modified files, or recent commit messages to spec folder names Use `AskUserQuestion` to confirm the save location with the user: If a likely match is found, suggest it as the recommended option Always include other spec folders as alternatives

03
Step 3: Analyze Work State

Work Completed — analyze recent git commits, review completed todos, identify patterns in changes made Work In Progress — active todo items, uncommitted changes, files currently being modified Work Remaining — pending todo items, blockers, dependencies, priorities Context — branch strategy, important decisions, known issues, relevant file paths with line numbers

04
Step 4: Write the Handoff Document

Save the file as `handoff--{YYYY-MM-DD-HH-mm}--{brief-work-summary}.md` in the confirmed location. Use `date +"%Y-%m-%d-%H-%M"` to get the correct local timestamp `{brief-work-summary}` is a short kebab-case description of the work (e.g., `add-cart-api`, `fix-auth-redirect`, `refactor-review-section`) Use this structure:

05
Step 5: Report

After saving, display: The full file path where the handoff was saved A brief summary of the current state

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.