What problem does it solve?
The task handoff checklist eliminates ambiguity after a development change by producing a single, structured acceptance-ready report so reviewers do not need to ask follow-up questions about what changed, what to test, or what documentation is missing.
Core Features & Use Cases
- Automated change scanning: Enumerates changed files from git diffs and summarizes added, modified, and removed files.
- Eight-dimension acceptance report: Produces a checklist covering navigation/entry points, documentation, rules/agreements, process changes, test plans, risks, code quality, and follow-up actions.
- Actionable outputs: Lists exact routes, API endpoints, required doc updates, smoke-test steps, rollback notes, and which skills to invoke next (e.g., smoke-test, human-verify).
- Use case: After completing a feature branch, generate a handoff report that shows where to click in the UI, which API contracts changed, what tests to run, and any remaining documentation debt.
Quick Start
Ask the assistant to generate a handoff checklist for the current branch by providing the branch or PR context so it scans git diffs and returns a complete acceptance-ready report.
