Prd Planner

This one tackles the classic problem of losing your train of thought while writing PRDs. It creates four persistent files (notes, task plan, PRD, tech spec) and works through a structured workflow so you're not context-switching between research and writing. The clever bit is step 2.5, where it scans your existing codebase for patterns like delete strategies or error handling before asking you edge case questions. If your project already has a soft-delete pattern, it just applies it instead of making you decide again. Honest take: the four-file pattern feels heavy at first, but it's genuinely useful for complex features where you need to show your work and keep stakeholders in sync.