product-requirements

Standardizing product requirements for architecture input involves summarizing what needs to be built, for whom, and why. This Skill captures user needs, MoSCoW priorities, and AI capabilities into structured templates to align stakeholders before design begins.

Document user journeys and MoSCoW requirements by filling out the provided template files, such as REQUIREMENTS.md and USER_JOURNEYS.md. These templates guide architecture conversations by capturing priorities, user flows, and AI capabilities in a unified format.

Structured product requirements templates are needed when aligning stakeholders before the architecture process begins. They encapsulate product needs and AI capabilities into a single coherent input, ensuring architecture teams can map dependencies and scope effectively.

Yes, you can use the .product/ directory workflow to align stakeholders before system design. By creating the directory with provided templates like SUMMARY.md and AI_CAPABILITIES.md, you activate a standardized process that guides downstream architecture teams.

No dependencies are required to map product scope for architects. The approach relies solely on template-driven inputs to encapsulate product needs, ensuring architects receive a coherent input without external module constraints.