work-item-sequencing

Orders GUS work items within an epic using dotted numeric prefixes in Subject__c.

1.0k|454|Updated Jun 21, 2017
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill work-item-sequencing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-item-sequencing
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/work-item-sequencing
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill work-item-sequencing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning an epic in GUS often leaves dependencies between work items implicit, making it unclear which items are blocked, which are ready, and which can run in parallel. This Skill defines a numbering convention that encodes sequencing and parallelism directly in the Subject__c field.

Core Features & Use Cases

  • Dependency Encoding: Prefix work item subjects with dotted numbers (1, 2, 1.1, 1.2) to express sequential order and parallel sibling groups within an epic.
  • Readiness Analysis: Determine which work items in an epic are ready, blocked, or done by comparing numeric prefixes against Closed/Completed statuses.
  • ADR-First Sequencing: Assign the lowest numbers to ADR-writing work items so architectural decisions are recorded before dependent work begins.
  • Use Case: When planning a multi-part epic, ask the assistant to number the work items so that setup tasks gate migration tasks, parallel subtasks share a parent number, and you can later query what is currently unblocked.

Quick Start

Ask the assistant to number the work items in this epic so dependencies and parallel tasks are clear, then list which items are ready to start.

Frequently Asked Questions about work-item-sequencing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I show dependencies between GUS work items in an epic?

Prefix each work item's Subject__c with a dotted number followed by a space. Sequential numbers like 1 and 2 mean 2 waits on 1, while sibling numbers like 1.1 and 1.2 run in parallel under the same parent.

How do I find which work items in an epic are ready to start?

Query all work items in the epic including Closed ones, parse the leading dotted number from each Subject__c, and check whether every item sorting before it is Closed or Completed. Unnumbered items are always ready.

Does a Fixed status count as done for work item dependencies?

No, Fixed is not done because it usually means the pull request is not merged yet. Only Closed or Completed statuses satisfy a prerequisite; non-terminal statuses like Ready for Review never unblock dependents.

When should I number work items in an epic?

Number items during epic-level planning or when a dependency is explicitly stated. Skip numbering for standalone work or epics of accumulated independent items, since unnumbered items are treated as fully independent.

What happens with malformed or duplicate work item numbers?

Malformed prefixes like 1. or 1..2 are treated as unnumbered but flagged as likely typos. Duplicate numbers like two 1.2 items are allowed and simply represent parallel siblings.