handover
Consolidate prior multi-step discussions, decisions, and artifacts into one executable handover document for a target agent or external tool agent. Use when work spans multiple design/communication steps and needs clean transfer.
What this skill does
# Skill: Context To Handover ## Purpose Create a complete handover document from existing context, especially when handover is not the first step in the workflow. This skill is for context synthesis and transfer, not for implementation itself. ## When To Use Trigger this skill when any of the following is true: - The current work included multiple design/discussion steps before execution. - Context is scattered across messages and files. - The next executor is another agent, tool-integrated agent, or human operator. - You need a single handover artifact that can be run without reading full chat history. ## Non-Goals - Do not redesign the whole solution unless there is a clear contradiction. - Do not assume the target is a coding agent. - Do not produce vague summaries that omit decisions, constraints, or evidence. ## Target Agent Model (critical) Treat `target agent` as an abstract executor. It may be: - coding agent - workflow/tool agent (for example automation, browser, retrieval, or orchestration agent) - external platform agent - human operator Always capture target-specific details explicitly: - runtime/platform - available tools and blocked tools - expected input/output interface - execution constraints (time, budget, permissions, environment) ## Workspace Policy - Default handover workspace: `.agents/handover/` - If user specifies another path, use user path. - Keep related artifacts in one workspace when possible. ## Required Outputs Create/update in the selected handover workspace: 1. `handover-<timestamp>.md` (required) 2. Optional supporting docs only if needed (for example `context-index.md`) ## Source Collection Model (critical) Before writing handover, collect and classify context from: 1. Conversation decisions 2. Existing design docs/specs/plans 3. Research notes and references 4. Existing code/log/test evidence (if implementation already started) 5. Open questions and unresolved risks For each collected item, capture: - source path or source type (chat/file/tool output) - short factual summary - why it matters for execution ## Handover Document Contract (critical) The handover document must include all sections below: 1. `Goal` 2. `Target Executor Profile` 3. `Current State` 4. `Decisions Already Made` 5. `Constraints` 6. `Relevant Artifacts` 7. `Execution Plan` 8. `Verification` 9. `Open Questions` 10. `Out of Scope` 11. `Referenced Sources` 12. `Kickoff Command or First Action` ### Section Rules - `Relevant Artifacts` must list concrete paths and usage notes. - `Referenced Sources` must only list sources actually used for this handover. - `Execution Plan` must be actionable, ordered, and free of placeholders. - `Verification` must include runnable checks when possible. - `Open Questions` must include owner and expected resolution path when possible. ## Workflow 1. Identify target executor type and its constraints. 2. Gather all relevant upstream context (chat + docs + artifacts). 3. Resolve conflicts by preserving latest explicit decision and recording deltas. 4. Write `handover-<timestamp>.md` from template. 5. Run completeness check against the 12 required sections. 6. Ensure next executor can start from the handover doc alone. ## Quality Bar - Context complete enough to avoid re-reading full thread. - No hidden assumptions. - No agent-type ambiguity. - No missing artifact paths for required inputs. - Verification criteria are concrete. ## Final Response Format Respond with: 1. handover workspace path 2. file paths created/updated 3. what context was synthesized (short) 4. copy-ready line for next executor (for example: `Run .agents/handover/handover-20260402-1030.md`) ## Template Use `assets/handover-template.md` as the default scaffold.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.