business_intake_scoping

Scopes one business task into a boundary-visible responsibility unit from partial intake information.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill business-intake-scoping-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business_intake_scoping
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/packs/business-intake/business_intake_scoping
Command: npx skills add https://github.com/synthaicode/XRefKit --skill business-intake-scoping-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When importing real business work into an AI-assisted repository, users often only know fragments: a task name, one owner, one artifact, or a recurring bottleneck. This Skill turns those partial seeds into a structured, boundary-visible scope instead of guessing or jumping straight into implementation steps. ## Core Features & Use Cases - Discovery-first scoping: Expands outward from the smallest visible seed into previous side, current responsibility, and next side, producing a scoped intake note. - Seven first-pass fields: Captures start condition, inputs, judgment points, outputs, send-back conditions, reference rules, and unresolved items using a reusable template. - Explicit partial results: Labels output as partial or scope-ready, keeps ambiguity visible, and returns the smallest next confirmation step. - Use Case: A user says "we keep messing up invoice handoffs between sales and accounting." The Skill produces a scoped intake note with the assumed boundary, known facts, missing confirmation points, and the next question to ask. ## Quick Start Use the business intake scoping skill to scope the recurring invoice handoff problem between sales and accounting into a boundary-visible responsibility unit.

Frequently Asked Questions about business_intake_scoping

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

FAQPage Schema
How do I scope a business task when I only know part of the process?▼

Start from the smallest visible seed such as a task name, owner, artifact, or repeated bottleneck. The Skill expands outward to previous side, current responsibility, and next side, then fills seven first-pass fields and marks anything missing as unresolved.

What is a boundary-visible responsibility unit in business intake?▼

It is a scoped business task with an explicit start trigger, inputs, judgment point, outputs, send-back condition, and next owner. If any of these are missing, the result is labeled partial scoping rather than forced into a false complete scope.

Can I use business intake scoping without a full process map?▼

Yes, the Skill is designed for partial information and does not require a complete business architecture first. It works from one or more seeds and explicitly records assumed boundaries and missing confirmation points.

When should I not use business intake scoping?▼

Do not use it to write detailed execution procedures or screen-level steps before the business boundary is explicit. It stops at the responsibility level and downgrades results that contain only local work steps.

What does the scoped intake note output contain?▼

The note contains known facts, an assumed boundary, previous side, current scope, next side, seven first-pass fields, unresolved items, a partial or scope-ready status, and the smallest next confirmation step.