pdd

Prompt-Driven Development

Overview

This sop guides you through the process of transforming a rough idea into a detailed design document with an implementation plan and todo list. It follows the Prompt-Driven Development methodology to systematically refine your idea, conduct necessary research, create a comprehensive design, and develop an actionable implementation plan. The process is designed to be iterative, allowing movement between requirements clarification and research as needed.

Parameters

• rough_idea (required): The initial concept or idea you want to develop into a detailed design
• project_dir (optional, default: ".sop/planning"): The base directory where all project files will be stored

Constraints for parameter acquisition:

• You MUST ask for all required parameters upfront in a single prompt rather than one at a time
• You MUST support multiple input methods including:
  • Direct input: Text provided directly in the conversation
  • File path: Path to a local file containing the rough idea
  • URL: Link to an internal resource (e.g., Quip doc, wiki page)
  • Other methods: You SHOULD be open to other ways the user might want to provide the idea
• You MUST use appropriate tools to access content based on the input method
• You MUST confirm successful acquisition of all parameters before proceeding
• You SHOULD save the acquired rough idea to a consistent location for use in subsequent steps
• You MUST NOT overwrite the existing project directory because this could destroy previous work and cause data loss
• You MUST ask for project_dir if it is not given and default ".sop/planning" directory already exist and has contents from previous iteration

Steps

1. Create Project Structure

Set up a directory structure to organize all artifacts created during the process.

Constraints:

• You MUST create the specified project directory if it doesn't already exist
• You MUST create the following files:
  • {project_dir}/rough-idea.md (containing the provided rough idea)
  • {project_dir}/idea-honing.md (for requirements clarification)
• You MUST create the following subdirectories:
  • {project_dir}/research/ (directory for research notes)
  • {project_dir}/design/ (directory for design documents)
  • {project_dir}/implementation/ (directory for implementation plans)
• You MUST notify the user when the structure has been created
• You MUST prompt the user to add all project files to Q's context using the command: /context add {project_dir}/**/*.md
• You MUST explain that this will ensure all project files remain in context throughout the process