preprocess

Name: preprocess
Availability: InStock
Author: MinhQuan

Extracts URD content and normalizes it into a structured pre_openspec.md for OpenSpec ingestion.

Updated Mar 27, 2026

Search Tags:#requirements #openspec #workflow-automation #open-spec #feature-classification #urd #pre_openspec

Ready to run

npx skills add https://github.com/minhquan2904/vibe-check-scam --skill preprocess

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preprocess
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/preprocess
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill preprocess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-process URD into a clean, structured specification suitable for OpenSpec ingestion, reducing manual restructuring and ambiguity during requirement conversion.

Core Features & Use Cases

Read URD content from Confluence pages, plain text notes, or external URLs.
Scaffold an OpenSpec change directory and generate pre_openspec.md structured for OpenSpec ingestion.
Classify features into NEWBUILD or MAINTENANCE using the base_knowledge signals and determine transaction flow type (Financial vs Non-Financial).
Create and organize the OpenSpec change artifacts under openspec/changes/<feature-name>/.

Quick Start

Provide a URD source (Confluence URL, local file path, or pasted raw requirements) to start generating pre_openspec.md.

Frequently Asked Questions about preprocess

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

FAQPage Schema

How do I convert a URD into OpenSpec changes?▼

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.

What is a pre_openspec.md file used for in requirement processing?▼

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.

Can I use Confluence URDs to generate OpenSpec change directories?▼

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>/.

How do I classify feature requirements as NEWBUILD or MAINTENANCE?▼

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.

Can I process raw text notes to create structured OpenSpec artifacts?▼

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.

What are the limitations of preprocessing URDs for OpenSpec ingestion?▼

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.