agent-handoff-planning
openbooklet.com/s/agent-handoff-planningopenbooklet.com/s/agent-handoff-planning@1.0.0GET /api/v1/skills/agent-handoff-planningStructure a clean handoff between workflow agents with explicit outputs, open questions, and next-owner guidance.
Review agent memory, handoff, retrieval, and learning designs for usefulness, provenance, privacy, staleness, and poisoning risk.
Review agent run traces, eval summaries, tool logs, and handoff evidence before accepting a workflow result or self-improvement proposal.
Select the best workflow agent for a task based on task shape, deliverables, and dependency packs.
Write correct @spec JSDoc annotations in source files to link code to specgraph spec documents and produce E0 evidence.
Assemble the minimal artifact bundle needed for another agent or human to continue work.
Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.
Create safe static review surfaces for demo and QA media. Use when Codex needs an HTML or Markdown review page comparing demo videos, source specs, QA reports, screenshots, storyboards, quality findings, and evidence links from demo-machine, manual-qa-machine, Playwright, or video analysis outputs.
Plan no-caption slideshow-style MP4s and frame reels from demo-machine screenshots, storyboard frames, selected video spans, or manual QA evidence. Use when Codex needs a polished still-frame walkthrough, hero reel, or reviewable visual summary without recapturing the browser flow.
Package completed demo-machine runs, browser capture artifacts, or evidence-backed product demos into source-linked handoff bundles. Use when Codex needs to organize `.demo.yaml`, `events.json`, `quality.json`, screenshots, storyboard outputs, rendered videos, review prompts, or release-ready demo assets without losing provenance.
Align design artifacts with code tokens and component APIs so spacing, color, type, and states stay consistent through implementation.
Choose the right developer artifact type, source of truth, and review surface for a task.
Translate a Figma screen or component into an implementation plan covering structure, states, constraints, and component boundaries.
Inspect failing GitHub Actions checks, isolate the actionable failure, and turn it into a concrete fix path with verification steps.
Shape source-backed model and diagram review artifacts for architecture, UML-style, C4, dependency, and workflow views.
Review or design multi-agent workflows with clear ownership, handoffs, evidence gates, conflict handling, and minimal coordination overhead.
Run the noslop pre-commit quality gate, interpret failures, and enforce content-aware protection rules before every commit.
Run the noslop pre-PR quality gate and handle the noslop-approved escape hatch for intentional config weakening before opening a pull request.
Install and configure noslop quality gates in an existing repository, including git hooks, CI workflows, and Claude Code guardrails.
Check whether a change is ready for review by testing the claimed behavior, summarizing risk, and naming any gaps reviewers should know about.
Design governed self-improving agent loops that sense work, model failure modes, act in small slices, gate evidence, and turn learnings into tracked proposals.
Auto-indexed from 45ck/skill-harness
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.