From the-workflow
Structured work handoff across context boundaries: triage decisions, constraints, and remaining work into a prompt-quality transfer document. Invoke whenever task involves handing off work — session restart, teammate delegation, async resumption, or any context boundary crossing.
npx claudepluginhub xobotyi/cc-foundry --plugin the-workflowThis skill uses the workspace's default tool permissions.
A handoff document is a prompt — an instruction set for the receiving agent. Triage your context into a structured,
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
A handoff document is a prompt — an instruction set for the receiving agent. Triage your context into a structured, information-dense transfer document that preserves high-value state and drops noise.
Two modes, determined by who receives the handoff:
If the user doesn't specify, ask.
Separate your context into two categories before writing anything.
Keep — state that must survive the boundary:
Drop — noise in transfer:
Generate a markdown document. Omit sections with no content — empty headers are noise.
# Handoff: [task name]
## Context
[1-2 sentences: what this work is about and its current state]
## Decisions
- [decision]: [rationale]
## Constraints
- [constraint]: [why it matters]
## External Resources
- [resource type]: [identifier/URL]
## Remaining Work
1. [highest priority next step]
2. [subsequent steps...]
## Verification State
- [what was tested/verified and result]
- [what remains untested]
## Open Questions
- [question]: [context needed to resolve]
Same structure as self-handoff, with these sections added before Decisions:
## Codebase Orientation
- [key file/directory]: [relevance to this task]
## Recommended Skills & Tools
- [skill or tool]: [why it's needed]
## Conventions
- [convention]: [where it's documented]
Target 500-2000 tokens. When work is extensive:
After generating the handoff, verify:
If Decisions or Remaining Work is empty when work was done, the triage missed something. Re-examine the conversation.