project-plan-session

Session planning from git history requires reading repository commits, AGENTS.md, and progress logs to surface actionable goals, then mapping them into a dependency-linked task list with routine, analytical, or generative complexity labels for focused execution.

A dependency-linked task graph maps project tasks by their execution dependencies and assigns complexity tags like routine, analytical, or generative. You need it for session planning to sequence effort efficiently and focus on actionable goals.

Planning a focused work session using repository context involves analyzing git history and AGENTS.md to assess project state, then outputting a concrete plan with a ready-to-run task list and clearly defined session goals based on progress artifacts.

Yes, you need an AGENTS.md file at the repository root along with progress artifacts for automated project planning. The planner requires these inputs to identify project state and generate accurate, dependency-linked session goals.

Yes, you can categorize task complexity automatically when creating a project plan. The planner assigns complexity labels to each task in the dependency graph, categorizing them as routine, analytical, or generative to guide effort allocation.

Limitations of using git history for task dependency tracking include requiring access to the repository root with an AGENTS.md file and progress logs. Without these artifacts, the planner cannot accurately assess project state or surface actionable goals.