assess

To classify a raw project requirement into an architecture type like a RAG app or multi-agent system, provide the project text to the assess skill. It categorizes the requirement into defined types and outputs an architecture-ready assessment to guide subsequent decomposition and activation planning.

The best way to scope upfront architecture and agent activation before decomposition is to run an initial project assessment. This process delivers an activation map, complexity estimate, and high-level design decisions to inform the BUILD phase and prepare the plan.

Yes, you can use requirement classification to estimate complexity for an automation pipeline. Classifying the raw requirement outputs a complexity estimate and suggests a high-level architecture approach, specifically scoping work before initiating the decomposition phase.

Upfront architecture assessment supports hybrid AI OS components and prompt chains. The classification mechanism categorizes requirements across these defined project types, recommending key design decisions to guide the subsequent BUILD phase.

You need to run requirement classification for early project scoping when you have a raw client requirement and must determine the project type before decomposition. It prepares the architecture-ready plan by delivering an initial activation map and complexity estimate.

After classifying a requirement into a multi-agent system, the assessment recommends high-level architecture approaches and key design decisions. It outputs an initial agent activation map and complexity estimate to directly inform the downstream design and build phases.