Phase Generator

Phase Generator creates PRPROMPTS files in three staged phases: Phase 1 (Core) for architecture, Phase 2 (Quality) for testing and security, and Phase 3 (Demo) for deployment. This prevents information overload by delivering relevant guidance exactly when your team needs it during development.

Yes. Phase Generator reads your PRD (Product Requirements Document) and tailors each phase's files to your project: compliance needs (HIPAA, SOC2), state management (BLoC, Riverpod), authentication methods, target platforms, and project type. Context flows from your PRD metadata into every generated file.

Start by generating Phase 1 (Core) to establish foundational architecture. Once core features are built, generate Phase 2 (Quality) to add testing and security practices. Finally, generate Phase 3 (Demo) for launch preparation and deployment guidance. Each phase builds on the previous foundation.

Yes. Phase Generator requires a PRD file at a specified path; it loads your project's metadata (compliance, platforms, state management, auth method) from that document to customize all generated guidance. Without a PRD, phase-specific context customization cannot occur.

Phase Generator supports an optional overwrite flag. By default, it generates files to your PRPROMPTS directory; you control whether to replace existing phase files or preserve them. This lets you regenerate specific phases without losing manual customizations in other phases.