[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCX3RJB055828V7SENMQTW":3,"skill-same:01M6MCX3RJB055828V7SENMQTW":69},{"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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MCX3RJB055828V7SENMQTW","contract-builder",null,"Maintain an execution contract only for an existing legacy change that requires one. New direct\u002Fplanned changes do not invoke this skill when a contract is absent.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcontract-builder\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"builder","contract","contract builder","change","execution","direct","only","Legacy","do","maintain","for","changes","Existing","invoke","when","new","2026-11-10 10:12:30",false,"---\nname: contract-builder\ndescription: Maintain an execution contract only for an existing legacy change that requires one. New direct\u002Fplanned changes do not invoke this skill when a contract is absent.\n---\n\n# Contract Builder\n\n## Bundled runtime\n\nBefore executing a CLI line below, replace its leading `SSF` with `node \"\u003Cplugin-root>\u002Fscripts\u002Fspec-superflow.mjs\"`; `\u003Cplugin-root>` is the absolute directory two levels above this file. Never run `SSF` literally or call an `ssf` from `PATH`.\n\nLegacy compatibility only: new planned changes use proposal.md + tasks.md and `SSF workflow start --path planned`. Do not generate a contract or request a second approval for them. Read the remaining instructions only for an existing legacy change.\n\nConverts planning artifacts into a single execution handshake: `execution-contract.md`. Load the baseline with `SSF runtime asset read templates\u002Fexecution-contract.md`.\n\nRead before generating: `.spec-superflow.yaml` (especially `dp_0_decisions`),\n`proposal.md`, `specs\u002F`, `design.md`, `tasks.md`, then load\n`docs\u002Fartifact-contract.md` with `SSF runtime asset read docs\u002Fartifact-contract.md`.\n\nEnter `bridging` before writing the contract; skip the transition if already there. Honor configured specs\u002Fdesign omissions. Reference requirement IDs and task IDs instead of copying their full text; preserve scope, obligations, tests, and review policy.\n\n## Artifact Language\n\nRead `artifact_language=\u003Cconcrete-language>` from `dp_0_decisions`. Generate\n`execution-contract.md` in the same language as that resolved value and the\napproved planning artifacts. Preserve required schema keywords and code\nidentifiers verbatim; language consistency applies to explanatory prose and\nheadings. If the concrete artifact language is missing or still `auto`, route\nback to `workflow-start` before writing the contract instead of guessing or\nsilently defaulting to English.\n\n## Artifact Mapping\n\n| Source | Extract |\n|--------|---------|\n| `proposal.md` → `## Why` + `## What Changes` | Intent Lock (problem + scope) |\n| `proposal.md` → `## Scope > ### Out of Scope` | Scope Fence |\n| `specs\u002F` → each `### Requirement:` | Approved Requirements, Scenarios, Test Obligations |\n| `design.md` → `## Decisions` | Architecture, Interface, Dependency Constraints |\n| `tasks.md` → numbered task groups | Execution Batches, Completion Definitions, Review Timing |\n\n## Cross-Check: Requirement Coverage\n\nBefore finalizing:\n1. List every SHALL\u002FMUST from `specs\u002F`\n2. Verify each is reflected in Approved Behavior, has a test obligation, and appears in at least one batch\n3. Flag unmapped requirements in Escalation Rules\n4. Note cross-batch dependencies\n\n## Contract Structure\n\nMust make obvious: approved behavior, out-of-scope, constraints, batches, test obligations, review gates, and conditions that force a rewind to planning. Prefer compression over repeating planning details.\n\n## Approval Model (DP-3)\n\nAfter drafting: summarize handoff rules, identify ambiguity and flag unmapped requirements. Reuse explicit approval already covering this exact contract; otherwise request it once, together with any still-pending planning decisions and the default Native execution choice. Approval of scope alone does not approve a contract that has not been shown. Never ask the user to approve the same unchanged contract twice. After approval:\n```bash\nSSF state set \u003Cchange-dir> dp_3_result \"approved: \u003Csummary>\"\nSSF state set \u003Cchange-dir> dp_3_timestamp now\nSSF state rebuild \u003Cchange-dir>\n```\n\nAdvance the state after approval:\n```bash\nSSF state transition \u003Cchange-dir> approved-for-build\n```\n\nDP-3 is a hard gate — no implementation without this record.\n\n## Stale Contract Detection\n\nRefresh if: scope changed in proposal, requirements changed in specs, constraints changed in design, batches changed materially in tasks, or the contract no longer matches intent.\n\n## Hotfix Mode\n\nGenerate a minimal contract only for a legacy Hotfix: Intent Lock (one sentence), Task List (numbered), Approval Gate (DP-3). Skip Scope Fence, Build Rules, Review Gates, Test Evidence. Still requires DP-3 approval. Quick direct execution and direct incident Hotfix do not invoke this skill; they use the signed receipt and finish with `test_result: pass` instead.\n\n## Guardrails\n\n- Do not continue to implementation if ambiguity remains\n- Do not approve the contract on the user's behalf\n- Do not skip the contract because planning docs look complete\n- Flag unmapped requirements; do not silently drop them\n\n## Post-Generation\n\nThe approved contract is recorded by `state rebuild` in the DP-3 sequence above, before the guarded transition. This applies to Full and legacy Hotfix. Do not refresh hashes merely to suppress an unapproved content change.\n\n## Exception Handling\n\n- **Parse failures**: Report specific file and section. Suggest re-running `spec-writer`.\n- **Missing files**: List every missing artifact. Route back to `spec-writer`.\n- **User interruption**: Re-read all artifacts on resume; check contract staleness via content comparison.\n- **Validation failure**: Flag unmapped requirements in Escalation Rules and approval summary.\n","# Contract Builder\n\n## Bundled runtime\n\nBefore executing a CLI line below, replace its leading `SSF` with `node \"\u003Cplugin-root>\u002Fscripts\u002Fspec-superflow.mjs\"`; `\u003Cplugin-root>` is the absolute directory two levels above this file. Never run `SSF` literally or call an `ssf` from `PATH`.\n\nLegacy compatibility only: new planned changes use proposal.md + tasks.md and `SSF workflow start --path planned`. Do not generate a contract or request a second approval for them. Read the remaining instructions only for an existing legacy change.\n\nConverts planning artifacts into a single execution handshake: `execution-contract.md`. Load the baseline with `SSF runtime asset read templates\u002Fexecution-contract.md`.\n\nRead before generating: `.spec-superflow.yaml` (especially `dp_0_decisions`),\n`proposal.md`, `specs\u002F`, `design.md`, `tasks.md`, then load\n`docs\u002Fartifact-contract.md` with `SSF runtime asset read docs\u002Fartifact-contract.md`.\n\nEnter `bridging` before writing the contract; skip the transition if already there. Honor configured specs\u002Fdesign omissions. Reference requirement IDs and task IDs instead of copying their full text; preserve scope, obligations, tests, and review policy.\n\n## Artifact Language\n\nRead `artifact_language=\u003Cconcrete-language>` from `dp_0_decisions`. Generate\n`execution-contract.md` in the same language as that resolved value and the\napproved planning artifacts. Preserve required schema keywords and code\nidentifiers verbatim; language consistency applies to explanatory prose and\nheadings. If the concrete artifact language is missing or still `auto`, route\nback to `workflow-start` before writing the contract instead of guessing or\nsilently defaulting to English.\n\n## Artifact Mapping\n\n| Source | Extract |\n|--------|---------|\n| `proposal.md` → `## Why` + `## What Changes` | Intent Lock (problem + scope) |\n| `proposal.md` → `## Scope > ### Out of Scope` | Scope Fence |\n| `specs\u002F` → each `### Requirement:` | Approved Requirements, Scenarios, Test Obligations |\n| `design.md` → `## Decisions` | Architecture, Interface, Dependency Constraints |\n| `tasks.md` → numbered task groups | Execution Batches, Completion Definitions, Review Timing |\n\n## Cross-Check: Requirement Coverage\n\nBefore finalizing:\n1. List every SHALL\u002FMUST from `specs\u002F`\n2. Verify each is reflected in Approved Behavior, has a test obligation, and appears in at least one batch\n3. Flag unmapped requirements in Escalation Rules\n4. Note cross-batch dependencies\n\n## Contract Structure\n\nMust make obvious: approved behavior, out-of-scope, constraints, batches, test obligations, review gates, and conditions that force a rewind to planning. Prefer compression over repeating planning details.\n\n## Approval Model (DP-3)\n\nAfter drafting: summarize handoff rules, identify ambiguity and flag unmapped requirements. Reuse explicit approval already covering this exact contract; otherwise request it once, together with any still-pending planning decisions and the default Native execution choice. Approval of scope alone does not approve a contract that has not been shown. Never ask the user to approve the same unchanged contract twice. After approval:\n```bash\nSSF state set \u003Cchange-dir> dp_3_result \"approved: \u003Csummary>\"\nSSF state set \u003Cchange-dir> dp_3_timestamp now\nSSF state rebuild \u003Cchange-dir>\n```\n\nAdvance the state after approval:\n```bash\nSSF state transition \u003Cchange-dir> approved-for-build\n```\n\nDP-3 is a hard gate — no implementation without this record.\n\n## Stale Contract Detection\n\nRefresh if: scope changed in proposal, requirements changed in specs, constraints changed in design, batches changed materially in tasks, or the contract no longer matches intent.\n\n## Hotfix Mode\n\nGenerate a minimal contract only for a legacy Hotfix: Intent Lock (one sentence), Task List (numbered), Approval Gate (DP-3). Skip Scope Fence, Build Rules, Review Gates, Test Evidence. Still requires DP-3 approval. Quick direct execution and direct incident Hotfix do not invoke this skill; they use the signed receipt and finish with `test_result: pass` instead.\n\n## Guardrails\n\n- Do not continue to implementation if ambiguity remains\n- Do not approve the contract on the user's behalf\n- Do not skip the contract because planning docs look complete\n- Flag unmapped requirements; do not silently drop them\n\n## Post-Generation\n\nThe approved contract is recorded by `state rebuild` in the DP-3 sequence above, before the guarded transition. This applies to Full and legacy Hotfix. Do not refresh hashes merely to suppress an unapproved content change.\n\n## Exception Handling\n\n- **Parse failures**: Report specific file and section. Suggest re-running `spec-writer`.\n- **Missing files**: List every missing artifact. Route back to `spec-writer`.\n- **User interruption**: Re-read all artifacts on resume; check contract staleness via content comparison.\n- **Validation failure**: Flag unmapped requirements in Escalation Rules and approval summary.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcontract-builder",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill contract-builder",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill contract-builder",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill contract-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMageByte-Zero\u002Fspec-superflow\u002Fskills\u002Fcontract-builder\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]