work-decomposition

Splitting a ruleset into tasks for skill authoring requires dividing the ruleset into TaskBoard tasks while defining sequencing, grouping, and difficulty to prevent design drift and high error costs. It enforces per-stage task creation and phase handling.

Grouping and ordering rules for a TaskBoard involves processing complex rules first so subsequent rules can reuse established mechanisms. This strategy maintains consistency across multi-document rules and anchors decisions in PATTERNS.md for auditability.

PATTERNS.md is needed when decomposing rules for governance because it serves as cross-phase memory and iteration evidence. It anchors design decisions to avoid duplicate work, maintain traceability, and document milestones for reuse.

Axis-based difficulty in task decomposition works by evaluating rule complexity to determine task order and grouping strategies during rule extraction. It guides the sequencing of TaskBoard tasks to ensure foundational mechanisms are built before dependent rules are processed.

Yes, you can use rule extraction patterns for multi-document governance by applying consistent TaskBoard naming conventions and phase boundary controls. This ensures team alignment and tracks coverage across complex rule sets.

Manual ruleset splitting in skill authoring risks design drift and high correction costs due to inconsistent task grouping and lack of cross-phase memory. Without anchored decision documentation, tracking milestone coverage and ensuring traceability becomes unreliable.