[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARET1R38C8H4FT2MYCVPPS":3,"skill-same:01M7ARET1R38C8H4FT2MYCVPPS":46},{"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":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ARET1R38C8H4FT2MYCVPPS","define-change",null,"Define and audit one lean SDLC v3 change through operator sign-off, without implementing it.","tigger-developer\u002Fsdlc","tigger-developer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43514058?v=4","01M7AREC1GA4M62DQ9WERQSSK7","tigger developer","01M7AREC2FNA0FF7ZT5EGH3PXK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fdefine-change\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: define-change\ndescription: Define and audit one lean SDLC v3 change through operator sign-off, without implementing it.\n---\n\n## Initialization prerequisite\n\nBefore creating or editing any ticket or candidate, require a readable\n`.sdlc\u002Fproject.yaml` declaring version 3 and no project-root `specs\u002F`\ndirectory. If either condition fails, stop this skill and tell the operator to\nrun `sdlc-init` from the project root. Do not allocate an ID, edit a record,\nstart a review or write code until initialization\u002Fmigration succeeds. Do not\nwork around the check, migrate by hand or infer permission to invoke the\ninitializer. Recheck the profile and layout before resuming.\n\n\nFollow `\u002Fopt\u002Fsdlc\u002Fdocs\u002FREADING.md`; reuse required documents already read in\nfull, unchanged and retained in context. A skill transition does not reload them.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`, `ISSUES.md`, `TESTING.md`, `CODING.md`,\n`ARCHITECTURE.md`, `GIT.md`, `DOCUMENTATION.md`, and `ORGMODE.md`, then the project\nprofile and its selected standards and authorities.\n\nWork on the project's recorded primary branch under `GIT.md` and\n`DELIVERY.md`. Do not create a feature branch during definition. Primary's\n`docs\u002Fwork.org` is the ticket authority; synchronize it and publish a minimal\nreservation under `DELIVERY.md` before treating a number as allocated. Record,\nreview and publish the definition on primary. Branching for code belongs to\nadmitted delivery, not ticket creation.\n\nDefinition defaults to **ATTENDED**. Ask the bounded clarification questions\nrequired to make the specification safe and context-independent. If the\noperator explicitly invokes **HANDS-OFF** definition mode, declare that mode\nand assume the operator is unavailable for the remainder of the definition\nwindow. In that mode, make sensible, reversible assumptions to keep the work\nmoving and record each one in the specification's decision log; do not stop for\nroutine status, incidental uncertainty, or approval requests. Stop only for a\ngenuine blocker, an unsafe or unauthorized action, the configured audit limit,\nor a decision that cannot be made safely from the available evidence. An\nordinary progress report is not a handback. Any interruption or operator\nresponse returns the skill to ATTENDED until HANDS-OFF is explicitly invoked\nagain.\n\nAsk no more than three concise free-form questions needed to define product\nscope. If operator direction raises unresolved test or design choices, ask no\nmore than three additional questions for each affected area. Do not use\nmultiple-choice UI.\n\nReserve the next shared numeric ID on primary under `DELIVERY.md`, using W\nfor a new work item. Reuse a defect's D identity when defining its fix. Create\n`tickets\u002FWNNN-descriptor\u002Fspec.org` from\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fv3\u002Fspec.org`. Include context, falsifiable acceptance\ncriteria, traced AT\u002FRT\u002FUT\u002FOT test definitions (including at least one meaningful\nUT under TESTING.md), edge cases, solution design,\nmandatory security impact, and a context-independent delivery handoff. Apply\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FORG-SCHEMA.md`: every AC carries `:ac:` and every test `:testdef:`.\nCreate `validation.org` by delivery admission; do not invent execution states\nin definition. Record reviews in `audits.yaml` under `AUDIT-RECORD.md`;\ndo not create parallel audit documents. Add or update the descriptive work item in `docs\u002Fwork.org`. Apply the\nchange-specific title, Org hierarchy, description-list, and semantic-emphasis\nrequirements in `ISSUES.md`; generic titles and visually unscannable drafts are\nnot ready for audit.\n\nIdentify affected documentation in Delivery Handoff. Where neither AT nor RT is justified,\nrecord why OT\u002FUT evidence suffices for definition review; this permits delivery\nto skip test-code review, not to omit the final delivery-code gate.\n\nWhen annotations are present, apply the annotation-review contract in `ISSUES.md`\nbefore audit or sign-off. Reconcile feedback as a batch, retain unresolved items,\nand move resolved annotations with their dispositions to `feedback.yaml` before\nremoving them from the specification. Only the agent edits the specification body;\na question is not an instruction. Include the feedback log as audit evidence when\npresent. No annotation records, even resolved or empty ones, may remain at the gate.\n\nCopy the template's `#+SCHEMA:` version. Keep `Synopsis` distinct from the\nchange-specific `#+TITLE:`, with its eight level-two categories and short bullets.\nIts summary must accurately and completely represent the detail below\nits section break. Load `\u002Fopt\u002Fsdlc\u002Fskills\u002Fdefinition-audit\u002FSKILL.md` and conduct\nthe composite review internally in this session. Address **every** finding as a batch:\nremediate valid findings and challenge incorrect or out-of-scope findings with\nevidence under `\u002Fopt\u002Fsdlc\u002Fdocs\u002FAUDITS.md`. Raise doubtful or unresolved disputes\nto the operator; never silently waive findings or expand scope to obtain a PASS.\nDo not launch an external reviewer.\n\nAfter current internal PASS is recorded in `audits.yaml`, move the work\nitem to `REVIEW`. Self-review requires no external verdict; an explicitly requested independent\nreview uses the same canonical record with its actual method.\nNever copy the verdict into\nspec metadata. Open the specification with the previewer selected by `MAIN.md`\nand return it for operator sign-off. Preview is presentation, not a gate. After\nexplicit sign-off, record `APPROVED YYYY-MM-DD` in `OPERATOR_SIGNOFF`, adding scope\nonly where approval is limited; follow `DOCUMENTATION.md`, not conversation narration.\nMove its work item to `ACTIVE` unless the operator explicitly defers delivery;\nretain `REVIEW` and the hold in that case. Design approval never lifts a hold.\nDo not implement code.\n\nReview orchestration and evidence ownership follow `AUDITS.md`; current-session\nreview uses `SELF-AUDIT.md`. No external call or new reviewer is authorized.\n","## Initialization prerequisite\n\nBefore creating or editing any ticket or candidate, require a readable\n`.sdlc\u002Fproject.yaml` declaring version 3 and no project-root `specs\u002F`\ndirectory. If either condition fails, stop this skill and tell the operator to\nrun `sdlc-init` from the project root. Do not allocate an ID, edit a record,\nstart a review or write code until initialization\u002Fmigration succeeds. Do not\nwork around the check, migrate by hand or infer permission to invoke the\ninitializer. Recheck the profile and layout before resuming.\n\n\nFollow `\u002Fopt\u002Fsdlc\u002Fdocs\u002FREADING.md`; reuse required documents already read in\nfull, unchanged and retained in context. A skill transition does not reload them.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`, `ISSUES.md`, `TESTING.md`, `CODING.md`,\n`ARCHITECTURE.md`, `GIT.md`, `DOCUMENTATION.md`, and `ORGMODE.md`, then the project\nprofile and its selected standards and authorities.\n\nWork on the project's recorded primary branch under `GIT.md` and\n`DELIVERY.md`. Do not create a feature branch during definition. Primary's\n`docs\u002Fwork.org` is the ticket authority; synchronize it and publish a minimal\nreservation under `DELIVERY.md` before treating a number as allocated. Record,\nreview and publish the definition on primary. Branching for code belongs to\nadmitted delivery, not ticket creation.\n\nDefinition defaults to **ATTENDED**. Ask the bounded clarification questions\nrequired to make the specification safe and context-independent. If the\noperator explicitly invokes **HANDS-OFF** definition mode, declare that mode\nand assume the operator is unavailable for the remainder of the definition\nwindow. In that mode, make sensible, reversible assumptions to keep the work\nmoving and record each one in the specification's decision log; do not stop for\nroutine status, incidental uncertainty, or approval requests. Stop only for a\ngenuine blocker, an unsafe or unauthorized action, the configured audit limit,\nor a decision that cannot be made safely from the available evidence. An\nordinary progress report is not a handback. Any interruption or operator\nresponse returns the skill to ATTENDED until HANDS-OFF is explicitly invoked\nagain.\n\nAsk no more than three concise free-form questions needed to define product\nscope. If operator direction raises unresolved test or design choices, ask no\nmore than three additional questions for each affected area. Do not use\nmultiple-choice UI.\n\nReserve the next shared numeric ID on primary under `DELIVERY.md`, using W\nfor a new work item. Reuse a defect's D identity when defining its fix. Create\n`tickets\u002FWNNN-descriptor\u002Fspec.org` from\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fv3\u002Fspec.org`. Include context, falsifiable acceptance\ncriteria, traced AT\u002FRT\u002FUT\u002FOT test definitions (including at least one meaningful\nUT under TESTING.md), edge cases, solution design,\nmandatory security impact, and a context-independent delivery handoff. Apply\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FORG-SCHEMA.md`: every AC carries `:ac:` and every test `:testdef:`.\nCreate `validation.org` by delivery admission; do not invent execution states\nin definition. Record reviews in `audits.yaml` under `AUDIT-RECORD.md`;\ndo not create parallel audit documents. Add or update the descriptive work item in `docs\u002Fwork.org`. Apply the\nchange-specific title, Org hierarchy, description-list, and semantic-emphasis\nrequirements in `ISSUES.md`; generic titles and visually unscannable drafts are\nnot ready for audit.\n\nIdentify affected documentation in Delivery Handoff. Where neither AT nor RT is justified,\nrecord why OT\u002FUT evidence suffices for definition review; this permits delivery\nto skip test-code review, not to omit the final delivery-code gate.\n\nWhen annotations are present, apply the annotation-review contract in `ISSUES.md`\nbefore audit or sign-off. Reconcile feedback as a batch, retain unresolved items,\nand move resolved annotations with their dispositions to `feedback.yaml` before\nremoving them from the specification. Only the agent edits the specification body;\na question is not an instruction. Include the feedback log as audit evidence when\npresent. No annotation records, even resolved or empty ones, may remain at the gate.\n\nCopy the template's `#+SCHEMA:` version. Keep `Synopsis` distinct from the\nchange-specific `#+TITLE:`, with its eight level-two categories and short bullets.\nIts summary must accurately and completely represent the detail below\nits section break. Load `\u002Fopt\u002Fsdlc\u002Fskills\u002Fdefinition-audit\u002FSKILL.md` and conduct\nthe composite review internally in this session. Address **every** finding as a batch:\nremediate valid findings and challenge incorrect or out-of-scope findings with\nevidence under `\u002Fopt\u002Fsdlc\u002Fdocs\u002FAUDITS.md`. Raise doubtful or unresolved disputes\nto the operator; never silently waive findings or expand scope to obtain a PASS.\nDo not launch an external reviewer.\n\nAfter current internal PASS is recorded in `audits.yaml`, move the work\nitem to `REVIEW`. Self-review requires no external verdict; an explicitly requested independent\nreview uses the same canonical record with its actual method.\nNever copy the verdict into\nspec metadata. Open the specification with the previewer selected by `MAIN.md`\nand return it for operator sign-off. Preview is presentation, not a gate. After\nexplicit sign-off, record `APPROVED YYYY-MM-DD` in `OPERATOR_SIGNOFF`, adding scope\nonly where approval is limited; follow `DOCUMENTATION.md`, not conversation narration.\nMove its work item to `ACTIVE` unless the operator explicitly defers delivery;\nretain `REVIEW` and the hold in that case. Design approval never lifts a hold.\nDo not implement code.\n\nReview orchestration and evidence ownership follow `AUDITS.md`; current-session\nreview uses `SELF-AUDIT.md`. No external call or new reviewer is authorized.\n",{"name":5,"description":7},"master","b1f296c62065adad981aac0d56b1a457fafa14e3","skills\u002Fdefine-change","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc","https:\u002F\u002Fgithub.com\u002Ftigger-developer","https:\u002F\u002Ftigger.dev","TA • developer • builder • tinkerer • stargazer","2026-11-14 23:08:57",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tigger-developer\u002Fsdlc --skill define-change",{"tool":38,"command":39},"bunx","bunx skills add tigger-developer\u002Fsdlc --skill define-change",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tigger-developer\u002Fsdlc --skill define-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fdefine-change\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ARG7HEQNQDHYR87YXVE332","useful-be","Load the minimum project and engineering context needed for useful work.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fuseful-be\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7ARG4QYZ67SRZMA928N84QE","test-code-audit","Self-review written tests before implementation in the current author context; never launch or act as an independent auditor.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-code-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ARG0CH4WZ59P6TSM3DW0H6","summarize-issues","Summarize a project's open work against its specifications and architecture. Advisory only; no file changes.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fsummarize-issues\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ARFXG6SMQ26NG9Y731GSB2","recommendations-please","Provide concrete expert recommendations for a technical decision without making file changes.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Frecommendations-please\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ARFSZVMXNCBC4BJ86RM3C9","pair-change","Run explicitly selected paired development with live operator validation and lean closure records.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fpair-change\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ARFMKRTJTVGAWAFQDXDQH4","migrate-legacy-acs-to-sdlc-v1","Archive and close a brownfield project's legacy GitHub tickets while reconciling its SDLC v1 acceptance-criteria ledger and documentation before SDLC v3 initialization. Invoke only when the operator requests this migration.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fmigrate-legacy-acs-to-sdlc-v1\u002FSKILL.md",[],[]]