Feature Handoff
Prepare a precise handoff for an agent or developer implementing a feature, continuing a task or reviewing a finished change.
Install
$ agentstack add skill-witnesstodark-mr-mak-workspace-feature-handoff ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-witnesstodark-mr-mak-workspace-feature-handoff) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Feature handoff
Read the current project files and relevant terminal or report before writing a handoff. Use the evidence currently on disk, not an earlier progress message.
Include the intended behavior, affected files, useful starting points, exact skill paths, known constraints and acceptance checks. For a continuation, add what is already implemented, what remains, current test results and any running process that must not be interrupted. Keep secrets and login material out.
Make ownership clear when several agents are working. Identify files that must not be overwritten. Carry forward accepted choices and unresolved questions. Do not assign the user work that the receiving agent can complete itself.
For a completed feature, lead with its practical result, then summarize the change and verification. Link the relevant report or artifacts. Distinguish a prepared build from an installed update and a submitted job from a reviewed asset. Read workspace-authoring when the handoff is a Workspace deliverable.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: witnesstodark
- Source: witnesstodark/mr-mak-workspace
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.