[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4NARY8FWHK2RRWHBW3KD6":3,"skill-same:01M7F4NARY8FWHK2RRWHBW3KD6":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7F4NARY8FWHK2RRWHBW3KD6","factory",null,"Hand ready tickets to the factory, resolve holds, resume stopped work, deliver skipped work, or pause and resume one repository.","lutzseverino\u002Fpostern","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7F4MESFQZ45SVN7DQD7Y8D4",0,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffactory\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: factory\ndescription: Hand ready tickets to the factory, resolve holds, resume stopped work, deliver skipped work, or pause and resume one repository.\n---\n\nA prompt or brief naming this skill is its invocation.\n\nWork in the repository the factory serves. Read `CONTRIBUTING.md`, the\ninstalled `factory-workflow`, `github-repository-configuration` and `comments`\nrules, and `.scriptorium\u002Fconfig.json` before acting. The guide and rules hold the requirements;\nthis skill supplies the method. Use the configured label roles rather than\nassuming the shipped strings. Read the issue's authoritative contract, comments,\nblockers, and any existing PR and handoff before choosing a path below.\n\n## Hand a ready ticket to the factory\n\n1. Check the contract's accepted revision and its validator notice, parent\n   readiness and open blockers under the guide and installed rules. Resolve\n   missing required inputs before seeking readiness.\n2. Choose the ticket's model, weighing its triage suggestion. Prefer a stronger\n   model for design judgment, ambiguous scope or a long cross-cutting change.\n   Use the rules' model-label syntax and metadata; the host operator resolves\n   an unavailable or disallowed model rather than substituting one silently.\n3. Apply the readiness policy through `triage`'s readiness command. With an App\n   or bot credential in a factory repository, hand the reviewed revision,\n   suggested readiness, model and route labels, and blockers to an authorized\n   person. Report pickup only when the factory actually records it.\n4. For a parent held under the latest-link-time fallback, wait until its latest\n   ticket link is visible in the timeline, then remove and re-add its ready\n   label after that timestamp. Each ticket still needs its own readiness.\n   With complete authorized link history, use the installed actor-history rule.\n\n## Read a hold\n\nRead the factory's run comment and current labels first. Match the reason\nrather than clearing a state label to see what happens:\n\n| Observation | Next action |\n| --- | --- |\n| Refused readiness or parent not ready | Verify the exact revision and the authorized person's readiness, then the parent's contract and link history. |\n| Model-label error | Reconcile the ticket's single model label with the chosen model; ask the host operator about resolvability or the allowlist. |\n| Repository configuration refused | Ask the host operator to verify the serving release and configuration acceptance. Keep the issue's evidence available. |\n| Open blockers, capacity or usage drain | Resolve blockers or wait for the host's gate to clear; no label reset bypasses it. |\n| Repository or release hold | Find the labelled open items and use Pause and resume below. |\n| Running or paused | Read the run comment; the factory owns the run and its automatic resumption. |\n| A `state:` stop | Use Resume stopped work below. |\n| Failed | Address the failure the run comment names first, then remove the failed label to request a retry subject to pickup gates. |\n| Skip | Use the directly launched path below; clearing a waiting marker does not request a factory retry. |\n\nIf no comment explains a held issue, ask the host operator for its reason; a\nhost with no cached valid configuration cannot comment on the issue. Keep\ncredentials and secret host material out of tracker records.\n\n## Take the skip route\n\nFor work excluded by the installed rules, arrange the ready, model and skip\nlabels together through the authorized readiness path. Launch `implement`\ndirectly with the contract, evidence, decisions, issue link and delivery role.\nThe worker opens the PR and records its handoff as\n`.repo-standards\u002Frules\u002Fcomments.md#delivery-records` says. Continue as the orchestrating agent through `babysit` from that handoff;\napply its current-head owner-approval gate when designated.\n\nFor an unanswered owner question, retain the skip marker and the question's\nworkflow state.\nAfter resolution and any required renewed readiness, resume the worker if no\nPR exists, or continue the same open PR and its handoff. Live host access gates\nonly the authorized live steps.\n\nA live-acceptance ticket takes this route. Its worker records the ticket's live\nacceptance on it, as `.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says,\ninstead of opening a PR, and reports back. It closes only once\nits live acceptance is recorded on it, never on a merge; its source ticket's PR\nlinks it without a closing reference. A time-bounded host access grant belongs to the\norchestrating agent that asked the maintainer for it, which records the workers\nusing it. Workers never end it: it ends when the last of them reports back, or\nat its own time bound.\n\n## Resume stopped work\n\nAnswer the question through the guide's owner-question route, posting as\n`.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says, and meet the installed\nQuestions and stops rule's conditions for a changed contract. Then return the\nissue to `state:ready`, which is the only way to resume it: never clear another\nlabel for it, and never merge the stopped PR by hand. For skipped work,\ncontinue as Take the skip route says instead.\n\n## Pause and resume one repository\n\n1. Read `labels.hold` in the repository configuration and locate every open\n   issue and PR carrying it. If the key is absent, arrange a compatible\n   configuration with the owner before attempting a pause. Distinguish this\n   repository hold from the release hold and the factory's per-run paused state.\n2. For an expedited change with an existing PR, put the hold on that PR. If\n   work starts before its PR exists, put it on the change's issue first and\n   record why the repository is paused and which change will carry it, as\n   `.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says.\n3. Deliver the expedited change outside factory pickup: launch a worker\n   directly or implement as the orchestrating agent. A held repository launches\n   no new work. An already-open factory PR can instead carry the hold and finish\n   through its exempt merge relaunch. Runs already started finish without\n   merging while another open item holds the repository.\n4. Once the expedited PR opens, add the hold to it before removing the hold\n   from the issue. Verify that transfer on both items. Before merging, inspect\n   all other open items carrying either configured hold: only the PR being\n   merged is exempt, so a forgotten issue hold would block it too.\n5. Finish validation, applicable reviews and merge authorization through\n   `babysit`. Its merge check exempts this PR's own hold, allowing the expedited\n   change to merge. The PR's closure ends that hold automatically. To resume a\n   deliberate pause without merging, remove the hold from the item that carries\n   it; leave other owners' holds alone. Confirm no remaining open hold and\n   report the resulting state. A release hold still restricts merges separately.\n\n\u003C!-- Seam (deferred): Scriptorium configuration reads; consumers: 6; extraction proposed in https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fissues\u002F967. -->\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: contract, readiness, delivery, question and credential\n  requirements. When it is missing, use the installed rules and\n  hand off any unresolved delivery or authorization question on the issue or PR.\n- The installed `factory-workflow` and `github-repository-configuration` rules,\n  located with `repository-standards`. When they are missing, use the guide\n  and configured roles; ask the owner before a route or merge-ownership decision\n  that those sources do not settle.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  sections the posting steps name. When it is missing, post each record the\n  steps name as one comment.\n- `.scriptorium\u002Fconfig.json`: configured label roles. When it is missing or\n  unreadable, perform read-only diagnosis and ask the owner to establish the\n  factory configuration before changing factory labels.\n","A prompt or brief naming this skill is its invocation.\n\nWork in the repository the factory serves. Read `CONTRIBUTING.md`, the\ninstalled `factory-workflow`, `github-repository-configuration` and `comments`\nrules, and `.scriptorium\u002Fconfig.json` before acting. The guide and rules hold the requirements;\nthis skill supplies the method. Use the configured label roles rather than\nassuming the shipped strings. Read the issue's authoritative contract, comments,\nblockers, and any existing PR and handoff before choosing a path below.\n\n## Hand a ready ticket to the factory\n\n1. Check the contract's accepted revision and its validator notice, parent\n   readiness and open blockers under the guide and installed rules. Resolve\n   missing required inputs before seeking readiness.\n2. Choose the ticket's model, weighing its triage suggestion. Prefer a stronger\n   model for design judgment, ambiguous scope or a long cross-cutting change.\n   Use the rules' model-label syntax and metadata; the host operator resolves\n   an unavailable or disallowed model rather than substituting one silently.\n3. Apply the readiness policy through `triage`'s readiness command. With an App\n   or bot credential in a factory repository, hand the reviewed revision,\n   suggested readiness, model and route labels, and blockers to an authorized\n   person. Report pickup only when the factory actually records it.\n4. For a parent held under the latest-link-time fallback, wait until its latest\n   ticket link is visible in the timeline, then remove and re-add its ready\n   label after that timestamp. Each ticket still needs its own readiness.\n   With complete authorized link history, use the installed actor-history rule.\n\n## Read a hold\n\nRead the factory's run comment and current labels first. Match the reason\nrather than clearing a state label to see what happens:\n\n| Observation | Next action |\n| --- | --- |\n| Refused readiness or parent not ready | Verify the exact revision and the authorized person's readiness, then the parent's contract and link history. |\n| Model-label error | Reconcile the ticket's single model label with the chosen model; ask the host operator about resolvability or the allowlist. |\n| Repository configuration refused | Ask the host operator to verify the serving release and configuration acceptance. Keep the issue's evidence available. |\n| Open blockers, capacity or usage drain | Resolve blockers or wait for the host's gate to clear; no label reset bypasses it. |\n| Repository or release hold | Find the labelled open items and use Pause and resume below. |\n| Running or paused | Read the run comment; the factory owns the run and its automatic resumption. |\n| A `state:` stop | Use Resume stopped work below. |\n| Failed | Address the failure the run comment names first, then remove the failed label to request a retry subject to pickup gates. |\n| Skip | Use the directly launched path below; clearing a waiting marker does not request a factory retry. |\n\nIf no comment explains a held issue, ask the host operator for its reason; a\nhost with no cached valid configuration cannot comment on the issue. Keep\ncredentials and secret host material out of tracker records.\n\n## Take the skip route\n\nFor work excluded by the installed rules, arrange the ready, model and skip\nlabels together through the authorized readiness path. Launch `implement`\ndirectly with the contract, evidence, decisions, issue link and delivery role.\nThe worker opens the PR and records its handoff as\n`.repo-standards\u002Frules\u002Fcomments.md#delivery-records` says. Continue as the orchestrating agent through `babysit` from that handoff;\napply its current-head owner-approval gate when designated.\n\nFor an unanswered owner question, retain the skip marker and the question's\nworkflow state.\nAfter resolution and any required renewed readiness, resume the worker if no\nPR exists, or continue the same open PR and its handoff. Live host access gates\nonly the authorized live steps.\n\nA live-acceptance ticket takes this route. Its worker records the ticket's live\nacceptance on it, as `.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says,\ninstead of opening a PR, and reports back. It closes only once\nits live acceptance is recorded on it, never on a merge; its source ticket's PR\nlinks it without a closing reference. A time-bounded host access grant belongs to the\norchestrating agent that asked the maintainer for it, which records the workers\nusing it. Workers never end it: it ends when the last of them reports back, or\nat its own time bound.\n\n## Resume stopped work\n\nAnswer the question through the guide's owner-question route, posting as\n`.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says, and meet the installed\nQuestions and stops rule's conditions for a changed contract. Then return the\nissue to `state:ready`, which is the only way to resume it: never clear another\nlabel for it, and never merge the stopped PR by hand. For skipped work,\ncontinue as Take the skip route says instead.\n\n## Pause and resume one repository\n\n1. Read `labels.hold` in the repository configuration and locate every open\n   issue and PR carrying it. If the key is absent, arrange a compatible\n   configuration with the owner before attempting a pause. Distinguish this\n   repository hold from the release hold and the factory's per-run paused state.\n2. For an expedited change with an existing PR, put the hold on that PR. If\n   work starts before its PR exists, put it on the change's issue first and\n   record why the repository is paused and which change will carry it, as\n   `.repo-standards\u002Frules\u002Fcomments.md#disclaimers` says.\n3. Deliver the expedited change outside factory pickup: launch a worker\n   directly or implement as the orchestrating agent. A held repository launches\n   no new work. An already-open factory PR can instead carry the hold and finish\n   through its exempt merge relaunch. Runs already started finish without\n   merging while another open item holds the repository.\n4. Once the expedited PR opens, add the hold to it before removing the hold\n   from the issue. Verify that transfer on both items. Before merging, inspect\n   all other open items carrying either configured hold: only the PR being\n   merged is exempt, so a forgotten issue hold would block it too.\n5. Finish validation, applicable reviews and merge authorization through\n   `babysit`. Its merge check exempts this PR's own hold, allowing the expedited\n   change to merge. The PR's closure ends that hold automatically. To resume a\n   deliberate pause without merging, remove the hold from the item that carries\n   it; leave other owners' holds alone. Confirm no remaining open hold and\n   report the resulting state. A release hold still restricts merges separately.\n\n\u003C!-- Seam (deferred): Scriptorium configuration reads; consumers: 6; extraction proposed in https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fissues\u002F967. -->\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: contract, readiness, delivery, question and credential\n  requirements. When it is missing, use the installed rules and\n  hand off any unresolved delivery or authorization question on the issue or PR.\n- The installed `factory-workflow` and `github-repository-configuration` rules,\n  located with `repository-standards`. When they are missing, use the guide\n  and configured roles; ask the owner before a route or merge-ownership decision\n  that those sources do not settle.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  sections the posting steps name. When it is missing, post each record the\n  steps name as one comment.\n- `.scriptorium\u002Fconfig.json`: configured label roles. When it is missing or\n  unreadable, perform read-only diagnosis and ask the owner to establish the\n  factory configuration before changing factory labels.\n",{"name":5,"description":7},"main","448e2ed8cdf04967d08e8f682dbcb135896c8185",".agents\u002Fskills\u002Ffactory","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 01:04:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add lutzseverino\u002Fpostern --skill factory",{"tool":37,"command":38},"bunx","bunx skills add lutzseverino\u002Fpostern --skill factory",{"tool":40,"command":41},"pnpm","pnpm dlx skills add lutzseverino\u002Fpostern --skill factory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffactory\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"CREDITS.md","REFERENCE","参考文档",99,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffactory\u002FCREDITS.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F4S3V789SV39G7XQQ021FS","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F4RZQ3SV81GM59D7FCZE98","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7F4RTBB780C72G2GP3GH904","triage","Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F4RN7REXARMQ18V8WZB29H","to-tickets","Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7F4RH5ZSNGESE2ECB4JH7J7","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7F4RF1VJMBJFQP4K974PRSZ","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]