Puddleworks Factory

Write a first draft of a swamp app from a puddleworks.dev/app-spec/v1 spec: an extension whose run method takes the spec's inputs, tests for it, a workflow with the same inputs, the publish manifest, README, LICENSE and a CLAUDE.md section. The spec can be a file path, an https URL or inline JSON, written by a person or another tool. Files go into the root of a checkout of the app's own repo; nothing is committed or pushed. The factory-build skill drives this end to end.

Write a puddleworks.dev/build-result/v1 for the last draft of an app spec: the extension, its entry point, the repository, the branch or commit, and the pull request once there is one, and what was published. Run it after the draft is pushed, again once the pull request is open, and again once the extension is published. The result is recorded as a resource on the puddleworks-factory model and, with out, written to a JSON file that anyone can read.

Write a starter puddleworks.dev/app-spec/v1 from an agreed puddleworks.dev/outcome-spec/v1. It copies what the outcome spec says (title, purpose, out of scope, who agreed it and when) and links back to where it was agreed. The app name is only a suggestion, and inputs, output, settings and delivery method are left blank for the builder; the prefill resource lists them. The starter does not pass @puddleworks/puddleworks-factory-build until they are filled in.

Before publishing, check an app's repo and recommend sharing it publicly or keeping it private. A licence, a repository link and 100% quality are required for public; paths, hosts, addresses or emails that look internal, or spec wording about who the app is for, recommend private; secrets block public. The answer is recorded as a visibility resource on the puddleworks-factory model. It changes nothing: the builder decides.

After the independent review, check an app is ready to publish: the review report matches the manifest's name and version with no issue or pending verdict, every acceptance criterion in spec/ maps to tests that exist or a manual check (spec/acceptance.json), and the visibility check allows the manifest's visibility. The answer, with a one-screen summary to confirm publishing against, is recorded as a readiness resource on the puddleworks-factory model. It changes nothing.