[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARFMKRTJTVGAWAFQDXDQH4":3,"skill-same:01M7ARFMKRTJTVGAWAFQDXDQH4":56},{"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},"01M7ARFMKRTJTVGAWAFQDXDQH4","migrate-legacy-acs-to-sdlc-v1",null,"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.","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\u002Fmigrate-legacy-acs-to-sdlc-v1\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: migrate-legacy-acs-to-sdlc-v1\ndescription: 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.\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\n# Prepare an SDLC v1 project for SDLC v3\n\n`sdlc-init` invokes this writing migration with the configured\n`delivery.definition` harness, provider where applicable, and model. Do not\nsubstitute an audit model or a hardcoded model preference.\n\nIf `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md` is absent or unreadable, report that exact path;\nnever search for another copy.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`, `\u002Fopt\u002Fsdlc\u002Fdocs\u002FISSUES.md`,\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FTESTING.md`, `\u002Fopt\u002Fsdlc\u002Fdocs\u002FDOCUMENTATION.md`, and\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FGIT.md` in full. Consult project documentation only as needed\nfor the targeted staleness pass.\n\n## Outcome and boundary\n\nThis is a fast archival and classification pass, not a historical review. It\nproduces:\n\n1. an accurate, complete, and current `docs\u002FACs.org`, produced by losslessly\n   converting the normally pre-existing `docs\u002FACs.md` before reconciliation;\n2. a lossless ticket snapshot under `docs\u002Farchive\u002Fmigrated-tickets\u002F`;\n3. a concise `docs\u002Fticket-migration.org` migration index;\n4. targeted corrections to stale project documentation;\n5. the unchanged move of the single file matching\n   `docs\u002Fimplementation?plan.md` to `docs\u002Farchive\u002F` with the same basename,\n   when the source exists; and\n6. closure of every legacy issue after the archive is committed.\n\nDo not invoke `sdlc-init`, create SDLC v3 artefacts, change tests or\nimplementation, or migrate undelivered scope into `docs\u002FACs.org`. Do not inspect\nold code, search Git history ticket by ticket, re-litigate design, reproduce\nhistorical verification, or add migration comments to tickets.\n\nExplicit invocation authorizes the defined final closure batch. It does not\nauthorize ticket-body, label, milestone, test-table, pull-request, or unrelated\nGitHub mutations.\n\n## Archive every issue once\n\nUse the authenticated GitHub interface for the current repository. Retrieve\nevery actual issue, open and closed, with all comments and the timeline events\nneeded to identify linked code commits; exclude pull requests and do not iterate\nan assumed numeric range. Download into an operating-system temporary staging\ndirectory, verify complete issue, comment, and timeline pagination, then promote\nthe complete snapshot to `docs\u002Farchive\u002Fmigrated-tickets\u002F`.\n\nWrite one `\u003Cissue-number>.md` file per issue containing:\n\n- issue number and descriptor, original URL, snapshot state and reason, labels,\n  milestone, author, and creation and closure dates;\n- the complete original issue body; and\n- every comment in chronological order, with author and timestamp; and\n- every code-commit reference recorded in the body, comments, or ticket\n  timeline.\n\nWrite `manifest.json` in that directory with repository identity, snapshot\ntime, issue count, open and closed counts, pagination result, and filenames.\nPreserve archived source text exactly; do not sanitize it.\n\nThe tracked archive is the immutable cache. Read only it for all later ticket\npasses and never re-fetch individual issues. A purpose-created baseline issue\nis the sole exception: create and archive it exactly once, then add it to the\nmanifest. If staging is incomplete or the destination contains conflicting\nmaterial, stop before closure.\n\n## Start the durable migration index\n\nImmediately after verifying and promoting the archive, create\n`docs\u002Fticket-migration.org` from\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002Fticket-migration.org`. Read that template in\nfull and follow its embedded structure, syntax, and validation instructions. If\nan interrupted migration already has an index, preserve its recorded state and\nreconcile its structure rather than overwriting it.\n\nUpdate the document after each completed evidence phase and immediately after\nclassifying each ticket. Incremental writes are required; per-ticket commits are\nnot. Give every ID a descriptor and link ticket titles to the local archived\nfiles. Keep complete source text in the archive rather than duplicating it here.\n\n## Normalize the legacy AC ledger before reconciliation\n\nUse `VALID` for an applicable legacy AC, never `HOLD` or `HOLDING`. Keep test\nresults and heuristic qualifications separate; validity is not a test pass.\nThose old generated labels are compatibility inputs, not blocked-work states.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002FACs.org` in full. Before indexing live\nRTs or appending migrated ACs, convert the pre-existing `docs\u002FACs.md` into\n`docs\u002FACs.org` using that canonical structure. Use `git mv` so the tracked\nhistory remains visible and no conflicting Markdown ledger remains.\n\nThe conversion is structural, not editorial. Inventory and reconcile every AC\nidentifier, descriptor, requirement, source, shipped or migration version,\nstatus, test relationship, test status, evidence note, supersession link,\nfootnote, glossary entry, and explanatory note. Normalize Markdown links,\ntables, emphasis, code spans, and footnotes into native Org without summarizing,\nsilently correcting, reinterpreting, merging, splitting, renumbering, or dropping\ninformation. Counts are supporting checks only; perform a field-by-field\nsource-to-target reconciliation before continuing.\n\nRemove the AC template's instructional comments and placeholders from the\nproject ledger. Keep `docs\u002FACs.org` valid Org throughout the remaining migration\nand validate it with Pandoc's Org reader after conversion and before every\nrepository commit that changes it.\n\nAfter writing or changing the ledger, cross-check its outline against the\ncanonical example in `\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002FACs.org`. Every AC MUST\nbe a level-three heading containing both its identifier and a useful descriptor,\nfor example `*** AC29.1 - Reject an invalid host definition`. An identifier-only\nAC heading fails this structural check. Preserve any additional source detail\nunder the canonical nested fields.\n\nIf `docs\u002FACs.org` already exists and `docs\u002FACs.md` does not, validate it against\nthe template and resume. If both exist, stop and report the conflict rather than\nchoosing or merging a ledger. If neither exists, initialize an empty\n`docs\u002FACs.org` from the canonical template; do not invent legacy entries. After\nconversion or initialization, verify that `docs\u002FACs.md` is absent and use only\n`docs\u002FACs.org` for all later passes.\n\nThe authority section must state that `docs\u002FACs.org` is the sole authority for\nrequirements established under the legacy ticket-led process. Archived tickets,\ncomments, and `docs\u002Fticket-migration.org` retain disposition, provenance, and\nrationale only; they are not current requirement or AC authorities. Signed-off\nSDLC v3 specifications govern requirements established or changed after\nmigration.\n\n## Build the live-RT delivery map first\n\n1. Index `docs\u002FACs.org` without renumbering entries. Presence of\n   an AC in this ledger is delivery evidence even when its archived ticket does\n   not record test results.\n2. Review every test definition in the maintained regression harness. Record\n   its descriptor, path or test name, AC references, issue references, and\n   membership in the supported whole-suite command. Do not infer this inventory\n   solely from `docs\u002FACs.org`.\n3. Run that whole suite, normally `make test`, at most once. Reuse current\n   operator-supplied passing evidence when available.\n4. If the suite fails, record its result in `docs\u002Fticket-migration.org`,\n   checkpoint only that index, the verified ticket archive, and the verified\n   format-only `docs\u002FACs.org` conversion, and stop. Do not diagnose the failure,\n   append or semantically change ACs, classify tickets, change other project\n   documentation, create a baseline issue, close tickets, or rerun individual or\n   historical tests within this skill.\n5. Only after a current passing result, build the RT-to-ticket-to-AC evidence\n   map.\n\nA passing suite makes each RT in its maintained harness current passing evidence\nfor the behaviour it verifies and every ticket and AC to which it directly\ntraces. Use this to correct legacy pending or unverified RT statuses. Reviewing\ntest definitions here is evidence inspection, not implementation investigation.\nDo not classify any ticket as delivered, abandoned, or undelivered until this\ncomplete live-RT map exists.\n\n## Complete the live-RT delivery sweep\n\nFor every RT still in the maintained harness, confirm that:\n\n- it traces to at least one AC;\n- every cited AC exists in `docs\u002FACs.org`; and\n- the ledger records the RT-to-AC relationship.\n\nRecover a missing AC from its archived ticket when provenance exists. When a\nticket has no recorded passing test evidence but one or more of its RTs remain\nin the passing maintained harness, classify the whole ticket as delivered.\nMigrate every AC and treat its pending or unverified UTs and OTs as assumed\npassing for migration. Mark every AC without independent passing evidence and\nthe delivered-ticket entry with the migration-heuristic footnote.\n\nFor orphan RTs, automatically create one pre-migration baseline issue for the\ncomplete descriptor-bearing set, archive it once, and use its ticket number for\nminimal observable ACs bounded by the maintained tests and current\ndocumentation. Explicit invocation authorizes this issue creation; do not stop\nfor operator confirmation.\n\n## Classify tickets after the RT sweep\n\nRead [references\u002Fclassification.md](references\u002Fclassification.md) in full and\nclassify the archived tickets in ascending number order, using the completed\nlive-RT map first. Then apply pre-existing `docs\u002FACs.org` entries, archived test\nresults, ticket-linked code commits, and other explicit evidence. Apply\nunambiguous AC additions, status corrections, supersessions, and traceability\nrepairs directly to `docs\u002FACs.org`. Add missing ACs at their correct identifier\npositions so the ledger remains in sequence. Preserve identifiers, descriptors,\nwording, relationships, statuses, provenance, and supersession lineage.\n\nTreat a code-commit reference recorded on a ticket as delivery evidence unless\nthe archived record explicitly says that work was reverted, abandoned, or only\npartial. Ticket state is not delivery evidence. Apart from identifying issues\nthat need final closure, use it only after the complete evidence pass finds no\ndelivery evidence: a closed ticket's scope is abandoned, while an open ticket's\nscope is undelivered.\n\n## Apply the near-complete heuristic automatically\n\nClassify a ticket as delivered when:\n\n- at least one test has a recorded passing result;\n- every recorded test has a passing result except no more than two tests in\n  total;\n- every unresolved test is a unit test or operator test marked `PENDING` or\n  otherwise unverified;\n- no test is recorded as failed; and\n- the archive contains no explicit abandonment, reversion, or known-incomplete\n  evidence.\n\nTreat those one or two tests as assumed passing for migration. If an AC's only\nevidence is one of these assumed passes:\n\n- mark the AC visibly in `docs\u002FACs.org` without changing its identifier;\n- mark the test as an assumed pass using the existing table conventions; and\n- add one footnote explaining that delivery was inferred because every other\n  ticket test passed and the only unresolved evidence was one or two UTs or OTs\n  whose results were not recorded.\n\nThe footnote must state that this is an inferred migration status, not a\ncontemporaneous test result, and identify whether inference came from the\nnear-complete rule or maintained-RT evidence for the ticket. Do not mark an AC\nthat has independent recorded passing evidence. Mark the ticket in the\ndelivered list with Org footnote `[fn:migration-heuristic]`.\n\nWhen no delivery evidence remains after applying the evidence rules, use only\nthe ticket's snapshot state to classify its scope: closed means abandoned; open\nmeans undelivered. Record an open bug under open defects. Record feature scope\nunder defined but undelivered features with its precise disposition. Do not\ninvestigate the code merely to rescue the ticket from this classification.\n\nRead one archived ticket at a time. As soon as it is classified, write its\ndisposition and evidence to `docs\u002Fticket-migration.org`, update the completed and\nnext-ticket fields, then release its raw content before reading the next ticket.\nDo not keep the complete ticket archive in model context.\n\n## Reconcile project documents\n\nGroup the migrated ACs by affected product area, then compare each batch with\nthe approved design, architecture, project documentation, maintained RT\nevidence, and external ownership contracts. When the batch clearly represents\na newer feature or change, update the affected documentation. When the agent is\nunsure whether behaviour or documentation is current, inspect only the relevant\nimplementation as a tie-breaker. Do not inspect code AC by AC, search Git\nhistory, or broaden the investigation beyond that uncertainty.\n\nBefore recording reconciliation complete, verify that `docs\u002FACs.org` follows the\ncanonical template and that its authority section is the sole normative\nauthority statement. Remove or rewrite migrated Markdown preamble wording that\nsays migration is unfinished, older criteria still live authoritatively in\ntickets, or ticket bodies and comments remain requirement or AC authorities.\nPreserve document metadata and every substantive source item. A migration note\nmay record the completion date or final migrated identifier as history.\n\nCheck active project instructions and documentation, including a project-root\n`AGENTS.md` when present, for statements that migration is unfinished, that\n`docs\u002FACs.md` remains current, or that live or archived tickets remain current\nrequirement authorities. Correct unambiguous stale statements in the same\ndocumentation batch. Record genuinely ambiguous conflicts for the operator; do\nnot rewrite archived material.\n\nMatch `docs\u002Fimplementation?plan.md` so either the hyphenated or underscored\nfilename is accepted. If exactly one source matches and its same-basename path\nunder `docs\u002Farchive\u002F` does not exist, move it unchanged with Git and repair\nreferences made stale by the move. If more than one source matches or the\ndestination conflicts, ask the operator rather than overwriting anything.\n\nSanitize changed technical documentation except the lossless ticket snapshots.\nUse proportionate link, format, and traceability checks; never create regression\ntests that grep documentation.\n\n## Finalize the Org migration index\n\nFollow the canonical template's finalization instructions. Original GitHub URLs\nremain in the lossless snapshots. Mark every heuristic-delivered ticket with\n`[fn:migration-heuristic]` and define that footnote once in the Org document.\nSet the migration phase to complete only after reconciliation and closure\nrecording finish. The archive is exhaustive; the Org file is the concise map a\nlater agent reads first.\n\n## Preserve context continuity\n\nDo not initiate or request context compaction merely because the migration is\nbatch-oriented or contains many tickets. Ticket count alone is not a reason to\ncompact. Never load the complete ticket archive into context at once; use the\narchive as external memory and `docs\u002Fticket-migration.org` as durable working\nstate.\n\nBefore any agent-initiated compaction that is genuinely necessary, first record\nthe current phase, completed ticket IDs or ranges, active assumptions, evidence,\nunresolved items, and next action in `docs\u002Fticket-migration.org`.\n\nIf the harness compacts automatically, continue without operator handback.\nReread this skill, the archive manifest, `docs\u002FACs.org`, and\n`docs\u002Fticket-migration.org`, then resume from the first unfinished ticket. Do not\nre-fetch tickets, repeat completed analysis, rerun tests, or reconsider recorded\ndecisions without contradictory evidence.\n\n## Commit and close in batches\n\nClassify automatically wherever these rules apply. Do not stop for operator\nconfirmation of heuristics, orphan RTs, baseline-ticket creation, or closure.\nPut genuinely contradictory or unclassifiable records in the human-review\nsection and continue; they do not prevent legacy ticket closure.\n\nCommit the complete archive, `docs\u002FACs.org`, removal of `docs\u002FACs.md`, Org index,\ndocumentation corrections, and implementation-plan move before closing any\nissue. The authorized baseline issue for orphan RTs is the only earlier GitHub\nmutation. Never commit per ticket or AC. For an unusually large migration, use\noccasional fixed-size recovery commits only when necessary.\n\nAfter that durable commit succeeds, close every issue that was open in the\nsnapshot and any archived pre-migration baseline issue created during the\nworkflow. Attempt each closure once, without a comment, continue through the\nbatch, and collect failures. Do not re-fetch tickets after closure.\n\nUpdate `docs\u002Fticket-migration.org` with the closure date, totals, and exact\nfailures, then create one final closure-record commit. Only a recorded failed\nclosure may be retried later.\n\n## Completion report\n\nReport only:\n\n- archived issue count and manifest path;\n- the single suite result or current evidence reused;\n- live-RT checksum totals, mapped and unresolved;\n- migration-category totals;\n- `docs\u002FACs.org` changes and heuristic-marked AC count;\n- stale documents corrected and implementation-plan archival;\n- archive and closure-record commits;\n- tickets closed; and\n- unresolved classifications or closure failures, with descriptors.\n\nIf the migration index or completion report does not fit in one terminal\nscreen, present `docs\u002Fticket-migration.org` with the previewer selected by\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`.\nPresentation is not an approval gate.\n\nThe operator decides whether the project is ready for `sdlc-init`, which\ncreates the v3 profile and work ledger after this ticket migration is committed.\n","Follow `\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\n# Prepare an SDLC v1 project for SDLC v3\n\n`sdlc-init` invokes this writing migration with the configured\n`delivery.definition` harness, provider where applicable, and model. Do not\nsubstitute an audit model or a hardcoded model preference.\n\nIf `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md` is absent or unreadable, report that exact path;\nnever search for another copy.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`, `\u002Fopt\u002Fsdlc\u002Fdocs\u002FISSUES.md`,\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FTESTING.md`, `\u002Fopt\u002Fsdlc\u002Fdocs\u002FDOCUMENTATION.md`, and\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FGIT.md` in full. Consult project documentation only as needed\nfor the targeted staleness pass.\n\n## Outcome and boundary\n\nThis is a fast archival and classification pass, not a historical review. It\nproduces:\n\n1. an accurate, complete, and current `docs\u002FACs.org`, produced by losslessly\n   converting the normally pre-existing `docs\u002FACs.md` before reconciliation;\n2. a lossless ticket snapshot under `docs\u002Farchive\u002Fmigrated-tickets\u002F`;\n3. a concise `docs\u002Fticket-migration.org` migration index;\n4. targeted corrections to stale project documentation;\n5. the unchanged move of the single file matching\n   `docs\u002Fimplementation?plan.md` to `docs\u002Farchive\u002F` with the same basename,\n   when the source exists; and\n6. closure of every legacy issue after the archive is committed.\n\nDo not invoke `sdlc-init`, create SDLC v3 artefacts, change tests or\nimplementation, or migrate undelivered scope into `docs\u002FACs.org`. Do not inspect\nold code, search Git history ticket by ticket, re-litigate design, reproduce\nhistorical verification, or add migration comments to tickets.\n\nExplicit invocation authorizes the defined final closure batch. It does not\nauthorize ticket-body, label, milestone, test-table, pull-request, or unrelated\nGitHub mutations.\n\n## Archive every issue once\n\nUse the authenticated GitHub interface for the current repository. Retrieve\nevery actual issue, open and closed, with all comments and the timeline events\nneeded to identify linked code commits; exclude pull requests and do not iterate\nan assumed numeric range. Download into an operating-system temporary staging\ndirectory, verify complete issue, comment, and timeline pagination, then promote\nthe complete snapshot to `docs\u002Farchive\u002Fmigrated-tickets\u002F`.\n\nWrite one `\u003Cissue-number>.md` file per issue containing:\n\n- issue number and descriptor, original URL, snapshot state and reason, labels,\n  milestone, author, and creation and closure dates;\n- the complete original issue body; and\n- every comment in chronological order, with author and timestamp; and\n- every code-commit reference recorded in the body, comments, or ticket\n  timeline.\n\nWrite `manifest.json` in that directory with repository identity, snapshot\ntime, issue count, open and closed counts, pagination result, and filenames.\nPreserve archived source text exactly; do not sanitize it.\n\nThe tracked archive is the immutable cache. Read only it for all later ticket\npasses and never re-fetch individual issues. A purpose-created baseline issue\nis the sole exception: create and archive it exactly once, then add it to the\nmanifest. If staging is incomplete or the destination contains conflicting\nmaterial, stop before closure.\n\n## Start the durable migration index\n\nImmediately after verifying and promoting the archive, create\n`docs\u002Fticket-migration.org` from\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002Fticket-migration.org`. Read that template in\nfull and follow its embedded structure, syntax, and validation instructions. If\nan interrupted migration already has an index, preserve its recorded state and\nreconcile its structure rather than overwriting it.\n\nUpdate the document after each completed evidence phase and immediately after\nclassifying each ticket. Incremental writes are required; per-ticket commits are\nnot. Give every ID a descriptor and link ticket titles to the local archived\nfiles. Keep complete source text in the archive rather than duplicating it here.\n\n## Normalize the legacy AC ledger before reconciliation\n\nUse `VALID` for an applicable legacy AC, never `HOLD` or `HOLDING`. Keep test\nresults and heuristic qualifications separate; validity is not a test pass.\nThose old generated labels are compatibility inputs, not blocked-work states.\n\nRead `\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002FACs.org` in full. Before indexing live\nRTs or appending migrated ACs, convert the pre-existing `docs\u002FACs.md` into\n`docs\u002FACs.org` using that canonical structure. Use `git mv` so the tracked\nhistory remains visible and no conflicting Markdown ledger remains.\n\nThe conversion is structural, not editorial. Inventory and reconcile every AC\nidentifier, descriptor, requirement, source, shipped or migration version,\nstatus, test relationship, test status, evidence note, supersession link,\nfootnote, glossary entry, and explanatory note. Normalize Markdown links,\ntables, emphasis, code spans, and footnotes into native Org without summarizing,\nsilently correcting, reinterpreting, merging, splitting, renumbering, or dropping\ninformation. Counts are supporting checks only; perform a field-by-field\nsource-to-target reconciliation before continuing.\n\nRemove the AC template's instructional comments and placeholders from the\nproject ledger. Keep `docs\u002FACs.org` valid Org throughout the remaining migration\nand validate it with Pandoc's Org reader after conversion and before every\nrepository commit that changes it.\n\nAfter writing or changing the ledger, cross-check its outline against the\ncanonical example in `\u002Fopt\u002Fsdlc\u002Fdocs\u002Ftemplates\u002Fmigration\u002FACs.org`. Every AC MUST\nbe a level-three heading containing both its identifier and a useful descriptor,\nfor example `*** AC29.1 - Reject an invalid host definition`. An identifier-only\nAC heading fails this structural check. Preserve any additional source detail\nunder the canonical nested fields.\n\nIf `docs\u002FACs.org` already exists and `docs\u002FACs.md` does not, validate it against\nthe template and resume. If both exist, stop and report the conflict rather than\nchoosing or merging a ledger. If neither exists, initialize an empty\n`docs\u002FACs.org` from the canonical template; do not invent legacy entries. After\nconversion or initialization, verify that `docs\u002FACs.md` is absent and use only\n`docs\u002FACs.org` for all later passes.\n\nThe authority section must state that `docs\u002FACs.org` is the sole authority for\nrequirements established under the legacy ticket-led process. Archived tickets,\ncomments, and `docs\u002Fticket-migration.org` retain disposition, provenance, and\nrationale only; they are not current requirement or AC authorities. Signed-off\nSDLC v3 specifications govern requirements established or changed after\nmigration.\n\n## Build the live-RT delivery map first\n\n1. Index `docs\u002FACs.org` without renumbering entries. Presence of\n   an AC in this ledger is delivery evidence even when its archived ticket does\n   not record test results.\n2. Review every test definition in the maintained regression harness. Record\n   its descriptor, path or test name, AC references, issue references, and\n   membership in the supported whole-suite command. Do not infer this inventory\n   solely from `docs\u002FACs.org`.\n3. Run that whole suite, normally `make test`, at most once. Reuse current\n   operator-supplied passing evidence when available.\n4. If the suite fails, record its result in `docs\u002Fticket-migration.org`,\n   checkpoint only that index, the verified ticket archive, and the verified\n   format-only `docs\u002FACs.org` conversion, and stop. Do not diagnose the failure,\n   append or semantically change ACs, classify tickets, change other project\n   documentation, create a baseline issue, close tickets, or rerun individual or\n   historical tests within this skill.\n5. Only after a current passing result, build the RT-to-ticket-to-AC evidence\n   map.\n\nA passing suite makes each RT in its maintained harness current passing evidence\nfor the behaviour it verifies and every ticket and AC to which it directly\ntraces. Use this to correct legacy pending or unverified RT statuses. Reviewing\ntest definitions here is evidence inspection, not implementation investigation.\nDo not classify any ticket as delivered, abandoned, or undelivered until this\ncomplete live-RT map exists.\n\n## Complete the live-RT delivery sweep\n\nFor every RT still in the maintained harness, confirm that:\n\n- it traces to at least one AC;\n- every cited AC exists in `docs\u002FACs.org`; and\n- the ledger records the RT-to-AC relationship.\n\nRecover a missing AC from its archived ticket when provenance exists. When a\nticket has no recorded passing test evidence but one or more of its RTs remain\nin the passing maintained harness, classify the whole ticket as delivered.\nMigrate every AC and treat its pending or unverified UTs and OTs as assumed\npassing for migration. Mark every AC without independent passing evidence and\nthe delivered-ticket entry with the migration-heuristic footnote.\n\nFor orphan RTs, automatically create one pre-migration baseline issue for the\ncomplete descriptor-bearing set, archive it once, and use its ticket number for\nminimal observable ACs bounded by the maintained tests and current\ndocumentation. Explicit invocation authorizes this issue creation; do not stop\nfor operator confirmation.\n\n## Classify tickets after the RT sweep\n\nRead [references\u002Fclassification.md](references\u002Fclassification.md) in full and\nclassify the archived tickets in ascending number order, using the completed\nlive-RT map first. Then apply pre-existing `docs\u002FACs.org` entries, archived test\nresults, ticket-linked code commits, and other explicit evidence. Apply\nunambiguous AC additions, status corrections, supersessions, and traceability\nrepairs directly to `docs\u002FACs.org`. Add missing ACs at their correct identifier\npositions so the ledger remains in sequence. Preserve identifiers, descriptors,\nwording, relationships, statuses, provenance, and supersession lineage.\n\nTreat a code-commit reference recorded on a ticket as delivery evidence unless\nthe archived record explicitly says that work was reverted, abandoned, or only\npartial. Ticket state is not delivery evidence. Apart from identifying issues\nthat need final closure, use it only after the complete evidence pass finds no\ndelivery evidence: a closed ticket's scope is abandoned, while an open ticket's\nscope is undelivered.\n\n## Apply the near-complete heuristic automatically\n\nClassify a ticket as delivered when:\n\n- at least one test has a recorded passing result;\n- every recorded test has a passing result except no more than two tests in\n  total;\n- every unresolved test is a unit test or operator test marked `PENDING` or\n  otherwise unverified;\n- no test is recorded as failed; and\n- the archive contains no explicit abandonment, reversion, or known-incomplete\n  evidence.\n\nTreat those one or two tests as assumed passing for migration. If an AC's only\nevidence is one of these assumed passes:\n\n- mark the AC visibly in `docs\u002FACs.org` without changing its identifier;\n- mark the test as an assumed pass using the existing table conventions; and\n- add one footnote explaining that delivery was inferred because every other\n  ticket test passed and the only unresolved evidence was one or two UTs or OTs\n  whose results were not recorded.\n\nThe footnote must state that this is an inferred migration status, not a\ncontemporaneous test result, and identify whether inference came from the\nnear-complete rule or maintained-RT evidence for the ticket. Do not mark an AC\nthat has independent recorded passing evidence. Mark the ticket in the\ndelivered list with Org footnote `[fn:migration-heuristic]`.\n\nWhen no delivery evidence remains after applying the evidence rules, use only\nthe ticket's snapshot state to classify its scope: closed means abandoned; open\nmeans undelivered. Record an open bug under open defects. Record feature scope\nunder defined but undelivered features with its precise disposition. Do not\ninvestigate the code merely to rescue the ticket from this classification.\n\nRead one archived ticket at a time. As soon as it is classified, write its\ndisposition and evidence to `docs\u002Fticket-migration.org`, update the completed and\nnext-ticket fields, then release its raw content before reading the next ticket.\nDo not keep the complete ticket archive in model context.\n\n## Reconcile project documents\n\nGroup the migrated ACs by affected product area, then compare each batch with\nthe approved design, architecture, project documentation, maintained RT\nevidence, and external ownership contracts. When the batch clearly represents\na newer feature or change, update the affected documentation. When the agent is\nunsure whether behaviour or documentation is current, inspect only the relevant\nimplementation as a tie-breaker. Do not inspect code AC by AC, search Git\nhistory, or broaden the investigation beyond that uncertainty.\n\nBefore recording reconciliation complete, verify that `docs\u002FACs.org` follows the\ncanonical template and that its authority section is the sole normative\nauthority statement. Remove or rewrite migrated Markdown preamble wording that\nsays migration is unfinished, older criteria still live authoritatively in\ntickets, or ticket bodies and comments remain requirement or AC authorities.\nPreserve document metadata and every substantive source item. A migration note\nmay record the completion date or final migrated identifier as history.\n\nCheck active project instructions and documentation, including a project-root\n`AGENTS.md` when present, for statements that migration is unfinished, that\n`docs\u002FACs.md` remains current, or that live or archived tickets remain current\nrequirement authorities. Correct unambiguous stale statements in the same\ndocumentation batch. Record genuinely ambiguous conflicts for the operator; do\nnot rewrite archived material.\n\nMatch `docs\u002Fimplementation?plan.md` so either the hyphenated or underscored\nfilename is accepted. If exactly one source matches and its same-basename path\nunder `docs\u002Farchive\u002F` does not exist, move it unchanged with Git and repair\nreferences made stale by the move. If more than one source matches or the\ndestination conflicts, ask the operator rather than overwriting anything.\n\nSanitize changed technical documentation except the lossless ticket snapshots.\nUse proportionate link, format, and traceability checks; never create regression\ntests that grep documentation.\n\n## Finalize the Org migration index\n\nFollow the canonical template's finalization instructions. Original GitHub URLs\nremain in the lossless snapshots. Mark every heuristic-delivered ticket with\n`[fn:migration-heuristic]` and define that footnote once in the Org document.\nSet the migration phase to complete only after reconciliation and closure\nrecording finish. The archive is exhaustive; the Org file is the concise map a\nlater agent reads first.\n\n## Preserve context continuity\n\nDo not initiate or request context compaction merely because the migration is\nbatch-oriented or contains many tickets. Ticket count alone is not a reason to\ncompact. Never load the complete ticket archive into context at once; use the\narchive as external memory and `docs\u002Fticket-migration.org` as durable working\nstate.\n\nBefore any agent-initiated compaction that is genuinely necessary, first record\nthe current phase, completed ticket IDs or ranges, active assumptions, evidence,\nunresolved items, and next action in `docs\u002Fticket-migration.org`.\n\nIf the harness compacts automatically, continue without operator handback.\nReread this skill, the archive manifest, `docs\u002FACs.org`, and\n`docs\u002Fticket-migration.org`, then resume from the first unfinished ticket. Do not\nre-fetch tickets, repeat completed analysis, rerun tests, or reconsider recorded\ndecisions without contradictory evidence.\n\n## Commit and close in batches\n\nClassify automatically wherever these rules apply. Do not stop for operator\nconfirmation of heuristics, orphan RTs, baseline-ticket creation, or closure.\nPut genuinely contradictory or unclassifiable records in the human-review\nsection and continue; they do not prevent legacy ticket closure.\n\nCommit the complete archive, `docs\u002FACs.org`, removal of `docs\u002FACs.md`, Org index,\ndocumentation corrections, and implementation-plan move before closing any\nissue. The authorized baseline issue for orphan RTs is the only earlier GitHub\nmutation. Never commit per ticket or AC. For an unusually large migration, use\noccasional fixed-size recovery commits only when necessary.\n\nAfter that durable commit succeeds, close every issue that was open in the\nsnapshot and any archived pre-migration baseline issue created during the\nworkflow. Attempt each closure once, without a comment, continue through the\nbatch, and collect failures. Do not re-fetch tickets after closure.\n\nUpdate `docs\u002Fticket-migration.org` with the closure date, totals, and exact\nfailures, then create one final closure-record commit. Only a recorded failed\nclosure may be retried later.\n\n## Completion report\n\nReport only:\n\n- archived issue count and manifest path;\n- the single suite result or current evidence reused;\n- live-RT checksum totals, mapped and unresolved;\n- migration-category totals;\n- `docs\u002FACs.org` changes and heuristic-marked AC count;\n- stale documents corrected and implementation-plan archival;\n- archive and closure-record commits;\n- tickets closed; and\n- unresolved classifications or closure failures, with descriptors.\n\nIf the migration index or completion report does not fit in one terminal\nscreen, present `docs\u002Fticket-migration.org` with the previewer selected by\n`\u002Fopt\u002Fsdlc\u002Fdocs\u002FMAIN.md`.\nPresentation is not an approval gate.\n\nThe operator decides whether the project is ready for `sdlc-init`, which\ncreates the v3 profile and work ledger after this ticket migration is committed.\n",{"name":5,"description":7},"master","b1f296c62065adad981aac0d56b1a457fafa14e3","skills\u002Fmigrate-legacy-acs-to-sdlc-v1","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 migrate-legacy-acs-to-sdlc-v1",{"tool":38,"command":39},"bunx","bunx skills add tigger-developer\u002Fsdlc --skill migrate-legacy-acs-to-sdlc-v1",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tigger-developer\u002Fsdlc --skill migrate-legacy-acs-to-sdlc-v1","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fmigrate-legacy-acs-to-sdlc-v1\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",315,"https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fmigrate-legacy-acs-to-sdlc-v1\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fclassification.md",4943,"https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fmigrate-legacy-acs-to-sdlc-v1\u002Freferences\u002Fclassification.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7ARFHHPW7JD2S35ECPPNRXK","hands-off-spike","Run an explicitly invoked, unattended exploratory spike from a signed-off brief, with current-session internal test-code and implementation reviews, never merged or deployed.","https:\u002F\u002Fgithub.com\u002Ftigger-developer\u002Fsdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fhands-off-spike\u002FSKILL.md",[],[]]