creating-stakeholder-packet

Extract and confirm a complete Stakeholder Input Packet from informal project input.

Updated Jun 11, 2026

Search Tags:#requirements #clarification #interview #handoff #product discovery #stakeholder packet

Ready to run

npx skills add https://github.com/veglezMX/agent-factory --skill creating-stakeholder-packet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: creating-stakeholder-packet
Source: https://github.com/veglezMX/agent-factory/tree/main/.claude/skills/creating-stakeholder-packet
Command: npx skills add https://github.com/veglezMX/agent-factory --skill creating-stakeholder-packet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn an incomplete, contradictory, or informal product idea into a confirmed Stakeholder Input Packet that downstream agents can trust.

Core Features & Use Cases

Interview-driven intake: Asks targeted questions to fill gaps, resolve hedges, and remove contradictions before delivery work begins.
Traceable packet drafting: Maps stakeholder statements into the 17 packet sections and preserves working state until confirmation.
Confirmation and safety gates: Reads back the critical business sections for explicit approval and blocks unconfirmed business truth from entering the packet.
Use Case: A project idea exists only in chat notes, so the Skill interviews the stakeholder, drafts the packet, confirms the key rules, and prepares it for the delivery pipeline.

Quick Start

Use the creating-stakeholder-packet skill to interview the stakeholder and produce a confirmed Stakeholder Input Packet from the current notes.

Frequently Asked Questions about creating-stakeholder-packet

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

FAQPage Schema

How do I turn rough product ideas into a structured requirements packet for handoff?▼

To turn rough product ideas into a structured requirements packet, you can use an interview-driven intake process that asks targeted questions to fill gaps, resolve contradictions, and confirm business rules before handoff. This maps informal notes into 17 defined packet sections for downstream delivery.

What is the best way to resolve contradictions in informal project notes before development?▼

The best way to resolve contradictions in informal project notes is through targeted stakeholder clarification interviews. This process identifies hedges and conflicting statements, resolving them through explicit confirmation gates to ensure only verified business truth enters the final packet.

How do I prepare incomplete project drafts for product discovery and agent delivery?▼

To prepare incomplete project drafts for product discovery, apply a completeness gating process that maps existing notes into structured sections. The system interviews you to extract missing details and reads back critical sections for explicit approval before agent delivery begins.

Can I use stakeholder interviews to fill gaps in partial project scope changes?▼

Yes, you can use stakeholder interviews to fill gaps in partial project scope changes. The intake process asks targeted questions to clarify new requirements, maps the updated statements, and preserves the working state until you explicitly confirm the revised packet sections.

Why do I need explicit approval before creating a stakeholder input packet?▼

You need explicit approval to block unconfirmed business truth from entering the stakeholder input packet. A read-back confirmation gate ensures critical business sections are verified by the stakeholder, preventing inaccurate or contradictory requirements from reaching the delivery pipeline.

What are the limitations of using automated intake for stakeholder requirements gathering?▼

A limitation of automated intake for stakeholder requirements gathering is that it cannot bypass the explicit confirmation gate. If the stakeholder does not provide explicit approval for the read-back of critical business sections, the process cannot finalize the 17 packet sections for delivery.