planning

Plan multi-step work in Trekker by structuring epics, tasks, and dependencies to ensure continuity. Group major features into epics, break them into actionable tasks, and declare dependencies so your plan persists across session resets.

Use epics and dependencies when your workflow involves multi-step features requiring strict execution order. Epics group related work into manageable units, while dependencies enforce task sequence and preserve context across sessions.

Break down a large feature by first creating an epic to represent it, then defining independent actionable tasks underneath. Apply search-first planning before structuring these tasks to ensure accurate and complete work breakdown.

Yes, you can record task dependencies to enforce execution order in Trekker. Declaring dependencies maintains execution sequence and preserves context across session resets, ensuring tasks are completed in the correct logical order.

Yes, search-first planning is required before breaking work into epics and tasks. This approach ensures you gather necessary context first, allowing you to create independent tasks and accurately declare dependencies for your Trekker plan.

The best way to maintain plan continuity across multiple Trekker sessions is to structure work using epics, create independent tasks, and explicitly declare dependencies. Session-aware updates then mirror current progress into your plan after validation.