business-context-intake

Captures business context through a structured interview before feature design begins.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill business-context-intake-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-context-intake
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/business-context-intake
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill business-context-intake-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often start designing features without a shared, documented understanding of the user problem, success metrics, or compliance constraints, leading to misaligned work and scope creep. This Skill runs a structured intake interview and commits the answers to a versioned business-context document before any brainstorming or design begins. ## Core Features & Use Cases - Structured Interview: Asks eight sequential questions covering the user problem, JTBD statement, urgency, measurable success metrics, non-goals, compliance (GDPR/PCI/HIPAA/SOC 2), stakeholders, and performance constraints. - Document Generation: Produces a committed Markdown document at .ai/YYYY-MM-DD-<feature-slug>/business-context/business-context-<feature-slug>.md including a north-star metric table, stakeholder map, and an Amazon Working Backwards PR/FAQ section. - Hard Gate Enforcement: Blocks the brainstorming skill from activating until an approved business-context document exists, with explicit skip rules for bug fixes and internal refactors. - Use Case: A product manager asks for a new checkout feature. The Skill interviews them one question at a time, captures a measurable success metric and three explicit non-goals, runs the business-context-reviewer agent, and commits the document before design starts. ## Quick Start Ask the AI to run the business-context-intake skill to capture the problem, users, and success metrics for your new feature before any design work begins.

Frequently Asked Questions about business-context-intake

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

FAQPage Schema
How do I capture business requirements before designing a feature?

Run a structured intake interview that asks one question at a time about the user problem, persona, success metrics, non-goals, and compliance. The answers are written into a committed Markdown document that downstream design steps read as input.

What is a JTBD statement and how is it written?

A JTBD (Jobs To Be Done) statement follows the format: When [situation], I want to [motivation], so I can [outcome]. It captures the context of use and desired outcome from the user's perspective rather than describing the feature itself.

When can I skip business context intake?

Skip it for bug fixes where correct behavior is obvious, dependency upgrades without behavior change, internal refactors with no user impact, and config changes. It is required for new features, user-visible enhancements, compliance work, and reliability initiatives.

What is the Amazon Working Backwards PR/FAQ format?

It is a document written as if the feature already launched, containing a customer-outcome-framed press release, a customer FAQ, and an internal FAQ covering riskiest assumptions. It surfaces business-model and value gaps before any specification is written.

Why must brainstorming wait for a business context document?

The skill enforces a hard gate so design never starts on assumptions. Without a committed document defining the problem, user, and measurable success metric, teams risk building toward an undefined goal and losing context across sessions.