tech-requirements-extractor

To extract client requirements from a PRD, provide a prd.json file describing the project scope. The system applies taxonomy-driven keyword matching to identify external service credentials and assets, generating a deduplicated checklist in docs/client-requirements.md.

Identifying external service credentials for client onboarding is done by analyzing PRDs to separate client-provided items from internally provisioned assets. It generates a structured, stage-timed requirements document to standardize the onboarding process.

Yes, you can generate a client requirements checklist from multiple PRDs. The extraction process supports reuse across multiple PRDs and stories to standardize onboarding, outputting a consolidated requirements document at docs/client-requirements.md.

Taxonomy-driven keyword matching for PRD asset extraction works by scanning prd.json for predefined credential and asset terms. It maps identified client-provided items to project stages, outputting a structured document that distinguishes client from Entourage-provisioned items.

Yes, you need a prd.json file to map client-provided assets to project stages. Providing a prd.json describing the project scope is the required input to generate the stage-timed client requirements checklist.

The client requirements checklist outputs to a markdown file located at docs/client-requirements.md. This document provides a deduplicated, stage-timed list separating client-provided credentials from Entourage-provisioned items.