sr-split-ready

To check if an RFC or architecture review is ready for task decomposition, inspect the artifact for baseline structural requirements like metadata, evidence anchors, acceptance criteria, and scope. This process acts as a split linter to ensure documents are properly structured for executable task splitting.

Task decomposition preparation is the process of validating that large drafts and review reports contain sufficient structure, such as source coverage maps and P0/P1 evidence tables, before splitting. You need to lint artifacts when preparing architecture audits or RFCs for executable workflow integration.

You prepare a large draft for splitting by verifying it meets baseline and structural requirements for task decomposition. This involves checking for dependency ordering and scope, then generating a companion document that details the artifact's review baseline and source coverage map.

Yes, you need basic knowledge of task decomposition principles and a structured review artifact to properly prepare RFCs. This foundational knowledge is required to interpret the split linter checks and apply the resulting verdict and checklist to your architecture review workflows.

A split readiness check for architecture reviews outputs a READY or NOT-READY verdict alongside a detailed checklist of structural requirements. It also generates a companion document mapping the artifact's review baseline, source coverage, and P0/P1 evidence table for task decomposition.