planning-assistant

To convert unstructured ideas into actionable software plans, provide your raw feature lists or brainstorming notes to a planning assistant that applies SCRUM structuring and senior engineering design patterns to generate Epics, User Stories, and tasks with acceptance criteria.

Structuring software plans using SOLID principles involves applying layered architecture and design patterns like repositories, services, and factories, ensuring each task is self-contained with clear intent and executable in isolation.

Yes, you can generate folder-based documentation and CLAUDE.md scaffolds for future agents by propagating architectural context through your plans, allowing subsequent automated agents to inherit structural guidance and project constraints.

Yes, this planning approach works for discovering hidden requirements in feature requests by proactively asking contextual questions before generating the final software plan, ensuring all architectural and functional constraints are surfaced early.

To organize to-do lists into self-contained software development tasks, you must structure each item with its own context, intent, and acceptance criteria, satisfying layered architecture requirements and ensuring isolated execution.