[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GZS382C6JC3QHWTSTXSBF":3,"skill-same:01M73GZS382C6JC3QHWTSTXSBF":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M73GZS382C6JC3QHWTSTXSBF","decision-record",null,"Decision record format for gate-moment rulings — Design Gate Row 0 determinations, escalations, and go\u002Fno-go calls captured as durable docs\u002Fdecisions\u002FDEC-YYYYMMDD-NN.md files with rule and evidence citations. Use when: a gate ruling was made, an escalation was resolved, or a go\u002Fno-go decision was reached (ADR-0061).","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.gemini\u002Fskills\u002Fdecision-record\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: decision-record\ndescription: >\n  Decision record format for gate-moment rulings — Design Gate Row 0\n  determinations, escalations, and go\u002Fno-go calls captured as durable\n  docs\u002Fdecisions\u002FDEC-YYYYMMDD-NN.md files with rule and evidence citations.\n  Use when: a gate ruling was made, an escalation was resolved, or a go\u002Fno-go\n  decision was reached (ADR-0061).\nversion: 1.1.0\nowner: pm\nstatus: active\nlast_reviewed: 2026-08-25\nscope: common\nmetadata:\n  type: process\n  triggers:\n    - decision record\n    - gate ruling\n    - go\u002Fno-go decision\n    - escalation decision\n    - record a decision\n---\n\n## Purpose\n\nCloses the Decision link of the Agent → Skill → Knowledge → Evidence → Rule → Decision chain (ADR-0061). Gate rulings made only in chat vanish when the session ends; a decision record keeps the ruling, what was rejected, and which rules and evidence produced it — queryable after the session is gone.\n\n## File Format\n\nRecords live at `docs\u002Fdecisions\u002FDEC-YYYYMMDD-NN.md` — one file per deciding session day, numbered within the day (`01`, `02`, ...) in the order the rulings were made.\n\n### Frontmatter Spec\n\n```yaml\nid: DEC-YYYYMMDD-NN\ndate: YYYY-MM-DD\nagent: \u003Cagent that decided>\ndecision: \u003Cone-line ruling>\nalternatives: \u003Cwhat was rejected and why>\nevidence_refs: [\u003Cevidence-ledger row IDs \u002F finding files>]\nrules_applied: [\u003Crule IDs, e.g. NEWS-R1>]\nskills_used: [\u003Cskill names>]\nknowledge_refs: [\u003CKnowledge-layer docs: country profiles, manuals, ADRs>]\nstatus: proposed|accepted|superseded\n```\n\n| Field | Required | Notes |\n|-------|----------|-------|\n| `id` | yes | Must match the filename; never reused after supersession |\n| `date` | yes | The deciding date, `YYYY-MM-DD` |\n| `agent` | yes | The single agent that owns the ruling (normally `pm`) |\n| `decision` | yes | One line — the ruling itself, not its justification |\n| `alternatives` | yes | What was rejected and why; a record is incomplete without it |\n| `evidence_refs[]` | yes (may be empty) | Entries must resolve to `evidence-ledger` rows or finding files |\n| `rules_applied[]` | yes (may be empty) | Stable rule IDs (see below) |\n| `skills_used[]` | yes (may be empty) | Skill names consulted, drawn from the skill relationship graph vocabulary (ADR-0060) |\n| `knowledge_refs[]` | yes (may be empty) | Knowledge-layer artifacts the ruling rests on — country profiles, manuals, ADRs, procedure schemas (ADR-0061 amendment 2026-08-25: closes the Agent→Skill→**Knowledge**→Evidence→Rule→Decision chain end to end) |\n| `status` | yes | `proposed` until confirmed, `accepted` once acted on, `superseded` when reversed |\n\n### Body\n\nFree-form below the frontmatter: context that does not fit one line, the reasoning trail, and any conditions attached to the ruling.\n\n## Mutation Model: Supersession, Never Deletion\n\nA decision record is never edited to reverse itself and never deleted. To reverse or amend a ruling:\n\n1. Set the original record's `status: superseded` and note the successor (e.g. a `superseded_by: DEC-...` line in its body)\n2. Create a new record that points back (e.g. `supersedes: DEC-...` in its body) and carries the new ruling\n\nThe chain stays append-mostly and auditable — the same model ADRs use in this workspace.\n\n## When to Record (Gate Moments)\n\nPer ADR-0061 and the gate-moment rule in `agents\u002Fpm.md` (workspace root) and `templates\u002Fcommon\u002Fagents\u002Fpm.md` (inherited by every variant), the PM MUST emit a decision record **before dispatch continues** at:\n\n- **Design Gate Row 0 rulings** — exempt\u002Fnon-exempt determination, spec assignment, design approval\n- **Escalations** — permission denials routed to the user, specialist disputes resolved by the PM\n- **Go\u002Fno-go decisions** — proceeding past (or routing back from) any hard gate\n\nRecord the ruling where the gate fires; do not batch records to the end of the session, when the reasoning has already gone cold.\n\n## Rule-ID Citation Convention\n\n`rules_applied[]` entries use stable rule IDs of the form `\u003CDOMAIN>-R\u003CN>`:\n\n- `NEWS-R1` — co-news two-source rule (annotated inline in the co-news context file)\n- IDs are **stable once assigned** — never renumber or reuse; a renamed rule orphans every record quoting it\n- Each variant's registry of rule IDs lives in **its own context.md** (annotated inline on the rule text); there is no central workspace registry\n\n## Linking Evidence\n\n`evidence_refs[]` is the downward link into the Evidence layer: every entry resolves to a row of an `evidence-ledger` table (claim | source | url\u002Fref | verification | status) or a finding file under `docs\u002Fevidence\u002Ffindings\u002F`. A record should read as \"these rules (`rules_applied[]`), applied to this evidence (`evidence_refs[]`), produced this ruling\" without re-deriving either from prose.\n","## Purpose\n\nCloses the Decision link of the Agent → Skill → Knowledge → Evidence → Rule → Decision chain (ADR-0061). Gate rulings made only in chat vanish when the session ends; a decision record keeps the ruling, what was rejected, and which rules and evidence produced it — queryable after the session is gone.\n\n## File Format\n\nRecords live at `docs\u002Fdecisions\u002FDEC-YYYYMMDD-NN.md` — one file per deciding session day, numbered within the day (`01`, `02`, ...) in the order the rulings were made.\n\n### Frontmatter Spec\n\n```yaml\nid: DEC-YYYYMMDD-NN\ndate: YYYY-MM-DD\nagent: \u003Cagent that decided>\ndecision: \u003Cone-line ruling>\nalternatives: \u003Cwhat was rejected and why>\nevidence_refs: [\u003Cevidence-ledger row IDs \u002F finding files>]\nrules_applied: [\u003Crule IDs, e.g. NEWS-R1>]\nskills_used: [\u003Cskill names>]\nknowledge_refs: [\u003CKnowledge-layer docs: country profiles, manuals, ADRs>]\nstatus: proposed|accepted|superseded\n```\n\n| Field | Required | Notes |\n|-------|----------|-------|\n| `id` | yes | Must match the filename; never reused after supersession |\n| `date` | yes | The deciding date, `YYYY-MM-DD` |\n| `agent` | yes | The single agent that owns the ruling (normally `pm`) |\n| `decision` | yes | One line — the ruling itself, not its justification |\n| `alternatives` | yes | What was rejected and why; a record is incomplete without it |\n| `evidence_refs[]` | yes (may be empty) | Entries must resolve to `evidence-ledger` rows or finding files |\n| `rules_applied[]` | yes (may be empty) | Stable rule IDs (see below) |\n| `skills_used[]` | yes (may be empty) | Skill names consulted, drawn from the skill relationship graph vocabulary (ADR-0060) |\n| `knowledge_refs[]` | yes (may be empty) | Knowledge-layer artifacts the ruling rests on — country profiles, manuals, ADRs, procedure schemas (ADR-0061 amendment 2026-08-25: closes the Agent→Skill→**Knowledge**→Evidence→Rule→Decision chain end to end) |\n| `status` | yes | `proposed` until confirmed, `accepted` once acted on, `superseded` when reversed |\n\n### Body\n\nFree-form below the frontmatter: context that does not fit one line, the reasoning trail, and any conditions attached to the ruling.\n\n## Mutation Model: Supersession, Never Deletion\n\nA decision record is never edited to reverse itself and never deleted. To reverse or amend a ruling:\n\n1. Set the original record's `status: superseded` and note the successor (e.g. a `superseded_by: DEC-...` line in its body)\n2. Create a new record that points back (e.g. `supersedes: DEC-...` in its body) and carries the new ruling\n\nThe chain stays append-mostly and auditable — the same model ADRs use in this workspace.\n\n## When to Record (Gate Moments)\n\nPer ADR-0061 and the gate-moment rule in `agents\u002Fpm.md` (workspace root) and `templates\u002Fcommon\u002Fagents\u002Fpm.md` (inherited by every variant), the PM MUST emit a decision record **before dispatch continues** at:\n\n- **Design Gate Row 0 rulings** — exempt\u002Fnon-exempt determination, spec assignment, design approval\n- **Escalations** — permission denials routed to the user, specialist disputes resolved by the PM\n- **Go\u002Fno-go decisions** — proceeding past (or routing back from) any hard gate\n\nRecord the ruling where the gate fires; do not batch records to the end of the session, when the reasoning has already gone cold.\n\n## Rule-ID Citation Convention\n\n`rules_applied[]` entries use stable rule IDs of the form `\u003CDOMAIN>-R\u003CN>`:\n\n- `NEWS-R1` — co-news two-source rule (annotated inline in the co-news context file)\n- IDs are **stable once assigned** — never renumber or reuse; a renamed rule orphans every record quoting it\n- Each variant's registry of rule IDs lives in **its own context.md** (annotated inline on the rule text); there is no central workspace registry\n\n## Linking Evidence\n\n`evidence_refs[]` is the downward link into the Evidence layer: every entry resolves to a row of an `evidence-ledger` table (claim | source | url\u002Fref | verification | status) or a finding file under `docs\u002Fevidence\u002Ffindings\u002F`. A record should read as \"these rules (`rules_applied[]`), applied to this evidence (`evidence_refs[]`), produced this ruling\" without re-deriving either from prose.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":35,"last_reviewed":36},"pm","common","active","1.1.0",{"type":28,"triggers":29},"process",[30,31,32,33,34],"decision record","gate ruling","go\u002Fno-go decision","escalation decision","record a decision","Decision record format for gate-moment rulings — Design Gate Row 0 determinations, escalations, and go\u002Fno-go calls captured as durable docs\u002Fdecisions\u002FDEC-YYYYMMDD-NN.md files with rule and evidence citations. Use when: a gate ruling was made, an escalation was resolved, or a go\u002Fno-go decision was reached (ADR-0061).\n",1787616000000,"main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fcommon\u002F.gemini\u002Fskills\u002Fdecision-record",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill decision-record",{"tool":51,"command":52},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill decision-record",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill decision-record","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.gemini\u002Fskills\u002Fdecision-record\u002FSKILL.md",true,[],[60,68,73,78,83,88],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":67},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":74,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":67},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":79,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":67},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":67},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":67},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]