菜单
Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when planning an epic, when the user states a dependency between work items, or when asked what's unblocked/ready in an epic.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Consume the salesforcedx-vscode-services extension API. Use when an extension depends on salesforcedx-vscode-services and you are registering commands, calling its services (Workspace, Connection, Project, Settings, FS, Channel, Media, prompts), watching files/config/target-org, or wiring the AllServicesLayer/runtime in extensionProvider.ts.
package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.
Prefer vscode-uri over node:path. Use when .ts files in /src import node:path or use path.join/basename/dirname/resolve, URI.file, or memfs paths.
Add custom SVG icons to salesforcedx-vscode-services for font generation. Use when adding new icons to media/icons-src, creating SVG icons for VS Code extension, or defining font-based icons.
TypeScript coding standards — apply when writing, reviewing, or refactoring .ts/.tsx, or naming/renaming .ts files (camelCase casing).
| name | work-item-sequencing |
| description | Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when planning an epic, when the user states a dependency between work items, or when asked what's unblocked/ready in an epic. |
Numbering convention for order + parallelism among work items in one epic. Number = prefix in Subject__c, space-delimited. Per-epic scope; cross-epic deps go in WI body prose, not numbers.
Companion to gus-cli (CLI mechanics: query, create, update, statuses, IDs).
Prefix Subject__c with a dotted number + single space:
1 Set up the runtime service
2 Migrate the parser to the runtime
1.1 Add config schema
1.2 Add config loader
1, 2, 3): in order. 2 waits on 1; 3 waits on 2.1.1, 1.2): same-parent siblings, no waiting on each other.2 waits on 1 + every 1.x/1.x.y.1.1.1, …): same recursive rule.WI ready when every WI sorting before it (at shallower-or-equal ancestor level) is done. Siblings parallel; sibling-group gates next number at parent level.
1.2 ready once 1.1 + descendants done. 2 ready once everything under 1 done.
Done = Status__c is Closed or Completed.
Fixed is not done — usually means PR not merged yet. Non-terminal statuses (Fixed, Ready for Review, QA In Progress) never satisfy a prerequisite. See gus-cli ## Status__c values.
Optional.
Unnumbered = no deps, nothing depends on it. Always ready; never gates, never gated. Don't infer order from date/position — no number means independent.
1, 2).1.1, 1.2).Subject__c with number + space. Create via gus-cli.Dense from 1 per group preferred; gaps harmless (sort is by value).
Status__c. Query without open-only filter — done prerequisites are Closed, which open-only excludes (see gus-cli "What's unfinished in this epic").Subject__c. None → unnumbered.Sort by integer segments (1.2 before 1.10, not lexical). Unnumbered sort last.
1., 1..2, 1.x): treat unnumbered + flag — likely typo'd dependency.1.2): allowed = parallel siblings. Don't flag.1.1, no 1): rule still holds; don't require parent to exist.W-12345 backport, version 2.40 release): only leading N/N.N… + space counts. Ambiguous → ask.