assembling-tl-handoff

Assembles a path-referenced Handoff Bundle for Tech Lead acceptance in the BA pipeline.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill assembling-tl-handoff-jin9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assembling-tl-handoff
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/assembling-tl-handoff
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill assembling-tl-handoff-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a business analysis pipeline finishes scoping, story drafting, governance, and feasibility work, someone still has to package those artifacts into a single signable package for the Tech Lead — without duplicating content, losing the original requirement, or shipping with unresolved blockers. This Skill performs that Stage 5 composition deterministically. ## Core Features & Use Cases - Handoff Bundle assembly: Links the raw requirement, Scope Sheet, Story Set index, Governance Check, and Feasibility Note by relative path instead of inlining full contracts, keeping context usage low. - Invariant enforcement: Sets state: ready-for-tl only when governance is clear, no blocker is open, feasibility is buildable or phased, and every open item traces to a real Scope-Sheet OQ id accepted by a PM or Sponsor. - Human acceptance gate (G5): Leaves accepted_by unsigned for the named Tech Lead; the agent never self-accepts. - Use Case: After running the BA pipeline on a new product requirement, ask the agent to package everything for Tech-Lead acceptance and receive a manifest with linked artifacts, inlined open items, and checked invariant assertions. ## Quick Start Assemble the Handoff Bundle for this requirement and tell me whether it is ready for the Tech Lead.

Frequently Asked Questions about assembling-tl-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package business analysis artifacts for Tech Lead acceptance?

Run the handoff assembly step, which links the Scope Sheet, Story Set index, Governance Check, and Feasibility Note by relative path into one Handoff Bundle manifest. It inlines only open items and invariant assertions, then sets state ready-for-tl when all checks pass.

What conditions must be met before setting state ready-for-tl?

The governance check verdict must be clear, no blocker may be open, the feasibility verdict must be buildable or phased, and all five contracts must share one task_id. If any invariant fails, the assembly stops and reports which check failed.

Why does the Handoff Bundle link artifacts by path instead of inlining them?

Linking by path keeps the bundle within the context budget of a small model and avoids duplicating the source of truth. Only open_items and the invariant assertions are inlined so the Tech Lead sees deferred decisions at a glance.

Can the agent sign off the Tech Lead acceptance gate itself?

No. Publishing the bundle with state ready-for-tl is a confirm action requiring a named human at gate G5. The agent assembles the bundle and asserts the invariants but leaves accepted_by unsigned for the Tech Lead.

What happens to open questions in the handoff bundle?

A deferred question appears in open_items only if a PM or Sponsor explicitly accepted it, and its source_oq must be a real Scope-Sheet OQ id. Unaccepted questions remain blockers and prevent the ready-for-tl state.