preprocess

To convert a URD into OpenSpec changes, extract the content from Confluence, text notes, or URLs to generate a normalized pre_openspec.md file. This structured artifact is output to the openspec/changes directory, reducing manual restructuring and ambiguity for OpenSpec ingestion.

A pre_openspec.md file is used to normalize URD content into a structured specification ready for OpenSpec ingestion. It captures classification, assumptions, and validation details to reduce ambiguity during requirement conversion.

Yes, you can use Confluence URDs to generate OpenSpec change directories. The process reads the URD content directly from Confluence URLs, scaffolds the directory structure, and creates the pre_openspec.md artifact under openspec/changes/<feature-name>/.

Feature requirements are classified as NEWBUILD or MAINTENANCE by analyzing base_knowledge signals extracted from the URD. The process also determines the transaction flow type, categorizing it as either Financial or Non-Financial.

Yes, you can process raw text notes to create structured OpenSpec artifacts. The preprocessing extracts requirements from pasted plain text notes to derive feature naming, flow type, and the change-directory structure.

A limitation of preprocessing URDs for OpenSpec ingestion is that the process requires a valid URD source from Confluence, local files, or URLs. It generates the pre_openspec.md scaffold but does not perform the final OpenSpec ingestion itself.