project-planning

To plan a software project end-to-end in a single session, you use an adaptive interview flow to capture goals, scope, and constraints, progressing through Discovery, Decisions, Documentation, and Review phases to ensure thorough alignment.

The best way to structure project discovery and technical decisions is using a defined phase sequence with checkpoints, moving from initial Discovery through Decisions, Documentation, and Review to ensure complete alignment and thoroughness.

Yes, you can automatically generate architecture and deployment documentation during project planning. The session auto-generates core artifacts including project.md, architecture.md, deployment.md, patterns.md, and ux-guidelines.md after the guided interview.

Yes, this guided project planning workflow works for internal initiatives and software development. It applies to product initiatives, internal projects, and software development where a structured discovery, decision-making, and documentation workflow is needed.

Fragmented project documentation happens when planning is spread across disconnected meetings and documents. You consolidate it by capturing discovery, decision-making, and knowledge capture into a single guided session with automatic artifact generation.