software-factory
Skill0 starsChanged todayMITView on GitHub
Scaffold, configure, and operate an autonomous, issue-driven software factory for any repository. Sets up token-scrubbed AFK implementation workflows, dependency-aware queue promotion, state-machine labels, and PR description synthesis.
- Reads credentials
12 other projects use a version of this.
Adopted by
Most recently taken up by
- anis-dr/skillstheir own version, first seen Nov 16, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- hamlim/skillstheir own version, first seen Nov 8, 2026
- op3616windows/skillstheir own version, first seen Nov 8, 2026
- Yeseh/skillstheir own version, first seen Nov 1, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- mattpocock/skills★ 325ksame name
- devcxl/mattpocock-skills-zh★ 543same name
- alexj11324/Mikka★ 87same name
- glassflow/tares★ 47same name
- HiteSit/real-scientist-skills★ 27same name
- anis-dr/skills★ 4same name
- malinskibeniamin/skills★ 4same name
- jddelia/software-factory★ 2same name
- christofferbergj/agent-skills★ 1same name
- hamlim/skills★ 1same name
2 more not listed
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 repository72 other files it gives its agents.
- animate-expoSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- apple-designSkill
- ask-emilSkill
- ask-mattSkill
- ask-sonnerSkill
- better-typographySkill
- break-uiSkill
- chief-of-staffSkill
- choreographSkill
- claritySkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- cold-emailSkill
- content-strategySkill
- copywritingSkill
- croSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- frontend-designSkill
- gesturesSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- learn-tasteSkill
- loop-meSkill
- marketing-psychologySkill
- migrate-to-shoehornSkill
- mobile-nativeSkill
- persuasionSkill
- pick-ui-librarySkill
- prisma-client-apiSkill
- programmatic-seoSkill
- prototypeSkill
- prototype-variantsSkill
- prSkill
- remove-animationsSkill
- researchSkill
- retroSkill
- review-animationsSkill
- scaffold-exercisesSkill
- seo-auditSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- Skillpack Self-testSkill
- supabase-postgres-best-practicesSkill
- tddSkill
- teachSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
PR Reflection: Before stopping, the agent writes its rationale to /tmp/factory-pr-body.md.
- Distinctive: line 36
Remote and Tracking: Verify the repository has a GitHub origin remote:
- Very specific: line 42
Existing Workflows: Check whether .github/workflows/agent-implement.yml or .github/workflows/agent-promote-queued.yml already exist.
- Very specific: line 52
Workflow Directory: Ensure .github/workflows and .github/scripts exist:
- Very specific: line 62
Ensure executable permissions: chmod +x .github/scripts/build-pr-body.sh.
- Very specific: line 98
Done when: All five labels exist in gh label list, workflow permissions return write access, and the model secret is stored.
- Distinctive: line 107
When an issue is specified with clear acceptance criteria and verification commands:
- Very specific: line 112
Dependent implementation: If an issue depends on unfinished work, link blockers and apply agent:queued:
- Distinctive: line 130
When a run completes:
- Distinctive: line 132
Verify CI test passes on the PR branch.
- Distinctive: line 142
When a factory run exits without opening a PR:
- Very specific: line 150
0 commits produced: Check the run comment for .factory-blocked.txt output.
- Distinctive: line 152
Stale lock: If a runner was killed mid-flight, manually release the lock:
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Software Factory
Scaffold, configure, and operate an autonomous software factory for a software repository. The software factory turns GitHub issues into draft pull requests via unattended, token-scrubbed agent runs triggered by issue labels.
Humans triage, authorize, and merge. The factory implements, validates, and reports. Nothing in this system merges to the default branch on its own.
Core Concepts & Leading Words
- Leash: CI checks (
typecheck,test,build, linter) define the leash. An agent must run and satisfy all local checks before concluding; remote CI displays red/green status on the draft PR prior to human review. - Scrubbed Environment: The agent executes inside a stripped shell (
env -i) with zero access toGITHUB_TOKENor repository secrets. - Lock: The
agent:in-progresslabel functions as a mutual exclusion lock to prevent duplicate concurrent runs on the same issue. - Deterministic Branch: Work is committed to a per-issue branch named
agent/issue-<N>-<slug>. The orchestrator rebases onorigin/mainand force-pushes to guarantee idempotent recovery. - Native Blockers: Automatic queue progression uses GitHub's native issue dependencies (
dependencies/blocked_by). - PR Reflection: Before stopping, the agent writes its rationale to
/tmp/factory-pr-body.md. The orchestrator wraps this file, neutralizes closing keywords, appends git diffstats, and opens a draft PR.
Consult deep reference documents when working on specific subsystems:
- State machine & label transitions:
references/state-machine.md - Security boundaries & sandboxing:
references/trust-boundaries.md - Diagnosing failures & rate limits:
references/troubleshooting.md
Steps
1. Inspect the Target Repository
Examine the target repository to determine configuration parameters before scaffolding:
- Remote and Tracking: Verify the repository has a GitHub origin remote:
git remote get-url origin gh repo view --json nameWithOwner,defaultBranchRef - Verification Commands: Identify the project's canonical test, build, and typecheck commands from configuration files (
package.json,Cargo.toml,pyproject.toml,Makefile, etc.). - Existing Workflows: Check whether
.github/workflows/agent-implement.ymlor.github/workflows/agent-promote-queued.ymlalready exist.
Done when: The repository slug, default branch, and test/build commands are recorded.
2. Scaffold Workflow and Script Assets
Copy the factory templates into the target repository:
- Workflow Directory: Ensure
.github/workflowsand.github/scriptsexist:mkdir -p .github/workflows .github/scripts - Install Workflows:
- Copy
assets/workflows/agent-implement.ymlto.github/workflows/agent-implement.yml. - Copy
assets/workflows/agent-promote-queued.ymlto.github/workflows/agent-promote-queued.yml. - Adapt the verification commands in
agent-implement.ymlto match the target repository's stack (e.g.npm test,cargo test,pytest).
- Copy
- Install PR Body Renderer:
- Copy
assets/scripts/build-pr-body.shto.github/scripts/build-pr-body.sh. - Ensure executable permissions:
chmod +x .github/scripts/build-pr-body.sh.
- Copy
You can perform this step automatically by running the bundled setup script:
./scripts/init-factory.sh --install-to /path/to/target-repoDone when: Both workflows and build-pr-body.sh exist in the target repository and pass bash -n .github/scripts/build-pr-body.sh.
3. Create Labels and Configure GitHub Permissions
The factory requires five state-machine labels and GitHub Actions write permissions to open pull requests:
- Create Labels:
gh label create "ready-for-agent" --color "0E8A16" --description "Fully specified; triage signal" --force gh label create "agent:implement" --color "1D76DB" --description "The trigger: factory implements this issue" --force gh label create "agent:queued" --color "FBCA04" --description "Promote when all blockers close" --force gh label create "agent:in-progress" --color "D93F0B" --description "Lock: active factory run holds this issue" --force gh label create "agent:blocked" --color "B60205" --description "Needs human triage before retry" --force - Grant Workflow PR Permissions:
GitHub Actions requires explicit write permissions to create pull requests with
GITHUB_TOKEN. Enable this via the GitHub CLI:gh api --method PUT "repos/{owner}/{repo}/actions/permissions/workflow" \ -F default_workflow_permissions=write \ -F can_approve_pull_request_reviews=true - Set Agent API Secret:
Configure the LLM runner API key as a repository secret (e.g.,
OPENCODE_API_KEY,ANTHROPIC_API_KEY):gh secret set OPENCODE_API_KEY
Done when: All five labels exist in gh label list, workflow permissions return write access, and the model secret is stored.
4. Operate the Factory Loop
Manage day-to-day issue implementation using the state machine:
A. Triage and Queue an Issue
When an issue is specified with clear acceptance criteria and verification commands:
- Immediate implementation: Apply
agent:implementto trigger the factory immediately:gh issue edit <N> --add-label "agent:implement" - Dependent implementation: If an issue depends on unfinished work, link blockers and apply
agent:queued:
Link blockers using GitHub's native issue dependencies API:gh issue edit <N> --add-label "agent:queued"BLOCKER_ID=$(gh api "repos/{owner}/{repo}/issues/<BLOCKER_N>" --jq .id) gh api --method POST "repos/{owner}/{repo}/issues/<N>/dependencies/blocked_by" -F issue_id="$BLOCKER_ID"
B. Monitor Execution
Track running jobs via GitHub CLI:
gh run list --workflow=agent-implement.yml
gh run watch <RUN_ID>C. Review and Merge
When a run completes:
- Locate the draft PR linked in the issue comments.
- Verify CI test passes on the PR branch.
- Review the code diff and the agent's six-section summary in the PR description.
- Convert from draft to ready-for-review and merge using a human account.
Done when: The issue is labeled agent:in-progress during execution, followed by a draft PR opening with Closes #N.
5. Diagnose and Recover from Failures
When a factory run exits without opening a PR:
- Check Failure Label: A failed run automatically removes
agent:implementand appliesagent:blocked. - Inspect Run Logs:
gh run view <RUN_ID> --log-failed - Diagnose Common Causes:
- 0 commits produced: Check the run comment for
.factory-blocked.txtoutput. The agent encountered an ambiguous specification or unmet dependency. - Check failure: The agent could not pass local test/typecheck suites within the timeout.
- Stale lock: If a runner was killed mid-flight, manually release the lock:
gh issue edit <N> --remove-label "agent:in-progress"
- 0 commits produced: Check the run comment for
- Retry: Fix the root cause in the issue description or codebase, then re-add
agent:implement:gh issue edit <N> --remove-label "agent:blocked" --add-label "agent:implement"
Done when: Stale locks are removed, blocking issues are resolved, and the retry run completes or logs a clear impediment.
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.

