area-intake

Project initiation and area setup requires gathering context like objectives, in-scope repositories, system dependencies, and constraints. This skill collects those details to produce a clear problem statement, execution checklist, and risk assessment for your new initiatives.

Onboarding for a new development area is structured by collecting area names, objectives, and system constraints. This process outputs a defined problem statement and an execution checklist to streamline workflow setup for new product teams.

Yes, the intake process explicitly assesses potential risks before configuring new workflows. By collecting constraints like dates and approvals alongside system dependencies, it generates a risk assessment to guide your area-specific execution.

Workflow setup handles repository mapping and system dependencies by collecting them as essential context. It identifies in-scope repositories and system dependencies to ensure your execution checklist accurately reflects the technical constraints of the area.

Project initiation context gathering requires you to provide the area name, objectives, in-scope repositories, system dependencies, and constraints like dates and approvals. These inputs drive the generation of your problem statement and execution checklist.