requirements

To run requirements discovery, provide initial client context and use the skill to automate structured sessions. It captures pain points and success criteria across quick, standard, or comprehensive tiers to produce a unified requirements artifact.

Documenting functional, non-functional, data, operational, and transition requirements is best handled through structured discovery. This skill specifies constraints, stakeholders, and success metrics to reduce scope creep and accelerate alignment.

Yes, you can trace requirements dependencies. The skill generates structured knowledge base data with versioning to feed downstream skills like architecture design, RFP responses, and engagement planning.

Yes, the requirements discovery process supports both new engagements and continuations of existing ones. It scales across quick, standard, and comprehensive discovery tiers to fit specific engagement needs.

To define success criteria and AI suitability, the skill automates the capture of client context and specific constraints during discovery. This ensures all success metrics and functional needs are documented in the final artifact.

When automating stakeholder requirements gathering, consider that the output relies heavily on the initial client context provided. Comprehensive discovery requires sufficient input to accurately map data, operational, and transition requirements.