Planning Documents

To standardize planning document naming, enforce a three-digit sequence number and kebab-case for primary documents within a prompts/ directory, using specific patterns for supporting reports and ideas to ensure consistent organization and retrieval.

The best way to name a new Product Requirements Document is using a sequential three-digit number followed by kebab-case, such as prompts/035-new-feature.md, ensuring it fits within the established project structure.

You organize supporting reports and idea capture files by applying specific naming patterns differentiated from primary documents, maintaining a consistent structure within the prompts/ directory for easy organization and retrieval.

Sequence numbers for new workflow documentation are determined by identifying the next available three-digit sequential number in the existing prompts/ directory, ensuring chronological alignment with established project files.

No specific dependencies or platform setups are required. The documentation structure operates by applying standardized naming conventions to files within a local prompts/ directory without relying on external components.