deliverable-setup

Automating deliverable archetype onboarding involves collecting team-specific settings and writing them to a .squad/archetype-config.json file. This defines output filenames, schema handling, and playbook steps to ensure consistent delivery workflows.

A deliverable archetype configuration file stores centralized settings per team, including output filenames, schema paths, playbook steps, and import hooks. It standardizes how deliverables are produced and consumed across the squad during onboarding and reconfiguration.

To set up playbook steps and schema handling, run the deliverable setup flow to collect archetype-specific settings. The process persists these configurations into the .squad/archetype-config.json file, establishing consistent governance for the team's outputs.

Yes, you can configure optional import hooks during team onboarding. The setup flow collects these settings and writes them to the .squad/archetype-config.json file, enabling automated post-aggregation processing for each deliverable team.

The archetype-config.json file includes fields for archetype, version, outputFilename, schemaPath, playbookSteps, importHook, and configuredAt. Writing these fields ensures consistent governance and standardized delivery workflows across the squad.

You need to reconfigure a deliverable archetype workflow when updating output file naming, adjusting schema paths, or modifying playbook steps. The setup flow applies these changes by overwriting the .squad/archetype-config.json file with the new configuredAt timestamp.