[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARENRB5582GTXGPS45MWJ9":3,"skill-same:01M7ARENRB5582GTXGPS45MWJ9":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},"01M7ARENRB5582GTXGPS45MWJ9","defect-raise",null,"Capture and register a reported defect with observed and expected behaviour, available evidence and impact, without requiring diagnosis or designing or implementing its fix.","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\u002Fdefect-raise\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: defect-raise\ndescription: Capture and register a reported defect with observed and expected behaviour, available evidence and impact, without requiring diagnosis or designing or implementing its fix.\n---\n\n# Raise a defect\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## Purpose and authority\n\nProduce a useful, traceable defect ticket. Raising a defect does not invoke\n`define-change`, approve delivery, start an audit or authorize implementation.\nA report may be actionable for investigation before its cause, reproduction or\ncorrect solution is known. Do not turn reporting into a design gate.\n\nFollow the session's project routing and `READING.md`; reuse retained context.\nFor an initialized SDLC project, read the project's requirement\u002Fwork authorities,\n`ISSUES.md`'s bug and identifier rules, the primary-branch ticket reservation\ncontract in `DELIVERY.md`, and `ORGMODE.md` for the record. Apply only ticket\nregistration here, not delivery admission or the full specification template.\nThe initialization prerequisite above applies to this skill. Do not create a\nforge issue without explicit authority.\n\n## Capture the report\n\nStart from the operator's evidence. Ask only questions needed to identify the\nproblem or make the report useful; record other missing facts as unknown.\nInclude, where known:\n\n- A specific title and short description of the failed user outcome.\n- Observed behaviour and expected behaviour, separately. Cite the requirement,\n  documented contract or operator expectation supporting the latter.\n- Reproduction steps, inputs and preconditions; frequency or intermittency.\n- Affected environment, version or revision, and last known working version.\n- Evidence references, such as exact errors, logs or screenshots, with provenance.\n- Impact, affected users or operations, and any known workaround.\n- Related requirements, tickets and possible duplicates.\n- Unknowns and the next useful investigation question.\n\nDistinguish reported observations, independently reproduced behaviour and\nhypotheses. Do not claim reproduction or a cause without evidence. A credible\nreport without reproduction steps is still recordable. If the expected behaviour\nis disputed or undocumented, preserve that uncertainty instead of inventing a\nrequirement, rejecting the report or converting it silently into a feature.\nRecord operator-assigned priority as such. Keep impact evidence separate from\nany proposed severity; do not invent release commitments.\n\nDescribe how a later check could distinguish the observed failure from the\nexpected behaviour when that is already clear. Formal acceptance criteria,\nAT\u002FRT\u002FUT\u002FOT definitions, root-cause analysis and solution design are not required\nto raise the defect. Do not run intrusive reproductions, change environments,\nwrite regression tests or expand into diagnosis merely to fill the report.\n\n## Register once\n\nSearch the authorized register and directly related records for duplicates.\nFor a confirmed duplicate, update the existing ticket with new evidence and\nprovenance; do not allocate another number. Record a possible relationship\nwithout merging distinct reports merely because their symptoms resemble each\nother. Preserve existing operator edits and evidence.\n\nFor a new SDLC ticket, synchronize primary and reserve an ID using DELIVERY's\ncollision-prevention protocol. Use the same namespace as features and spikes,\nusing D and one more than the highest number reserved across W, D, S and\nlegacy tickets. Never use a defect-only counter. Do not create a feature\nbranch to raise a defect or allocate from a branch copy of the register.\n\nCreate `tickets\u002FDNNN-description\u002Fdefect.org`. All ticket types live directly\nunder `tickets\u002F`; do not create type subdirectories. If root `specs\u002F` exists,\nrequire `sdlc-init` before normal ticket work. Existing IDs are preserved by\nmigration; do not renumber an existing defect when adding evidence.\nUse a descriptive Org title and concise sections suited to the evidence above.\nDo not copy the delivery specification template or add empty ceremonial sections.\n\nAdd the ticket to primary's `docs\u002Fwork.org` with the `defect` tag, the existing\ninitial lifecycle state and a link to `defect.org`. The register owns lifecycle;\nthe report owns the defect evidence. Do not duplicate the report in the index.\nCommit and synchronize only the authorized ticket changes under the project's\nexisting policy, preserving unrelated work. Report a publication failure rather\nthan claiming registration succeeded remotely.\n\n## Handoff\n\nReturn the ID with descriptor, report location, whether it was newly registered\nor added to an existing ticket, and the material unknowns. Registration means\nreported, not confirmed, diagnosed, delivery-approved or corrected.\n\nFurther diagnosis or implementation requires its own instruction. If a fix\nlater needs `spec.org`, add it to the same ticket directory and link the defect\nreport and original requirement; do not create another ticket merely to change\nphase. Preserve the original observations and their provenance. If a genuinely\nseparate change is needed, link it explicitly rather than silently splitting\nidentity. Any later requested audit uses canonical `audits.yaml`; raising a\ndefect alone requires neither an audit nor an audit record.\n","# Raise a defect\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## Purpose and authority\n\nProduce a useful, traceable defect ticket. Raising a defect does not invoke\n`define-change`, approve delivery, start an audit or authorize implementation.\nA report may be actionable for investigation before its cause, reproduction or\ncorrect solution is known. Do not turn reporting into a design gate.\n\nFollow the session's project routing and `READING.md`; reuse retained context.\nFor an initialized SDLC project, read the project's requirement\u002Fwork authorities,\n`ISSUES.md`'s bug and identifier rules, the primary-branch ticket reservation\ncontract in `DELIVERY.md`, and `ORGMODE.md` for the record. Apply only ticket\nregistration here, not delivery admission or the full specification template.\nThe initialization prerequisite above applies to this skill. Do not create a\nforge issue without explicit authority.\n\n## Capture the report\n\nStart from the operator's evidence. Ask only questions needed to identify the\nproblem or make the report useful; record other missing facts as unknown.\nInclude, where known:\n\n- A specific title and short description of the failed user outcome.\n- Observed behaviour and expected behaviour, separately. Cite the requirement,\n  documented contract or operator expectation supporting the latter.\n- Reproduction steps, inputs and preconditions; frequency or intermittency.\n- Affected environment, version or revision, and last known working version.\n- Evidence references, such as exact errors, logs or screenshots, with provenance.\n- Impact, affected users or operations, and any known workaround.\n- Related requirements, tickets and possible duplicates.\n- Unknowns and the next useful investigation question.\n\nDistinguish reported observations, independently reproduced behaviour and\nhypotheses. Do not claim reproduction or a cause without evidence. A credible\nreport without reproduction steps is still recordable. If the expected behaviour\nis disputed or undocumented, preserve that uncertainty instead of inventing a\nrequirement, rejecting the report or converting it silently into a feature.\nRecord operator-assigned priority as such. Keep impact evidence separate from\nany proposed severity; do not invent release commitments.\n\nDescribe how a later check could distinguish the observed failure from the\nexpected behaviour when that is already clear. Formal acceptance criteria,\nAT\u002FRT\u002FUT\u002FOT definitions, root-cause analysis and solution design are not required\nto raise the defect. Do not run intrusive reproductions, change environments,\nwrite regression tests or expand into diagnosis merely to fill the report.\n\n## Register once\n\nSearch the authorized register and directly related records for duplicates.\nFor a confirmed duplicate, update the existing ticket with new evidence and\nprovenance; do not allocate another number. Record a possible relationship\nwithout merging distinct reports merely because their symptoms resemble each\nother. Preserve existing operator edits and evidence.\n\nFor a new SDLC ticket, synchronize primary and reserve an ID using DELIVERY's\ncollision-prevention protocol. Use the same namespace as features and spikes,\nusing D and one more than the highest number reserved across W, D, S and\nlegacy tickets. Never use a defect-only counter. Do not create a feature\nbranch to raise a defect or allocate from a branch copy of the register.\n\nCreate `tickets\u002FDNNN-description\u002Fdefect.org`. All ticket types live directly\nunder `tickets\u002F`; do not create type subdirectories. If root `specs\u002F` exists,\nrequire `sdlc-init` before normal ticket work. Existing IDs are preserved by\nmigration; do not renumber an existing defect when adding evidence.\nUse a descriptive Org title and concise sections suited to the evidence above.\nDo not copy the delivery specification template or add empty ceremonial sections.\n\nAdd the ticket to primary's `docs\u002Fwork.org` with the `defect` tag, the existing\ninitial lifecycle state and a link to `defect.org`. The register owns lifecycle;\nthe report owns the defect evidence. Do not duplicate the report in the index.\nCommit and synchronize only the authorized ticket changes under the project's\nexisting policy, preserving unrelated work. Report a publication failure rather\nthan claiming registration succeeded remotely.\n\n## Handoff\n\nReturn the ID with descriptor, report location, whether it was newly registered\nor added to an existing ticket, and the material unknowns. Registration means\nreported, not confirmed, diagnosed, delivery-approved or corrected.\n\nFurther diagnosis or implementation requires its own instruction. If a fix\nlater needs `spec.org`, add it to the same ticket directory and link the defect\nreport and original requirement; do not create another ticket merely to change\nphase. Preserve the original observations and their provenance. If a genuinely\nseparate change is needed, link it explicitly rather than silently splitting\nidentity. Any later requested audit uses canonical `audits.yaml`; raising a\ndefect alone requires neither an audit nor an audit record.\n",{"name":5,"description":7},"master","b1f296c62065adad981aac0d56b1a457fafa14e3","skills\u002Fdefect-raise","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 defect-raise",{"tool":38,"command":39},"bunx","bunx skills add tigger-developer\u002Fsdlc --skill defect-raise",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tigger-developer\u002Fsdlc --skill defect-raise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fdefect-raise\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",[],[]]