intake

To create a structured intake document, you need to capture the problem, goal, non-goals, constraints, stakeholders, and acceptance criteria. This skill uses template-driven document assembly to convert vague requests into a standardized intake format for downstream planning.

Capturing non-goals and acceptance criteria requires forcing explicit scope boundaries and testable conditions during the intake phase. This skill preserves testable criteria without placeholders, ensuring the request stays concrete and actionable for downstream specification.

Yes, you can use this skill to triage investigation requests lacking a specification. It applies to the first workflow phase, drafting structured intake documents for new feature requests, changes, and investigations by validating prerequisite workflow state.

Intake document generation requires prerequisite workflow state validation to ensure readiness. This validation confirms the initial problem space is ready for template-driven document assembly before downstream planning and scoping research begin.

You need to include explicit open questions in your requirements intake document to identify unresolved uncertainties early. This ensures stakeholders can address missing information before the request moves into downstream specification and planning phases.

You should not use a template-driven intake document when a new request already has a complete specification. This skill is designed specifically for the first workflow phase to capture initial problems, goals, and constraints before downstream planning begins.