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.