workflow-template-seeder

To generate a runnable Next.js template from a brief spec, provide a short specification defining the slug and integrations, and the seeder orchestrates existing skills to output a ready-to-run directory with scaffold, README, and metadata.

Skills-first orchestration for template creation chains existing Ship Faster skills to drive the generation and validation of new templates, ensuring consistent structure and minimal scope without leaking sensitive information into the final output.

A seeded template directory includes a clean Next.js scaffold, a README with installation steps, an env example file, and a metadata.json, providing a clean baseline with traceable inputs and outputs for immediate reuse.

You can create a Next.js storefront template without leaking secrets by providing a short spec at template_spec.md; the seeder workflow generates a shareable template under templates/ with no secrets and minimal scope.

Yes, you can use the template seeder for rapid scaffolding without manual setup by providing a brief spec defining the target user and required integrations, which automatically produces a ready-to-run template directory.

The limitation of using a brief spec to seed templates is that the output scope remains minimal by design, requiring predefined slug, target user, and integration details to successfully orchestrate existing Ship Faster skills into a clean baseline.