project-discovery

Automating discovery and requirements specification involves orchestrating a single guided session to extract user roles, needs, and constraints, producing a complete requirement-spec.md document. This skill coordinates the ProjectSpecFactory pipeline to synthesize business context into structured project requirements.

Generating a requirement spec from project intent documentation requires parsing the initial project-intent.md file to identify workflows and constraints. The skill delegates to project management and architectural modules to synthesize this input into a metadata-rich requirement specification document.

Yes, the discovery workflow supports resuming with an existing requirement spec document. If a file already exists, the system prompts for user confirmation to ensure safe overwrites before generating the updated metadata-rich requirement specification.

Yes, the requirements discovery process operates without external dependencies, relying solely on internal project management and architectural delegation. It uses a runtime template to transform user roles and business context into a structured specification document.

Identifying user roles and business context during project discovery happens by applying the ProjectSpecFactory pipeline to your initial project documentation. The system extracts flows and constraints, then delegates synthesis to project management and architectural components to finalize the requirements.

A guided discovery session for software project requirements is needed when transitioning from initial project intent to structured planning. It merges user discovery with requirements specification to produce a comprehensive requirement-spec.md ready for the next development phase.