explore-task

Requirements discovery captures constraints, risks, and success criteria before coding. It iteratively probes stakeholders to develop domain models and evaluate architectural readiness, ensuring implementation plans address actual project needs.

To draft an implementation plan, use a discovery session to surface architectural trade-offs and decisions. A living memory whiteboard enforces strict memory updates, capturing domain models and readiness evaluations prior to development handoff.

Yes, iterative discovery sessions support requirements capture by enforcing one-step-per response. This approach maintains a living memory whiteboard, ensuring architecture decisions and domain models develop progressively through continuous probing.

The best way to evaluate architectural readiness is through structured discovery that probes constraints and success criteria. This produces memory artifacts and an implementation plan, ensuring architecture decisions are fully captured before handoff.

You should avoid drafting an implementation plan when requirements are already fully defined and architecture decisions are stable. If no iterative discovery or domain model development is needed, proceeding directly to coding bypasses the discovery phase.

Yes, the discovery process stores memory artifacts during iterative sessions. It uses a living memory whiteboard with strict updates to capture architecture decisions and implementation plans, ensuring structured handoff to the start-task phase.