factory-intake
Skill0 starsChanged 49 days agoLicence not identifiedView on GitHub
The software factory's front door — turn an idea into a live, Access-gated preview you can approve from your phone, then ship it public. Use when the user hands over an idea and wants it built end to end with a decision point at the end — "build me this", "spin up a candidate for this idea", "I have an idea for a small site", "factory this". Runs research, at most three batched question rounds, commits a spec, scaffolds a public repo with CI and a required-check ruleset, delegates the build to the factory-build workflow, waits for the certificate, smoke-tests through an Access service token, scores once with codex, pushes a notification and asks Ship / Iterate / Stop, then promotes through merge-pr-with-gate and deletes the previews. Greenfield and stateless only in v1; not for changing an existing site (v2), not for bug fixes from issues (use factory-issue-fix). Not a Workflow wrapper; this is a session-long process skill.
- Reads credentials
- Deletes or force-pushes
- Installs packages
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- RickWyatt-me/dark-factorytheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- RickWyatt-me/dark-factory★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-boardSkill
- critic-gated-buildSkill
- file-concernsSkill
- implement-issueSkill
- parallel-build-orchestratorSkill
- pr-workflowSkill
- resolve-merge-conflictSkill
- scrutineer-autopilotSkill
- shipSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.