ais.maintain.clarify

Route user input to ingest project context and clarify feature specifications.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-maintain-clarify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ais.maintain.clarify
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.maintain.clarify
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-maintain-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of ingesting new project context and clarifying ambiguities in feature specifications, making it easier to maintain and update AI-driven projects.

Core Features & Use Cases

  • Project Context Ingestion: Automatically classify and integrate new project context (e.g., SOWs, transcripts, requirements) into project artifacts.
  • Spec Clarification: Resolve ambiguities in feature specifications by routing based on user input and conversation context.
  • Use Case: For a project with a new change order, use this Skill to ingest the change order, classify it, and update the project plan and architecture accordingly.

Quick Start

Use the /ais.maintain.clarify skill to process the new change order document 'change-order-v2.docx'.

Frequently Asked Questions about ais.maintain.clarify

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

FAQPage Schema
How do I ingest project context and classify new requirements for AI projects?

Project context ingestion automatically classifies and integrates new requirements like SOWs and transcripts into project artifacts, routing content based on source authority hierarchy.

What is the best way to clarify ambiguities in feature specifications during project maintenance?

Spec clarification resolves ambiguities in feature specifications by routing user input and conversation context to accurately classify and update project artifacts.

How do I update a project plan after receiving a new change order document?

To update a project plan after a change order, ingest the document to classify its content and automatically apply incremental updates to architecture directories and artifacts.

Do I need specific directory access to process spec clarifications for AI project maintenance?

Yes, spec clarification requires access to project specification and architecture directories to accurately route content and apply incremental artifact updates.

Can I use automated routing to integrate transcripts into existing project artifacts?

Yes, automated routing integrates transcripts by classifying context through a source authority hierarchy, ensuring ingestion updates the correct project artifacts.

What are the limitations of using automated context ingestion for project plan updates?

Context ingestion limitations include reliance on predefined source authority hierarchy for classification and mandatory access to project spec and architecture directories for updates.