Feature Handoff

Use this skill when work in the current context discovers a dependency that must be implemented somewhere else, often by another agent in a separate session.

The output is a copy/paste artifact, not a conversation summary. The receiving agent must be able to understand and act on it without access to the source session.

Boundary

A handoff packages the need already established by the current work. It does not create new product authority.

• Preserve accepted requirements and constraints at their existing strength.
• Do not promote an idea, example, or implementation convenience into a requirement.
• Describe the required outcome before proposing a mechanism.
• Do not prescribe the receiving component's internal implementation unless the interface or mechanism is itself part of the established dependency.
• If the handoff exposes a correctness-sensitive semantic seam that needs durable normative authority, use behavioral-spec instead of hiding that work inside the handoff.
• If the work is really a durable behavioral specification, use behavioral-spec. A feature handoff may reference such artifacts but does not replace them.

Requirement levels