documentation-criteria

You need a Product Requirements Document (PRD) before starting feature development to define scope and align stakeholders. It serves as the foundational artifact to ensure all stakeholders understand project requirements and technical approach before implementation begins.

A PRD should include project scope, required content, and stakeholder alignment details. By defining documentation requirements and utilizing standardized templates, you ensure consistency, completeness, and adherence to best practices across all technical projects.

Determine document creation order by evaluating project conditions and complexity. This skill provides decision matrices to guide users on when to create specific documents like PRDs, ADRs, Design Docs, and Work Plans based on project needs.

Yes, the criteria scale with project complexity. By evaluating project scope, you can decide exactly which documents are necessary. For smaller projects, the decision matrices help omit unnecessary artifacts like extensive Work Plans or ADRs.

A Work Plan outlines the broader execution strategy and milestones, whereas a Task File details specific actionable items. Both templates are provided to standardize documentation creation and track project requirements effectively.